Develop Bugs

[Q] Note 3 User - Moving to LG G3 - Please Help?

Dear LG Friends,
Long time XDA member, coming from the Windows Phone days HTC, then to Android HTC, bunch of Samsungs, and am now thinking about the LG space. More specifically moving from the Note 3 (T-Mobile US) running on the AT&T US, to the LG G3.
Before I do, I need some help from you guys. Which variant should I go for? I know my primary choices will be the T-Mobile and the AT&T variants (I believe they are 851 and 850)? Based on what's important to me, below, can you guys advise which variant to get?:
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
2. This is related to # 1 - But I heard that only T-Mobile has the unlocked Bootloader? However, doing some research, I believe the AT&T and the Verizon and Sprint variants can also be unlocked? Is this true? If so, are they anymore limited than the factory unlocked T-Mobile variant?
3. LTE bands - I will most likely be using the phone on AT&T US, but if development options/support are higher on other variants, I might consider buying those models, even if they are missing some AT&T bands. For the Note 3 - T-Mobile is a Pentaband phone, meaning it had all the bands needed, so it could easily work on AT&T LTE, all the time. The reverse was not true.
And basically that is it. Initial instinct says to go chase the T-Mobile variant, based on my needs above. But please educate me and help me out if I have missed something. Thank you so much in advance!

Any input guys?

ProFragger said:
Any input guys?
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
Click to expand...
Click to collapse
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates and that means missing out on necessary fixes
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it. It essentially just makes installing TWRP easier since you dont have to root before installing it unlike other variants
Nevertheless Lollipop can be rooted on all US Variants right now really easily. But the only downside to it is that removing custom roms sometimes can be a pain since you have to use a way where it sometimes works and sometimes doesnt

itsbighead said:
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it
Click to expand...
Click to collapse
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !

ProFragger said:
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !
Click to expand...
Click to collapse
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.

itsbighead said:
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.
Click to expand...
Click to collapse
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!

ProFragger said:
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!
Click to expand...
Click to collapse
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way

itsbighead said:
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way
Click to expand...
Click to collapse
This is helpful, once again bud. So how would I downgrade back to KK? Would I have to run a stock firmware of some sort? In Samsung, he Flash a .Tar file through their flashing tool called the Odin. Would that be similarly done here?

Anyone flashed the TW Lollipop ROM from Civz for the P-900 on their T-900?

I would normally just do it, but it says to flash Lollipop bootloader with oden before flashing the ROM. Never tried this before, so I was hoping someone else has been there and done that. I know all other P-900 ROMS run just fine on our T-900's and this one is probably the same.
http://forum.xda-developers.com/galaxy-note-pro-12/development/rom-civzp900lollipop-5-0-2-aroma-12-jul-t3155589

Jessooca said:
Yep. It'll work. It works better if you flash the twrp for the Note Pro 12.2 onto your Tab Pro 12.2 first though, so flash the latest twrp https://dl.twrp.me/v1awifi/twrp-2.8.7.0-v1awifi.img.tar.html for the Note Pro on your Tab Pro 12.2 then flash whichever of the Note Pro rom's you want on your tablet. They work, I've done it many times before. If you have any issues then just flash the stock tar file for your Tab Pro 12.2 via Odin.
Enjoy
Click to expand...
Click to collapse
Yes I am on hyper drive now, but this Lollipop seems like it's a different animal. I tried several different ways to get it going with no luck. I tried the note TWRP and even tried to Oden the note stock rom. Have you found a way to get 5.0 TW on our "black sheep" T-900?

