Hello! I have just upgraded to Android M and I have two quick questions: 1 is , is it a problem if my system did not have any problems updating , even though I am S-OFF and my boot-loader is unlocked, this system being installed from a zip? 2 is, I do not have the brightness bar in the notification area, and that is a feature I used to use a lot, yet it isn't there, and I can't find it anywhere in settings. Please help on the second one and tell me if this is supposed to happen or not, also BTW in the boot loader it says System status: official, but it is S-OFF and the boot loader is unlocked.
1-Did you unlock the bootloader or it was unlocked when you got the phone? maybe you have the developer edition phone.
2-I think this option is not available for the M9+ you need to use an app like Brightness slider control or any other app from google play
Reply
About your first question: I was the one who unlocked the boot loader because I had the clean slate ROM installed and just reverted to stock, yet the stock ROM was a very old version and because it was S-OFF and the boot loader was unlocked I feared that I might not get the marshmallow update, yet I decided to try and install the update anyways, and to my surprise it worked flawlessly. Is this normal lol
Related
Hi everyone, I´m really pissed about that issue; I´d really appreciate any help and thanks in advance to you all.
Story: I was using Sva´s rom for kitkat, everything normal, then I´ve seen Sasikas´s for lollipop and decided to try it out. I flashed the original firmware and then the custom, both via odin, used them normal as usual. For some reason, I decide to compare the new sva´s, also for lollipop and when I tried to flash, THE ISSUE BEGAN!
Issue: after doing the normal odin process, when the message “complete” shows up and the phone reboots, the bar of updating progress stop about 25% and the phone reboot to the normal mode, but only with a black screen. This is the screen I´m talking about: 3w generacionandroid.com/wp-content/uploads/2014/09/Android_updating.jpg
What I already tried and it didn´t work:
1 – factory reset after the “boot”; I think the problem is that the “system isn´t being write” so …
2 – different roms, both custom and stock; something interesting about this is that the point of the bar that resets the phone varies according to the rom I use, just as follow:
Rom lollipop: at 25% of the bar the system restarts;
Rom kitkat: the bar jumps from 25% to the end and boots the system until Samsung logo. I noticed that the carrier logo sound is cutted in the end.
I can freely install any recovery and enter dl mode.
By the way, the bootloader file must be flashed at pda or bl in odin?
Flash the bootloader file in the BL slot.
about the bootloader...
I´ve installed a bootloader to try the new lollipop in sva´s rom, maybe because of this I can´t flash anymore? I´ve found this info about bootloaders, could someone tell me if I´m thinkg right about it?
"In literal terms, bootloader is code that is executed before any Operating System starts to run. "
This way what I need is a bootloader for kitkat or previous? Where can i find it?
cry for help
almost givin up...
so, happy new year to everyone, I´ll wait until January to check any replies, otherwise selling for parts. ='[.
Shortening: I can enter recovery and dl mode BUT not getting to install roms;
I know I fixed selinux permissions once and installed a bootloader said to be to install a version of lollipop, that´s all new stuff I did.
I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
My phones info;
Software status: Modified
Android Security patch level: May 1 2016
Baseband version: M8992_1253331 .29.01.88.02R SUPER_NA
Kernal Version: 3.10.84-perf-g329ac5f
[email protected] #1
Thu Apr 21 00:11:23 CDT 2016
System Version: 24.221.4.clark_retus.retus.en.US.retus
Build Number: MPHS24.49-18-4
The pending update: New version:24.221.8.en.US
Thank you.
u need to flash official factory image inorder to get the updates
i hardly recommend you to use fastboot and install stock firmware from this site
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick...
install the latest firmware and then check for updates
if u have any queries then go through this.... make sure that u don't mess up
https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Cjet said:
I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
Click to expand...
Click to collapse
If I understand your post correctly, and the COMPLETE firmware image was flashed, then you should have no issues taking an OTA update... the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt.
Try this, before you accept and download the update, boot into stock recovery and wipe cache. Or better yet, do a full factory reset and accept the update and apply it, then let it boot fully, do another factory reset and then set it up clean.
I don't know why this happens... it just seems like a few every update won't take it no matter what we do, and for we do not have the latest full factory image yet so there isn't much we can do to find another way.
Thank you both for your reply. However, I am still not clear on something.... there seems to be confusing/conflicting advice regarding the Software "Modified" status and it's role in accepting updates.
1. "if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick..."
2. " the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt."....... If the Software status says "modified" doesn't that mean that the system is indeed modified, and that trying to load the OTA in this state will result in a bootloop? .
u neee to flash official firmware.... the only way to remove modified and change it to official....
it actually doesn't matter that if bootloader is unlock u can install the updates...... i was on may patch and i also wanted to change the software status from modified to official in order to get sept patch... but in moto firmware center the latest was feb 2016.... so i had to downgrade... i tried and it worked... then i was eligible for ota and yes im on sept patch
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Prazaar said:
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Click to expand...
Click to collapse
I disagree... it CAN go back to Official, I had several ROMs on my device, then flashed stock image and somehow mine went back to Official. Was mine a fluke? I don't know, but it is clearly Official now. Note the picture clearly shows the bootloader was unlocked (Status 2) and I had at least dozen different ROMs flashed over time before going back to stock using the May 2016 security image and then successfully OTAing up to October security update.
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.
I know what you mean. My Software status is with LineageOS "official" i can flash every rom an the status stuck in official.
Factory img is no warranty for official status but also makes no difference for ota
Getapatalkt vom meinem Moto X Style
thebaconbox said:
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Click to expand...
Click to collapse
Because I am new to all of this and don't know anything about custom Roms. All I want to do is get this thing back to stock.
[/QUOTE
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.[/QUOTE]
Wow, thanks everyone for the suggestions and patience!
OK, so the software status does not affect OTA update installation. Software status being modified does not necessarily mean that the SYSTEM is modified. Yet if the SYSTEM is modified then taking the OTA update will cause a softbrick.
How can I tell if my SYSTEM is modified before deciding on taking the OTA update?
I have had the official Motorola firmware flashed/reinstalled previously by friend's son, and that didn't take the OTA update. It caused soft brick (No Command error bootloop)
I then went to the Motorola site myself, downloaded the firmware and flashed/reinstalled it. This is where I am currently, trying to decide if I should take the update or put it off until I have a couple of hours free to troubleshoot in case the OTA softbricks this thing again (it takes me much, much longer to figure this stuff out than it does for you guys. )
And if that does soft brick it again, then I am not sure what I am doing wrong with the flashing. So, is there any way for me to check to see if the SYSTEM is modified before I try the update.? Thank you!
Sagar_1401 said:
u neee to flash official firmware.... the only way to remove modified and change it to official....QUOTE
This was done twice and still says modified
Click to expand...
Click to collapse
Status modified will change to official after an OTA update.
Sent from my XT1572 using Tapatalk
Anyone? No one knows if there is any way for me to check to see if the SYSTEM is modified before I try the update.?
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Prazaar said:
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Click to expand...
Click to collapse
I don't understand what you are saying. I cannot see "what" if it is modified? Edited - removed earlier rant.
(Sorry)
SOLVED.....
Today I backed everything up, bit my lip and hit "install update". It did update the phone and it did change the software status to "Official". I did this with the bootloader unlocked, and it worked . It does say Status Code 3, and the bootloader unlocked warning screen on startup appears, both of these I am guessing is normal. Everything seems good.
Hi... I have updated my phone to LineageOS successfully but I lost fingerprint option. I'm getting system update options in Settings but when I tried to update the stuck in bootloop and I was able to get it to work by entering some codes in this forum... First, I have unlocked the bootloader and rooted my phone and installed TWRP and flashed LineageOS. All went good but I lost the fingerprint option and auto rotate and some features are not working properly. If I want to update it again to the latest version, do I have to unlock bootloader, root again? Please help... My phone was good before I updated it
Kishorechittem said:
Hi... I have updated my phone os successfully but I lost fingerprint option. My concern is how to update os again as I have already unlocked bootloader and rooted my phone
Click to expand...
Click to collapse
Which os did you update and which rom was it before. Please tell exact versions and if you have the regarding links.
Normally that happens without the right firmware like marshmallow before installing a nougat rom. But let's see what's the problem of yours.
Hello, guys.
Recently, i wanted to install the fulmics ROM (which is awesome) on my LG G6 H870.
So, i've done it, the bootloader has been unlocked, it's rooted right now, and i've got the Fulmics ROM which works perfectly.
But, i still have a question. When i boot up my phone, i've got this message :
"Your device software cannot be checked for corruption. Lock the bootloader. etc..."
This isn't a problem, because i can boot up my phone.
But i just wanted to know if i can remove this message, and how ?
Thank you all for your answers and your help.
This is normal and cannot remove that message. Just ignore it, how many times do you actually reboot for it to be an issue? If you ever need send phone off for repair just flash stock and lock bootloader again.
normal bro don't worry
[/COLOR]
basicreece said:
This is normal and cannot remove that message. Just ignore it, how many times do you actually reboot for it to be an issue? If you ever need send phone off for repair just flash stock and lock bootloader again.
Click to expand...
Click to collapse
dude I've got a question: if you wanted to get your bank's app working again in a custom rom/recovery is it possible to relock the bootloader in order to get older compatibility (mario kart, spotify options, bancoestado) but in a system like PA Quartz 3 or PixelExperience ? Or bootloader wont boot locked another system than LG?
I seriously need those apps but also need Android 10
learning_to said:
[/COLOR]
dude I've got a question: if you wanted to get your bank's app working again in a custom rom/recovery is it possible to relock the bootloader in order to get older compatibility (mario kart, spotify options, bancoestado) but in a system like PA Quartz 3 or PixelExperience ? Or bootloader wont boot locked another system than LG?
I seriously need those apps but also need Android 10
Click to expand...
Click to collapse
Magisk manager and use the magisk hide feature.
My brother has a RETIN Athene running stock ROM with latest April patch and he's been complaining about frequent ghost touches. He'd often find his phone call, text someone at random, apps opening automatically and what not. I've suggested him to do a factory reset but I'd like to know if this can be solved without a factory reset. I had already unlocked his bootloader earlier to let him try a custom ROM as the stock was getting sluggish so if needed, a fastboot ROM can be flashed as well if it comes to that.
He recently got a QC 3.0 charger from Motorola but the problem has been going on before that (if he recalls correctly). Could this be because of the charge as I remember his G4 plus had some occasional ghost touches when his phone was new but that only happened while it was being charged.
I'm open to any advice and tips. His phone is barely usable now.
Update: I did a cache wipe from recovery a few minutes ago and noticed that his recovery was showing the the following info:
oem_locked
Software status: Official
Maybe I relocked the bootloader when flashing stock back then. Do I need to unlock bootloader again with "fastboot oem unlock"?
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
gioyocho said:
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
Click to expand...
Click to collapse
I see... I'll tell him to change the brightness to auto. Do you think upgrading to a new phone is better and the only available solution?
Also, after I flashed the fastboot ROM a while ago, he has updated to all the following OTAs without any issues, that's how he's on the April patch. No hard brick, nothing.
gioyocho said:
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
Click to expand...
Click to collapse
You can relock your bootloader. And the bricking kicks in only if you flash OTAs when rooted or on a custom recovery. Generally when you have system modifications.
corlatemanuel said:
You can relock your bootloader. And the bricking kicks in only if you flash OTAs when rooted or on a custom recovery. Generally when you have system modifications.
Click to expand...
Click to collapse
Well, no system modifications were done. That's why the OTAs were successful