Related
I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?
roastspud said:
I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?
Click to expand...
Click to collapse
You should be able to flash back to stock using odin then upgrade or flash the updated version with odin.
Sent from my SCH-I545 using xda app-developers app
You have to unroot your device and flash the firmware with corresponding CSC to your country. On top of that you have to flash the firmware that was ALREADY officialy in your country (best way is to download package from sammobile.com) after that the OTA will work. I know because I also had problems with OTA after rooting the device.
I have reflashed the BTU UK firmware I9505XXUAMDM via ODIN and my device now shows as running official rom
Kies now says...
Your devices current firmware version is not supported to update via Kies.
What gives?
Hi,
Recovery mode mentions multi csc. Could this be the problem?
roastspud said:
I have reflashed the BTU UK firmware I9505XXUAMDM via ODIN and my device now shows as running official rom
Kies now says...
Your devices current firmware version is not supported to update via Kies.
What gives?
Click to expand...
Click to collapse
Maybe go into stock recovery and wipe data/factory reset then reboot ??
Sent from my SCH-I545 using xda app-developers app
jds3118 said:
Maybe go into stock recovery and wipe data/factory reset then reboot ??
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks.
Just tried that. Went back to recovery mode after and it said manual mode.. applied the csc again and mentioned multi csc exists
roastspud said:
Thanks.
Just tried that. Went back to recovery mode after and it said manual mode.. applied the csc again and mentioned multi csc exists
Click to expand...
Click to collapse
Recovery mode has a android bot lay down with a red exclamation mark
roastspud said:
I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?
Click to expand...
Click to collapse
Hi,
Where did you buy a "Brand New S4" with root?
Not sure what you are trying to do.
You have root, so, just flash the latest stock ROM and you are up to date.
If you are trying to get back to "Official" stock, then, look HERE
Use Triangle Away to reset your counter, and you will be able to get Ota.
Sent telepathically from my S4
malybru said:
Hi,
Where did you buy a "Brand New S4" with root?
Not sure what you are trying to do.
You have root, so, just flash the latest stock ROM and you are up to date.
If you are trying to get back to "Official" stock, then, look HERE
Use Triangle Away to reset your counter, and you will be able to get Ota.
Sent telepathically from my S4
Click to expand...
Click to collapse
I bought the phone from Amazon as new.. This is my first Android phone and I only noticed the problem when I checked the apps and it had SuperSU istalled and Kies complained about not being supported for updates.
What I am trying to do is get the phone running as stock so it will update via Kies + OTA and also remove the yellow multi CSC writing from the boot recovery menu.
I have tried unrooting and flashing stock BTU firmware but then I still have the yellow writing in the boot recovery menu and cannot update via Kies.
roastspud said:
I bought the phone from Amazon as new.. This is my first Android phone and I only noticed the problem when I checked the apps and it had SuperSU istalled and Kies complained about not being supported for updates.
What I am trying to do is get the phone running as stock so it will update via Kies + OTA and also remove the yellow multi CSC writing from the boot recovery menu.
I have tried unrooting and flashing stock BTU firmware but then I still have the yellow writing in the boot recovery menu and cannot update via Kies.
Click to expand...
Click to collapse
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.
malybru said:
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.
Click to expand...
Click to collapse
Thanks for your help so far.
Yes I have Triangle Away but no root..
malybru said:
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.
Click to expand...
Click to collapse
Ok.. here is what I have done so far..
Rooted the rom and ran triangle away to reset my counter to 1 . I have removed root and flashed stock BTU firmware then wiped data/cache from the recovery menu.
But I still have the multi csc message in stock recovery that will not budge and Kies reports the phone is not supported for updates.
Could this be because the boot loader is locked?
roastspud said:
Ok.. here is what I have done so far..
Rooted the rom and ran triangle away to reset my counter to 1 . I have removed root and flashed stock BTU firmware then wiped data/cache from the recovery menu.
But I still have the multi csc message in stock recovery that will not budge and Kies reports the phone is not supported for updates.
Could this be because the boot loader is locked?
Click to expand...
Click to collapse
Hi,
The bootloader is not locked.
You should have reset the counter to "0"
Then, flashed the stock firmware without rebooting the phone.
Does the recovery says that it "applied BTU" ? If not then your region code is not proper and that's why OTA does not work. Unfortunately it is hard to change CSC right now as Samsung has blocked the keystrings for user packages, keystrings works only for engineer builds.
And about that flash counter, it does not matter if its 100 or 0. The OTA will work as long as the status in download mode is official for both variables, and in Settings > About device is official too.
As I work at Samsung's R&D I know that you have to flash the firmware which was RELEASED for your country with proper CSC, the CSC has to be set (you can check it in recovery mode) and then both variables in download mode have to "Official" and status in About device also has to be Official. Then the OTA will work (At least over-the-air, not through Kies). Best way to check the OTA is to flash first firmware released for your country and check the updates. Ive done it dozen times on various devices and it always worked. You cannot be rooted and need stock recovery. The only major problem might be changing CSC on your own, because as I said it is not easy right now as Samsung blocked *#272* keystring in user packages (released for the market). Flashing engineering build will make the all keystrings work, but I guess you won't find any of those odin flashables on the net.
tehaerpl said:
Does the recovery says that it "applied BTU" ? If not then your region code is not proper and that's why OTA does not work. Unfortunately it is hard to change CSC right now as Samsung has blocked the keystrings for user packages, keystrings works only for engineer builds.
And about that flash counter, it does not matter if its 100 or 0. The OTA will work as long as the status in download mode is official for both variables, and in Settings > About device is official too.
As I work at Samsung's R&D I know that you have to flash the firmware which was RELEASED for your country with proper CSC, the CSC has to be set (you can check it in recovery mode) and then both variables in download mode have to "Official" and status in About device also has to be Official. Then the OTA will work (At least over-the-air, not through Kies). Best way to check the OTA is to flash first firmware released for your country and check the updates. Ive done it dozen times on various devices and it always worked. You cannot be rooted and need stock recovery. The only major problem might be changing CSC on your own, because as I said it is not easy right now as Samsung blocked *#272* keystring in user packages (released for the market). Flashing engineering build will make the all keystrings work, but I guess you won't find any of those odin flashables on the net.
Click to expand...
Click to collapse
It says applied BTU but multi CSC exists. How do I find the original CSC code out? SO its not possible to change this at all or at least get rid of that stupid message?
Is a green andriod bot with a red exclamation mark anything to be worried about?
OTA updates now work fine However they dont work via Kies. Is this normal?
FYI the flash counter was at 3 so somebody had obviously messed with this.
Sorry for all the questions. This is my first Android device having switched from Crapple
It is weird because the box was sealed and had the protectors on the phone.
Multi CSC means that the file that was flashed contains few regions code and that it can be changed inside the OS with keystring. So nothing to worry about as long as it is set to your country and OTA works. As for the icon, it is normal after entering recovery, my device also has that icon, it does not mean that there is some error. Kies does not always wants to cooperate I do not know why, but as long over-the-air works you're not missing anything apart from cable update.
tehaerpl said:
Multi CSC means that the file that was flashed contains few regions code and that it can be changed inside the OS with keystring. So nothing to worry about as long as it is set to your country and OTA works. As for the icon, it is normal after entering recovery, my device also has that icon, it does not mean that there is some error. Kies does not always wants to cooperate I do not know why, but as long over-the-air works you're not missing anything apart from cable update.
Click to expand...
Click to collapse
Thanks everyone Now I just need to find some decent apps
Have fun with Android, in case of any questions you can always send a PM
roastspud said:
It says applied BTU but multi CSC exists. How do I find the original CSC code out? SO its not possible to change this at all or at least get rid of that stupid message?
Is a green andriod bot with a red exclamation mark anything to be worried about?
OTA updates now work fine However they dont work via Kies. Is this normal?
FYI the flash counter was at 3 so somebody had obviously messed with this.
Sorry for all the questions. This is my first Android device having switched from Crapple
It is weird because the box was sealed and had the protectors on the phone.
Click to expand...
Click to collapse
Hi,
That is why I questioned the fact that you bought a phone , and it came "Out-of-the-box" with root.
This just does not happen.
Anyway,glad you got it sorted.
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
mygadgetgeek.com said:
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
Click to expand...
Click to collapse
not yet, but i have a lot of data now on my phone. will try that though. in case that doesn't work, any other advice?
cptnappy said:
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Click to expand...
Click to collapse
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
radicalisto said:
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
Click to expand...
Click to collapse
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
Ah Ok, if it says Official it should be good to go. Seems like maybe the download has gotten corrupt due to an intermittent internet connection.
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
OK, then maybe you should learn a few things before trying to update - Knox is a security system in latest Samsung phones that is supposed to be triggered/set when you root (or install any custom kernel/recovery). Your initial (old) firmware could still let you root without triggering the Knox flag, and then you can update to the latest firmware for your region using Mobile Odin Pro and still keep your root AND without triggering the Knox flag. However once you update using Samsung OTA / Odin / Kies to a firmware more recent than MJ3 you can no longer root without also triggering your Knox warrany flag - read more about this in the Universal Root De La Vega thread!
i gave up after several tries, since i'm on 4.3 i think that would do for now. maybe it's just downloading a stability update or something? everytime i do an OTA update, it tells me that the download of the new firmware is complete then reboot. when i get to 32% the droid falls flat on its back and shows the red triangle on its chest, over and over. i don't lose my phone data or anything. just won't update. i'll wait for 4.4 Kitkat instead. hope i'll be able to update to that when it comes out.
EDIT: i tried going into recovery mode, wiping cache, and factory reset.. still no dice. maybe Odin's the only way i guess. problem is my internet connection lol
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Sent3 said:
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Click to expand...
Click to collapse
i managed to update mine using Samsung Kies3 (not Kies, but Kies3). Hope updating OTA is fixed in the future with the update i just did
PLZ help me on this guys , im going mad on this
HOW TO SOLVE THE " DM-VERITY VERIFICATION FAILED NEED TO CHECK DRK FIRST " or when i install a stock rom this one first appears bUt not in reCovery " DEVICE DOESNT HAVE DRK , INSTALL DRK " ????????
it all happened after i deleted my imei then succesfully restored it with backup when downgrading from that god forsaken CM13 made by raymanFX (it was build 8 i think) , now OTAs and Security patches all face this issue in recovery when installing after being downloaded , now im in middle of nowwhere with no backup and ive tried everything but none works and im not a hacker nor an information thief just a member waiting for HELP... (SM-N910H)
:crying::crying::crying::crying::crying::crying:
! THERE IS NO OFFICIAL SAM CUSTOMER SERVICE IN MY CITY AND mobile merchants are not TRUSTWORTHY !
Someone told me that i need to find a cert file for my Phone and i found it , how is it related to DRK and what should i do with it??
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
yeah. try flashing samsung stock firmware with odin. have you done it
Sent from my SM-N920G using Tapatalk
YEP Odin flash is most of the time a good fix.
ankahuja said:
Whatever happens to the phone, if the phone turns on, doesnt have any hardware issue it can be revived.
The universal method is flashing stock firmware through odin
Download your country's note 4 firmware from sammobile and flash it through odin
Works most of the time
For any more help pm m!
Click to expand...
Click to collapse
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
ArmanFGT said:
well . odin was the first thing to try i have gone even far far away from odin and non works . but a video on youtube got my attention , a guy with a s6 edge had this problem and fixed with some sort of software (i attached it) , a friend of mine says that its sth called BOX and i dont understand him !https://www.youtube.com/watch?v=HlMQQPpqELI
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
sudhakar35 said:
The same occurred for my LG G3 D855 which has erased its IMEI just for trying 'restore upgrade errors' in the LG mobile support tool. From that onwards I have firmly decided not to flash manually in any way except when official upgrades / uupdates are released via KIES or via OTA update.
Please do not flash by your own as it is always risky. It is not a PC where you can take out the affected hard disk and fix it in a working PC and backup the data.
To all manual flashing persons :
If your phone succeeds in manual flashing, donnot brain wash others to do the same. Not all persons always do R & D in android like you.
Click to expand...
Click to collapse
Thanks for the reply but the main problem is that any OTA that comes to note 4 i download them and the device says to restart to recovery to install the Update and i say yes but when it goes to recovery the recovery wont function well since it shows dm-verity error and supported API : 3 the update process fails to complete . My imei is as cool as always i havent had a problem with IMEI since i bought the phone
at least 10000 people have note 4 and none has had the problem ???? REALLY ?
seems like im pretty f***ed up
chappatti said:
See here: http://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
Use google and search for
Note 4 DM-VERITY VERIFICATION FAILED
You get a 100 hits.
Click to expand...
Click to collapse
dear chappati , according to that video i need a physical thing which is called a BOX and a software called GC PRO because that guy had my problem and fixed it with a clicking , but im reasearching for 5 months and nothing comes out . i need information PLZ
Hi, i used to had that problem too, when i first flash a custom rom to my N910G i back up my stock rom.. everthing including EFS.. after that then i wipe everything like normal procedure when u flash a rom. till then 1 day i wanna go back to stock rom i accidentally ticked EFS while i wanna restore that stock rom back up and then i thought it was nothing serious until i flash stock rom with odin and when i boot into stock recovery that dm-verity message was shown, did so much research but no luck. my n910G was on a Singapore firmware, that time it had a update i just try my luck by downloading the latest SG firmware and then that message was gone! m now already on MM no problems like that anymore
Deleted
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'm a long time Ericsson and Sony user, LG G6 is in fact the first LG mobile I'm using.
I'm a bit confused with the LG UP tool and Uppercut (when compared to Sony's Flashtool).
My phone is P4P region, however it was shipped to me with V20c-EUR-XX firmware (3.18.71 kernel, OPR1.170623.032, PHONE_SW_FULL_VERSION LGH870AT-00-V20c-EUR-XX-AUG-17-2018+0).
It doesn't have any Play (P4P) operator branding etc.
Unfortunately OTA upgrade nor LG Bridge are unable to upgrade it to latest firmware. lg-firmwares.com suggested that I should use uppercut and LG UP software to patch it.
Question 1:
Which firmware should I use ? I assume that as long as it already has a generic firmware, any EU open firmware should work. Is my assumption correct ?
Question 2:
When flashing the selected firmware, am I obliged to do a 'wipe' or can I upgrade it without loosing personal data on the phone ? If I can upgrade, which options should be selected in LG UP tool ?
Question 3: How reliable is Backup and Recovery tool when it comes to making a backup before flashing and restoring from this backup after the upgrade ? I'd like to move to at least v20i firmware.
Thanks in advance.