Jessooca said:
I have had it on mine for a good few weeks, however it took Linux, 2 stock tar files, the latest 4.4.2 from the T900 and the recent Tab S Lollipop update, and a whole lot of trial and error to get an official ported touchwiz version to boot without issues on the Sm-t900 and due to the high likelihood someone might do something wrong and screw something up, I chose not to share it. I had to contact no less than 5 of the most intelligent experts I knew of in Android and boot loaders, kernels, etc before i even flashed it to make sure what I did would work.
Mind you this was done several weeks ago and since then I have given out the tar file to others, not on XDA that I know or work with and none of them have had a single issue with it, that I know of.
I considered putting it up on here, however again I don't have the time to work out any errors, kinks or issues that people on here might have. I also know that OFFICIALLY Samsung will be releasing the 5.0.2 update to the SM-T900 very soon, July/August/September however it's been released already to another country.
So I figured everyone has already waited this long, why take the risk of sharing it with others that I cannot or will not the time to fix or work out any errors with it. IF you do want it, PM me and I"ll share you the link, but again it's all your own risk. I can only say that for me and my friends who I have given it to, Zero of them have mentioned any problems. I myself have no issues with it on my Sm-t900.
Jessica
Click to expand...
Click to collapse
What do you mean by "It's been released already to another country" ? Wouldn't it be posted on sammobile.com ? I did send you a PM, and am sure I wouldn't have any trouble with your Tab S port if you would send a link?

Jessooca said:
I've sent you a PM, and to clarify, I was making reference to this Official NOTE Pro 12.2 Android 5.0.2 update which was released http://www.sammobile.com/firmwares/download/50030/P900UEU1COF4_P900XAR1COF4_XAR/
I
Click to expand...
Click to collapse
ok,,....,so still no link to your "TAB S PORT" you are "running on your tab pro now"

Help - Updating s4 mini i9192

I have an s4 mini i9192 4.2.2 and I want to upgrade it to 4.4.2. My current csc country is in Saudi Arabia and I cant find any updated firmware for that. How to update and which firmware can i use?

atnasan said:
I have an s4 mini i9192 4.2.2 and I want to upgrade it to 4.4.2. My current csc country is in Saudi Arabia and I cant find any updated firmware for that. How to update and which firmware can i use?
Click to expand...
Click to collapse
The only way to update is to use a Custom ROM.

Same problem for my Devise S4 mini Dous GT-I9192, Officially you will not find any Samsung Stock Rom higher than 4.2.2 the only way to look for Custom Roms the only problem you will face both Sims are on always as all Custom Roms based on CM. other problems are minor specially when you use Stable Custom Rom

Alaioby79 said:
Same problem for my Devise S4 mini Dous GT-I9192, Officially you will not find any Samsung Stock Rom higher than 4.2.2 the only way to look for Custom Roms the only problem you will face both Sims are on always as all Custom Roms based on CM. other problems are minor specially when you use Stable Custom Rom
Click to expand...
Click to collapse
I'm pretty sure the sim problem is in Nougat roms. You can turn off sims in Marshmallow.

Help
I tried to update it using the odin way and it had an error. What to do now? The other methods aren't working either.

atnasan said:
I tried to update it using the odin way and it had an error. What to do now? The other methods aren't working either.
Click to expand...
Click to collapse
which instructions are you following?
what rom are you flashing?
What was the error msg?

atnasan said:
I tried to update it using the odin way and it had an error. What to do now? The other methods aren't working either.
Click to expand...
Click to collapse
Cna you be more specific. Please?

help
android(dot)gs how to manually update galaxy s4 mini duos to android 4.4.2 kitkat
This is the site I used.
I cant remember the error msg but it popped up when I pressed start.
I have no idea what I am doing. I never tinkered with my phone before so I don't know what you mean when you say flashing a rom. I just googled how to update and I found this site. I'm a complete novice at these things.
The other methods I used are Kies and the normal way in settings.

