From what i see here on xda, seems to be no way of upgrading a rooted MM to Nougat?
All i can find is flashing a stock MM and sideloading the OTA.
Is it accurate, or is there a way to preserve current ROM?
Flashing the stock kernel / recovery perhaps?
On the other hand is there a real advantage of N over MM, other than the higher version number?
I am pretty satisfied with MM, but the temptation is high
Thank you!
dyonissos said:
From what i see here on xda, seems to be no way of upgrading a rooted MM to Nougat?
All i can find is flashing a stock MM and sideloading the OTA.
Is it accurate, or is there a way to preserve current ROM?
Flashing the stock kernel / recovery perhaps?
On the other hand is there a real advantage of N over MM, other than the higher version number?
I am pretty satisfied with MM, but the temptation is high
Thank you!
Click to expand...
Click to collapse
If you are happy and everything is working the way you want, leave it alone. I do not see a great advantage of Nougat over MM. I have had N on a couple of my other phones and it made no real daily difference. There are a couple of customer oms based on N, you can flash just to scratch that itch.
Try Epsilon ROM
Just to clarify, i am only interested in the stock rom, but thank you for the suggestion.
I am quite upset Motorola did not release a recovery image for Z Play, as they did for the X, but i will get over it.
mahdif62 said:
Try Epsilon ROM
Click to expand...
Click to collapse
Isn't that based on NT? So even not an option for MM users...
Usually it should be possible to do OTA.
Root is usually systemless, so system is not modified.
Twrp only gets booted not flashed, so recovery is not modified.
Logo is not modified.
If you did not use the power of root to modify something, only modified part is boot partition. It was said some years ago that it would not be checked, but this may have changed.
I'll try it in some weeks. Don't have the time currently. Doing Nandroid backup is time consuming, and restoring system if something is not working also. OTA is supposed to work without problems, and it should revert to a usable (not updated) state if it doesn't, but I wouldn't bet on it.
Related
So i'm confused about this whole thing with ROMs and firmware and the Viper One 3.0.0 that was just released.
I've been playing it safe with ROMs, being outdated regularly because "it worked". Probably not the best choice for security reasons, but wiping my phone and reinstalling the OS, restoring all the apps, is time consuming and something I try to avoid doing as much as possible.
So Saturday I upgraded my phone from 1.9.1 of Viper One M9 to 2.3.0, then took the OTA to 2.3.1. Previously I installed 1.9.1 and a week later 2.0.0 came out. So I waited until this weekend to finally go to 2.x.x. In a mean twist of fate, less than 24 hours later I'd find that Viper One M9 3.0.0 is out. So no matter what I try to do it seems I'm in for perpetual upgrades, wiping and reinstalling the OS, restoring apps, etc.
So here's my questions:
1. Do I actually need to install any firmwares for this? I see dottat's thread http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397 and I'm not sure if I'm supposed to install that first. My instinct is "no" but I would like to verify that before I try to go to 3.0.0.
2. If it's not required, is it at least optional? If so, what benefits are we aware of that the new firmware will fix? I get the impression that the firmware update isn't truly supported with Viper One M9 since the firmware hasn't been officially released, nor was it unofficially released before the compiled 3.0.0 build was released.
3. How "official" is the 1.33.605.15 that I just linked above? Is it 100% for sure going to be the next release and we're just waiting for it to be pushed out as an OTA update? When I had my Droid Bionic we had something like 20+ "unofficial" builds of ICS that were leaked early, and ultimately the one that was released OTA was 3 or 4 versions behind what was the 'latest'. Definitely created problems for some people and not looking to see that happen to me.
4. When I do an upgrade of Viper One, I normally do the full wipe and then have to restore the apps with titanium backup, then the SMS messages that I have with another app, resetup the icons on my screens, resetup the viper settings, etc. Takes me basically a full day to re-test and re-setup everything how I like it. Is there a better way that doesn't take all day? I'd prefer to be on the latest, but with the constant restoring I'm pretty much always behind because I don't have the 8+ hours it takes to resetup my phone exactly how I want it every time an update comes out. I've heard the non-wiping is not recommended, so I've never tried that. Is it actually safe and effective?
5. Anyone using 3.0.0 and having any problems or comments?
In case anyone asks, the phone is s-off, rooted, etc by the mighty dottat with his Java card.
Thanks,
-Josh
Joshy8 said:
So i'm confused about this whole thing with ROMs and firmware and the Viper One 3.0.0 that was just released.
I've been playing it safe with ROMs, being outdated regularly because "it worked". Probably not the best choice for security reasons, but wiping my phone and reinstalling the OS, restoring all the apps, is time consuming and something I try to avoid doing as much as possible.
So Saturday I upgraded my phone from 1.9.1 of Viper One M9 to 2.3.0, then took the OTA to 2.3.1. Previously I installed 1.9.1 and a week later 2.0.0 came out. So I waited until this weekend to finally go to 2.x.x. In a mean twist of fate, less than 24 hours later I'd find that Viper One M9 3.0.0 is out. So no matter what I try to do it seems I'm in for perpetual upgrades, wiping and reinstalling the OS, restoring apps, etc. [emoji14]
So here's my questions:
1. Do I actually need to install any firmwares for this? I see dottat's thread http://forum.xda-developers.com/verizon-one-m9/general/official-ruu-1-33-605-15-t3137397 and I'm not sure if I'm supposed to install that first. My instinct is "no" but I would like to verify that before I try to go to 3.0.0.
2. If it's not required, is it at least optional? If so, what benefits are we aware of that the new firmware will fix? I get the impression that the firmware update isn't truly supported with Viper One M9 since the firmware hasn't been officially released, nor was it unofficially released before the compiled 3.0.0 build was released.
3. How "official" is the 1.33.605.15 that I just linked above? Is it 100% for sure going to be the next release and we're just waiting for it to be pushed out as an OTA update? When I had my Droid Bionic we had something like 20+ "unofficial" builds of ICS that were leaked early, and ultimately the one that was released OTA was 3 or 4 versions behind what was the 'latest'. Definitely created problems for some people and not looking to see that happen to me.
4. When I do an upgrade of Viper One, I normally do the full wipe and then have to restore the apps with titanium backup, then the SMS messages that I have with another app, resetup the icons on my screens, resetup the viper settings, etc. Takes me basically a full day to re-test and re-setup everything how I like it. Is there a better way that doesn't take all day? I'd prefer to be on the latest, but with the constant restoring I'm pretty much always behind because I don't have the 8+ hours it takes to resetup my phone exactly how I want it every time an update comes out. I've heard the non-wiping is not recommended, so I've never tried that. Is it actually safe and effective?
5. Anyone using 3.0.0 and having any problems or comments?
In case anyone asks, the phone is s-off, rooted, etc by the mighty dottat with his Java card.
Thanks,
-Josh
Click to expand...
Click to collapse
There's newer firmware out. Look in neo's 5.1 deodex thread. That os is also 5.1 (rom).
Sent from my HTC6535LVW using Tapatalk
LOL! So it is! I saw it last night and somehow I screwed up and linked to your thread. Hooray for tired long days.
1. You do need to update your firmware to 2.6.605.10 before installing ViperOneM9 3.0.0, or you will most likely see a bootloop or have other issues.
2. ViperOneM9 3.0.0 was based on the 2.6.605.10 firmware that is posted in NEO's thread. Bottom line is that you should be on that firmware before flashing viper.
3. The 2.6.605.10 firmware is official, but prerelease, and it is very likely not the final version that will be released when the FOTA is pushed out to the public. You can just flash the firmware of the final release version when that is released, so you don't need to worry about being ahead/behind the release version.
4. On ViperOneM9, there is no reason to do a full wipe unless you are coming from another ROM. If you read the thread, you will see that the developers and most of the people around there haven't done a clean flash since their first flash of viper. Make a backup before flashing, and you can always revert to that if you have an issue when you dirty flash.
5. 3.0.0 is working great. No reason not to update.
Thanks for the response bschram. It is appreciated.
I actually wiped my phone and installed 3.0.0 without updating the firmware. Phone still works fine, but I will be updating the firmware as soon as I am confident I know what I'm doing with firmware upgrades. I'm a bit more nervous about updating firmware as I don't want to break the phone.
I'm glad to hear that I don't have to do a full wipe, and I'll definitely be doing that going forward. I will say that 3.0.0 is way more reliable than 1.9.1 was.
Just to make sure I am doing things correctly.... I am not totally new to this. Coming from stock 5.0.2... with S-off/Bootloader Unlocked. Flash firmware from NEO's deodexed rom in fastboot, advanced wipe in TWRP, then flash any 5.1 rom that is compatible IC, Viper, ect.... Then we should be good to go?
Then when offical OTA arrives, wait until firmware is pulled then flash the same way? Just making sure I will doing things right..... Thanks in advance
bschram said:
1. You do need to update your firmware to 2.6.605.10 before installing ViperOneM9 3.0.0, or you will most likely see a bootloop or have other issues.
2. ViperOneM9 3.0.0 was based on the 2.6.605.10 firmware that is posted in NEO's thread. Bottom line is that you should be on that firmware before flashing viper.
3. The 2.6.605.10 firmware is official, but prerelease, and it is very likely not the final version that will be released when the FOTA is pushed out to the public. You can just flash the firmware of the final release version when that is released, so you don't need to worry about being ahead/behind the release version.
4. On ViperOneM9, there is no reason to do a full wipe unless you are coming from another ROM. If you read the thread, you will see that the developers and most of the people around there haven't done a clean flash since their first flash of viper. Make a backup before flashing, and you can always revert to that if you have an issue when you dirty flash.
5. 3.0.0 is working great. No reason not to update.
Click to expand...
Click to collapse
Came in a bit late to the m9 threads. Is the losing VOLTE thing still a thing or was that earlier builds and firmwares? My phone is attached to my work account so it's big pain to talk with actual verizon and i've been hesitant on flashing roms. Not asking for gaurantees, i get the risk, just wondering if that is still going on.
teckels said:
Came in a bit late to the m9 threads. Is the losing VOLTE thing still a thing or was that earlier builds and firmwares? My phone is attached to my work account so it's big pain to talk with actual verizon and i've been hesitant on flashing roms. Not asking for gaurantees, i get the risk, just wondering if that is still going on.
Click to expand...
Click to collapse
It's never been 100% understood why this has happened. It isn't specific to any ROM, I think someone on stock rooted ROM had this issue happen. Once you S-OFF you will be at risk, as far I am aware.
andybones said:
It's never been 100% understood why this has happened. It isn't specific to any ROM, I think someone on stock rooted ROM had this issue happen. Once you S-OFF you will be at risk, as far I am aware.
Click to expand...
Click to collapse
Is it a common thing or has it only happened to one or two people.
Tommydorns said:
Is it a common thing or has it only happened to one or two people.
Click to expand...
Click to collapse
I
Thiss I am not too sure of, but I don't think too many.
Tommydorns said:
Is it a common thing or has it only happened to one or two people.
Click to expand...
Click to collapse
Me and one or two others. I have my suspicions as to what caused it and the casual crack rom flasher likely won't fall victim to it.
Sent from my HTC6535LVW using Tapatalk
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.
Good day guys!
I have an app that I need to use for my phone but it seems in android N that it consumes more battery, maybe because it is not optimized for it yet. Regardless, I would like to try MM again and see if it does indeed drain less, if not, I would like to go back to android N. Can I flash MM thru bootloader as described here (Restore for OTA part) > https://forum.xda-developers.com/moto-z-play/how-to/howto-moto-z-play-unlock-root-t3508547, obviously not flashing over bootloader.img or the modem. It is then my understanding I cannot take the OTA again to get back to android N because it will brick my device. With that, how would I get back to android N if and when I want? Could I just restore my backup that is made before my downgrade? Or do I have to flash custom stock ROMs provided here? Can I even do that?
I am rooted in android N, I am actually not sure how to unroot it to get another OTA. With the systemless root, I believe I just need to reflash boot.img, however, I didn't make a backup of that, and I am not sure where to get it. Maybe I get it thru the android N OTA? I found a file called boot.img.p. If I removed the p is this what I need?
Thanks, guys!
Cheers
Joshua
Just bumping this... No one has any thoughts or ideas here?
Hello all,
Long story short I currently have an Unlocked 10, rooted, s off, and bootloader unlocked. I have flashed over the Verizon rom and radios last year and left it this way for a while. I'm getting to the point where I'm about ready for a factory reset but figured I might as well update if I'm going to do that. Better yet I'd like to get on LeeDroid but preferably on Android N.
So I need to update to an Android N ROM first, then over to LeeDroid. I can do it, but frankly I do this stuff so little that every time I get a little nervous. My 10 is my daily driver but I currently have a raggedy s6 here I can pop a sim in for a minute if needed.
So I'm wondering would it make sense to just do a backup, flash the latest Unlocked N version then flash LeeDroid? Wouldn't my Verizon radios stay where they're at, or will flashing those roms over write them? And, none of this flashing should overwrite my recovery, should it?
Also, I apologize if this is not appropriate but my other option at this point is to ask, are there any fairly well regarded XDA friends here with some spare time that would be open to taking 20 bucks or so to get me fixed up remotely over teamviewer or something?
Thanks for all your help. I don't post here often but when I do I always find the direction I need as someone who is not a frequent modder anymore lol.
Launchpadmcqu4ck said:
Hello all,
Long story short I currently have an Unlocked 10, rooted, s off, and bootloader unlocked. I have flashed over the Verizon rom and radios last year and left it this way for a while. I'm getting to the point where I'm about ready for a factory reset but figured I might as well update if I'm going to do that. Better yet I'd like to get on LeeDroid but preferably on Android N.
So I need to update to an Android N ROM first, then over to LeeDroid. I can do it, but frankly I do this stuff so little that every time I get a little nervous. My 10 is my daily driver but I currently have a raggedy s6 here I can pop a sim in for a minute if needed.
So I'm wondering would it make sense to just do a backup, flash the latest Unlocked N version then flash LeeDroid? Wouldn't my Verizon radios stay where they're at, or will flashing those roms over write them? And, none of this flashing should overwrite my recovery, should it?
Also, I apologize if this is not appropriate but my other option at this point is to ask, are there any fairly well regarded XDA friends here with some spare time that would be open to taking 20 bucks or so to get me fixed up remotely over teamviewer or something?
Thanks for all your help. I don't post here often but when I do I always find the direction I need as someone who is not a frequent modder anymore lol.
Click to expand...
Click to collapse
To minimize potential problems I would start fresh going from M to N.
Flash the full N RUU.exe. Flash the latest TWRP, then flash LeeDroid. New firmware, TWRP, and custom rom.
comstockload said:
To minimize potential problems I would start fresh going from M to N.
Flash the full N RUU.exe. Flash the latest TWRP, then flash LeeDroid. New firmware, TWRP, and custom rom.
Click to expand...
Click to collapse
Would you suggest Verizon N rom since I'm already on Verizon M or would Unlocked N be better?
Launchpadmcqu4ck said:
Would you suggest Verizon N rom since I'm already on Verizon M or would Unlocked N be better?
Click to expand...
Click to collapse
Get a copy of your current M rom for the firmware you currently have and download that. Remember, we're talking full roms not updates. Now get the latest N rom for your device (full ruu.exe). Now you have options. I would flash the N rom, then the latest TWRP, then LeeDroid. Any problems, and you can go right back to M. I always use TWRP 3.0.2-6 with M. So if I go back to M I flash that version of TWRP (from within TWRP itself) first. Take your time. You can do this. You can get the latest N rom from HTC's website. To get your M rom you'll have to search for it using your firmware numbers. Someone should have a copy.
BTW, you can watch ROOT JUNKY's videos on youtube as a refresher on the basics of flashing TWRP and so on. Don't use his files though. They're old.
comstockload said:
Get a copy of your current M rom for the firmware you currently have and download that. Remember, we're talking full roms not updates. Now get the latest N rom for your device (full ruu.exe). Now you have options. I would flash the N rom, then the latest TWRP, then LeeDroid. Any problems, and you can go right back to M. I always use TWRP 3.0.2-6 with M. So if I go back to M I flash that version of TWRP (from within TWRP itself) first. Take your time. You can do this. You can get the latest N rom from HTC's website. To get your M rom you'll have to search for it using your firmware numbers. Someone should have a copy.
Click to expand...
Click to collapse
Yeah I think you're right. I made it this far lol. But the N rom from HTC would just be the unlocked N wouldn't it, not Verizon? I know the Verizon ruu is over in the Verizon HTC 10 forum here so I could get that. Also I think I need to go brush up on firmware vs rom I tend to think they're the same thing but they're not, right?
Launchpadmcqu4ck said:
Yeah I think you're right. I made it this far lol. But the N rom from HTC would just be the unlocked N wouldn't it, not Verizon? I know the Verizon ruu is over in the Verizon HTC 10 forum here so I could get that. Also I think I need to go brush up on firmware vs rom I tend to think they're the same thing but they're not, right?
Click to expand...
Click to collapse
I see. By "unlocked" you mean the US unlocked GSM HTC 10. I wouldn't mess with trying to alter your radios right now. Yes, stick with Verizon on everything. LeeDroid should run fine with that. Installing a new HTC rom changes your firmware. It will be updated as you go to N. If you decide to back to M, it will be downgraded. Installing a custom rom won't change your firmware. A full rom is composed of several components. The firmware is one component.
comstockload said:
I see. By "unlocked" you mean the US unlocked GSM HTC 10. I wouldn't mess with trying to alter your radios right now. Yes, stick with Verizon on everything. LeeDroid should run fine with that. Installing a new HTC rom changes your firmware. It will be updated as you go to N. If you decide to back to M, it will be downgraded. Installing a custom rom won't change your firmware. A full rom is composed of several components. The firmware is one component.
Click to expand...
Click to collapse
Ohhh okay I follow. Yeah sorry I did mean the GSM Unlocked model, I bought direct from HTC. But I couldn't get it to work on unlocked firmware with Verizon so I ended up flashing the Verizon ROM and radio last year.
So I'll grab the Verizon RUU and flash that, then LeeDroid. And update my TWRP. Its long over due anyways lol
Can't thank you enough for your help. I'm going to give it a shot this weekend I think. I really want to run LeeDroid!
hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!
nubry said:
hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!
Click to expand...
Click to collapse
I don't think it will work because Samsung has anti rollback in its phones which prevents the bootloader from being downgraded. However, a system and boot flash might work. I don't know about the modem though.
Samsung is one of the few brands that implement it.
I don't really see the use though as it is quite possible to bootloop and if done incorrectly, could result in a hard brick.
nubry said:
hi, I'd like to know if there were any way I could revert back to marshmallow without bricking the device. I was thinking about rooting my phone, download the stock a520 6.0 rom zip file and flash it with the recovery menu. First I don't wanna brick it, second I'm not sure I can find some flashable zip file.
I did this with my old Motorola moto g 3 and never had any problems.
do you guys think it'll work and so where I could find those files? also if there's any other safe way to do it share it please!
Thanks in advance!
Click to expand...
Click to collapse
Quick question...
Why would you want to?
I did this with my old Moto X Play and bricked it
iloveoreos said:
I don't think it will work because Samsung has anti rollback in its phones which prevents the bootloader from being downgraded. However, a system and boot flash might work. I don't know about the modem though.
Samsung is one of the few brands that implement it.
I don't really see the use though as it is quite possible to bootloop and if done incorrectly, could result in a hard brick.
Click to expand...
Click to collapse
that is what I thought... I think the only real solution would be to find a custom Rom of the Stock 6.0 but untouched. It would not need the bootloader to be downgraded would it?
I really like samsung phones but I hate the way the treat costumers, it feels like being fooled.
Thank you for your reply though !
moozer said:
Quick question...
Why would you want to?
I did this with my old Moto X Play and bricked it
Click to expand...
Click to collapse
When I bought my Moto g 2015 it was very fast and that was surprising. All the updates started to drain the battery and make the device work slower . I tried almost all the custom Rom possible and after flashing back the stock 5.1 out of the box version I have to admit they wanted the device to become slow with all the updates.
Now when I received my A5 it was already running nougat. I think the best you can get from your phone is with the outbox version because everything is planned to be running perfectly so people buy it. For me even though it brings new features and stuff, update wont get you device any better.
So ya that's the reason I'd like to downgrade.
nubry said:
that is what I thought... I think the only real solution would be to find a custom Rom of the Stock 6.0 but untouched. It would not need the bootloader to be downgraded would it?
I really like samsung phones but I hate the way the treat costumers, it feels like being fooled.
Thank you for your reply though !
Click to expand...
Click to collapse
You could extract the system and boot out of the stock firmware, but I don't know if it's worth the risk.
nubry said:
When I bought my Moto g 2015 it was very fast and that was surprising. All the updates started to drain the battery and make the device work slower . I tried almost all the custom Rom possible and after flashing back the stock 5.1 out of the box version I have to admit they wanted the device to become slow with all the updates.
Now when I received my A5 it was already running nougat. I think the best you can get from your phone is with the outbox version because everything is planned to be running perfectly so people buy it. For me even though it brings new features and stuff, update wont get you device any better.
So ya that's the reason I'd like to downgrade.
Click to expand...
Click to collapse
Motorola got in trouble for that. Others too. It's illegal now, so you should leave out that theory.
I've had only positive experiences with my last 5 smartphones. Upgrading does precisely that...makes it better. An OEM would not produce an upgrade without testing it. That's why we had a better experience with Nougat and even better with Oreo.
What do you do differently with Oreo than you did with Nougat?