atnasan said:
android(dot)gs how to manually update galaxy s4 mini duos to android 4.4.2 kitkat
This is the site I used.
I cant remember the error msg but it popped up when I pressed start.
I have no idea what I am doing. I never tinkered with my phone before so I don't know what you mean when you say flashing a rom. I just googled how to update and I found this site. I'm a complete novice at these things.
The other methods I used are Kies and the normal way in settings.
Click to expand...
Click to collapse
First you need to take some time to learn all about "flashing" (writing new software [firmware really] onto hardware ie chip in your phone), as doing it wrong can "brick" your phone (turn phone into a brick, yes never work again!), eg flashing wrong model number eg I9190 firmware to your phone.
I couldn't find the tutorial you mention in first 5 pages of search, do you mean this one?
http://android.sc/update-android-4-4-2-i9192xxucng2-kitkat-on-samsung-galaxy-s4-mini-duos/
strictly speaking you should not flash firmware from another region as it can stop your phone working properly. But it is possible, though I don't know about your phone or these tutorials as I haven't read them and checked all files etc
This tutorial has more info, that may help you if you decide to continue (at your own risk!)
http://techbeasts.com/update-galaxy-s4-mini-duos-i9192-to-android-4-4-2-kitkat-official-firmware/
in particular it says back up your EFS which is particular important when flashing different region in case you mess up (save to external SD & copy to PC also)
by flashing you will wipe all your personal data stored on internal SD eg photos, msg, notes, calendars etc so you need to back them up to PC (or external SD)
Kies wont let you flash that ROM as it's from wrong region (I think). Odin will though.
Nobody can help unless you give us the exact error msg + other info like Odin ver, file names etc
If you are going to flash a new ROM you might want to flash a newer custom ROM, like Cyanogenmod 13, Linage 13 or 14 (Android versions 6 & 7 respectively), you'll get new features, much better battery life, security and privacy though you will lose Samsung apps like notes etc

Help
I tried it again using the firmware from TT. This was before I saw your reply and I got this message. It was stuck for a while and I plugged in my internet adapter and it said it failed. ( in the pictures)
If you type in this,"manually update i9192 kitkat" on google, it should be the first site to come up which is the one I used.
My phone was made in china, bought in the USA, being used in the Caribbean but has Saudi Arabia codes. I don't understand. The last update from them is 2014. I used the one from Russia and TT. Both of them failed.
Should I stick with updating it to 4.4.2, flash a newer ROM ? Would this 'newer ROM' be able to work on my phone?
Or drop the whole thing because I have no idea what I'm doing?
Is there a low chance of me bricking my phone if I flash a newer ROM?

atnasan said:
I tried it again using the firmware from TT. This was before I saw your reply and I got this message. It was stuck for a while and I plugged in my internet adapter and it said it failed. ( in the pictures)
If you type in this,"manually update i9192 kitkat" on google, it should be the first site to come up which is the one I used.
My phone was made in china, bought in the USA, being used in the Caribbean but has Saudi Arabia codes. I don't understand. The last update from them is 2014. I used the one from Russia and TT. Both of them failed.
Should I stick with updating it to 4.4.2, flash a newer ROM ? Would this 'newer ROM' be able to work on my phone?
Or drop the whole thing because I have no idea what I'm doing?
Is there a low chance of me bricking my phone if I flash a newer ROM?
Click to expand...
Click to collapse
Is your phone connecting properly? There is nothing showing in the id com port window at top left, when connected properly there will be, or does that disappear when error msg shows? I can't remember. Possible it means your drivers are not installed properly, or try newer ones here (though not always better)
https://forum.xda-developers.com/showthread.php?t=961956&page=61
(scan with anti virus first)
You might want to try a newer version of Odin
Though first thing is try another usb cable. Also usb cable must always be connected to usb connectors attached direct to the PC pcb (normally at the back (or side on laptop), not an extra one like at the front and definitely not thought an external usb hub.
Your phone is probably grey market, nothing wrong with that, mine is too (mine is German phone, bought from HK used in Australia). However if pre owned it could have had other roms flashed,
It's entirely up to you which version of Android you want to use, they will all work on your phone, though anything higher than 4.4.2 will be a custom ROM, most of us here run them ie Cyanogenmod (CM) or Linage (LOS) which has recently replaced CM. LOS still has a few little issues but it is already stable, though a couple of small bugs. The good thing is you will get regular updates for many, including the monthly security updates, and they have a many new features too. To flash these you will however need to unlock your bootloader and use TWRP for the recovery.
I suggest you make a nandroid back up as soon as you install TWRP, then you can always go back to your current setup.

Alaioby79 said:
Same problem for my Devise S4 mini Dous GT-I9192, Officially you will not find any Samsung Stock Rom higher than 4.2.2 the only way to look for Custom Roms the only problem you will face both Sims are on always as all Custom Roms based on CM. other problems are minor specially when you use Stable Custom Rom
Click to expand...
Click to collapse
Where we can find samsung official ROMs? There is some 4.4.2 roms available in
http://www.sammobile.com/firmwares/database/GT-I9192/

hnikaein said:
Where we can find samsung official ROMs? There is some 4.4.2 roms available in
http://www.sammobile.com/firmwares/database/GT-I9192/
Click to expand...
Click to collapse
not for S4 mini Dous GT-I9192, all Stock ROMs for our devise is only 4.2.2

Alaioby79 said:
not for S4 mini Dous GT-I9192, all Stock ROMs for our devise is only 4.2.2
Click to expand...
Click to collapse
in this page you can also see we can upgrade to 4.4.2:
http://www.gsmarena.com/samsung_i9190_galaxy_s4_mini-5375.php

hnikaein said:
in this page you can also see we can upgrade to 4.4.2:
http://www.gsmarena.com/samsung_i9190_galaxy_s4_mini-5375.php
Click to expand...
Click to collapse
Samsung said it will update to 4.4.2 but it did not, GSMARENA.COM sometimes not offering or updating to actual status and I had communicated with SAMSUNG but no reply from them however S4 mini is from S-Line which shall be more valuable to SAMSUNG but they did not care.

Alaioby79 said:
not for S4 mini Dous GT-I9192, all Stock ROMs for our devise is only 4.2.2
Click to expand...
Click to collapse
Maybe you mean in some regions. Because otherwise your statement is completely false. I had the 4.4.2 stock firmware on duos for instance.

xdmusicbx said:
Maybe you mean in some regions. Because otherwise your statement is completely false. I had the 4.4.2 stock firmware on duos for instance.
Click to expand...
Click to collapse
Yes for some region only not for all variants

Help me
Yes, it's connected properly. It is highlighted blue by ID:COM before the error occurs. I just installed the drivers you sent me.
I did the update with the latest Odin and I still got the error message.
Only my original cable connects to the computer so I cant try any others. Once it's connected and appears in 'my computer', doesn't that means its connected?
It wasn't pre-owned but how would I know if a ROM is already installed?
I think I want to upgrade to the 4.4.4 and IF I get it to work, I will then upgrade to the latest one. I'm assuming this is easier and since I have no idea what I'm doing or where to go, I should definitely go with the easiest first. Right ? You lost me at Cyanogenmod. This is guy stuff.
Can you direct me where I need to go please with some instructions ?
Thank you

you should quote msg or use @atnasan to be sure your reply is seen by other poster.
If I remember correctly (it's been a long time) when odin gets stuck at get pit it is normally a communication issue even though your phone appears to show up correctly in it. You must run Odin with full admin rights on your pc. Some used to say only the Odin for S4 Mini & ver 3.07 or 3.09 (I think it was) would work (see the S4 mini Odin thread) Some firewalls can cause issues so turn them off (maybe reboot with antivirus off). You need a usb port that connects direct to the motherboard & original usb cable (really just needs a good quality cable in good condition, I think, just not one of those thin $5 ones).
If that doesn't work try to borrow another USB cable or try another PC or laptop.
Luckily I've never had any issues, all Odin ver worked, I just right click on Odin to run as admin from my user account on Windows 7 64bit even with Zonealarm firewall running. But other people have had problems.
No need to update to 4.4.2 etc if you will try to install a custom ROM like Linage or Cyanogenmod or one of the more customised . (in fact on my I9195 updating to 4.4.2 loaded a new bootloader, which had a stronger ver of knox)
If Odin won't flash stock you can try flash TWRP with Odin then use that to try flash a custom ROM from your sd card using TWRP instead of using Odin. Use TWRP from the neozone75 thread, I am using the tryout ver 3.1 which is working perfectly, so I suggest that. (ver 3.0..3 gave me errors checking the md5, though most people don't both with that check, so would work). Linage OS is about to change official version from LOS13 to LOS14 (Android 6 & 7) so you might want to wait a week or so if you choose that ROM, as I don't think there will then be any updates to LOS13 after that as each phone on LinageOS downloads section only has 1 Android version supported.

Can you install Lineage OS on Samsung Note 2 Verizon (SCH-I605)?

I'm planning on running Lineage OS. I was wondering if I can load Lineage OS on my Note 2 device. I would hopefully like Mobile Services like LTE and calling/texting to work, wifi too. Help please!

You should make a TWRP backup and try the build for t0lte.
If it doesn't work then restore your backup.

Option58 said:
You should make a TWRP backup and try the build for t0lte.
If it doesn't work then restore your backup.
Click to expand...
Click to collapse
Thanks! But you know... I'm a little bit new to this. What is t0lte mean and would verizon work with this (LTE and WIFI and also texting and calling.
Why I'm new is because I used to hack around with my old kindle tablet and I just got my first android phone (used to have an iPhone 6). So I check the lineage OS website and I didn't see one for SCH-I605, so I thought there would be no options. But thanks!

piggyuniform said:
Thanks! But you know... I'm a little bit new to this. What is t0lte mean and would verizon work with this (LTE and WIFI and also texting and calling.
Why I'm new is because I used to hack around with my old kindle tablet and I just got my first android phone (used to have an iPhone 6). So I check the lineage OS website and I didn't see one for SCH-I605, so I thought there would be no options. But thanks!
Click to expand...
Click to collapse
The galaxy note 2 has a few versions, the two biggest are the international version (t03g/GT-N7100; doesn't support LTE ), (t0lte/GT-N7105; supports LTE). I personally don't suggest you install lineage for t0lte but you could try and give it a shot. it has been known that kernels for the n7105 can work on the i605 so I don't see why a rom wouldn't be able to work since the differences between the devices are minimal. I doubt you will be able to install it though since there should be a device check within the updater script that prevents you from installing the ROM but you can look it up on how to remove this checking if you REALLY want to install it. Be careful if you flash the rom, make sure you do a TWRP backup of the system and data to be on the safe side.
Regards
EDIT: There seems to be a few people who has had some success when installing lineage t0lte for the i605. I still advise against it but at least now you know that it may work for you.

Valkyrie146 said:
The galaxy note 2 has a few versions, the two biggest are the international version (t03g/GT-N7100; doesn't support LTE ), (t0lte/GT-N7105; supports LTE). I personally don't suggest you install lineage for t0lte but you could try and give it a shot. it has been known that kernels for the n7105 can work on the i605 so I don't see why a rom wouldn't be able to work since the differences between the devices are minimal. I doubt you will be able to install it though since there should be a device check within the updater script that prevents you from installing the ROM but you can look it up on how to remove this checking if you REALLY want to install it. Be careful if you flash the rom, make sure you do a TWRP backup of the system and data to be on the safe side.
Regards
EDIT: There seems to be a few people who has had some success when installing lineage t0lte for the i605. I still advise against it but at least now you know that it may work for you.
Click to expand...
Click to collapse
Thanks for that, now I understand! I've been stuck on one route for the past while though. Since the I605 uses Verizon which has a locked down boot loader... I've been trying to run Suck It Verizon and No You Verizon. Im kind of worried if I will get soft bricked, which is fine because I can flash stock recovery, but if I get hard bricked, I'm screwed for sure. So I've been trying to load a android 4.1 or 4.1.1 or 4.1.2 stock rom but I can't seem to do that because I run 4.4.2, as of that I already have No you Verizon (Android File Host has working downloads for it right now). If you know what I mean, have you gone through this trouble before (or parts of it?), because I am in horrible pain lol.

No joy on the t0lte LineageOS. It fails the device check.

Check the Verizon forum for possible solutions: https://forum.xda-developers.com/note-2-verizon

downgrade 8.0 to 6.0 a520

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?