My plan when the 5.1 update comes is to wait for someone to release the files, which hopefully will happen soon after the update if people will use Motorola Device Manager to update to get the files.
Then once the 5.1 system.img is pre-rooted, I would flash that along with the 5.1 kernel/radios but leave the bootloader and partition table on 5.0 until we know if mofo.exe works on 5.1. This may or may not be stable doing it this way, I will have to see. And mfastboot may or may not have checks in it to prevent me from flashing the 5.1 kernel/radios with a 5.0 bootloader/partition table, idk.
I don't think that 5.1 bootloader should have patched whatever exploit mofo.exe takes advantage of since mofo.exe was not even released until after 5.1 was released on the Nexus 6. I doubt there was time for Motorola to patch this or even figure out what mofo.exe is doing.
Thoughts anyone? And if someone is planning on upgrading to 5.1, please use MDM and post the files!! Thanks!
Edited - would I need to flash the 5.1 recovery too?
Edited - maiko1 has posted that MoFo won't work on 5.1 so that is something to think about before upgrading.
I'm also waiting for 5.1, and assuming it can be used with mofo, I _WILL_ go and buy mofo))
Reminder - if you upgrade to 5.1, YOUR VERSION OF MOFO.EXE WILL NOT WORK ON 5.1. This is because the way maiko1 has configured things - your version of mofo.exe will only work on 4.4.4, 5.0 and 5.0.2 bootloaders. He needs to make some changes to the purchase process to allow you to redownload (for free) a new version of mofo.exe that will work on 5.1 because mofo.exe not only checks your device serial number but also checks the version of the bootloader you are running.
So you will not be able to use mofo.exe if you upgrade to 5.1. You will need to wait for maiko1 to make the necessary changes to his site to allow you to redownload an updated copy of mofo.exe that will be able flash your device once you have a 5.1 bootloader.
I just wanted to give everyone using MoFo a heads up here - maiko1 hasn't been responding to emails and hasn't been on XDA for a week. So if you upgrade to 5.1 and need to wait on maiko1 to make his updates before you can redownload a copy of mofo.exe that will work on the 5.1 bootloader, there is no telling how long it will take for him to make his updates.
The problem is not just that maiko1 is not responding lately, we also will have to wait for the 5.1 fxz to show up. This is true for the XT1096 users even if we just want to flash modified 5.1 system images w/o updating the bootloader. The XT1097 users can likely modify the Pure Edition 5.1 system.img.
Well the update still hasn't arrived !
@maiko1 has edited the OP of the MoFo thread to say that MoFo doesn't work on the next update Idk if that is 5.1 or the minor 911 bug.
Wasn't the 911 bugfix update only for the 2013? Unless we got one too (I froze the OTA app in TiBU but haven't heard of the 2014 getting it).
As much as I'd like to have 5.1, my plan is to wait until a flashable 5.1 image with root and xposed becomes available. Now that I have root, I don't want to give it up even for 5.1.
I got an invitation for the 5.1 soak test from Motorola today. I'd like to help, but I don't want to lose root.
I got an invitation also. Not going to accept it unless it can be MoFo'ed
Can I have your invitation Ive never even rooted this phone lol
Sent from my XT1096 using Tapatalk
Temporary root from Kingroot on att running lollipop xt1097
I obtained root using kingroot on my att xt1097, it was temporary, about 5 minutes. Has anyone use kingroot? I root on the first try, then I thought I did something wrong so I tried it again and it didn't work... Tried it like 15 more times and it worked again tried to install binaries with supersu and rebooted and lost it again. Repeated the process again and keep losing the root. Any ideas?
Not sure if anyone got back to you on this but, kingroot is a temp root, it doesn't last past a reboot. I'm not entirely sure it'll even stay during a session on the moto x at all. Our phone, (last I checked) wasn't officially supported by the kingroot app yet.
It appears the 5.1 update is live for soak testers...hopefully someone can get the files for you guys to test out MoFo
So allow OEM unlock is under developer options... Not near a pc to attempt it. That is if it works similar to my n6 and is as simple as fastboot OEM unlock
GatorsUF said:
It appears the 5.1 update is live for soak testers...hopefully someone can get the files for you guys to test out MoFo
Click to expand...
Click to collapse
For xt1096??!! Haven't got my update yet
tacosrdelicioso said:
For xt1096??!! Haven't got my update yet
Click to expand...
Click to collapse
Yep. Seems smooth. I hope it means unlocking will soon be possible. It would be like having a mini nexus 6 lol
And tried to unlock... Need code. Motorola won't give it up. Dang them.
I got the ota uploading to drive. Once it's done I'll post a link so someone can check it out.
---------- Post added at 08:12 AM ---------- Previous post was at 07:59 AM ----------
https://drive.google.com/file/d/0B-05eXAx4kW7aFV3Z3I0OG4yUU0/edit?usp=docslist_api
Soak ota
shane1 said:
I got the ota uploading to drive. Once it's done I'll post a link so someone can check it out.
---------- Post added at 08:12 AM ---------- Previous post was at 07:59 AM ----------
https://drive.google.com/file/d/0B-05eXAx4kW7aFV3Z3I0OG4yUU0/edit?usp=docslist_api
Soak ota
Click to expand...
Click to collapse
@JulesJam go go go
I didn't take the update for obvious reason, does anyone know if this updates bootloader?
Does anybody know if I will have problems if I install the OTA if I am currently rooted with MoFo? I understand that I will likely lose root, but will I brick my phone or anything?
bhmcarr said:
Does anybody know if I will have problems if I install the OTA if I am currently rooted with MoFo? I understand that I will likely lose root, but will I brick my phone or anything?
Click to expand...
Click to collapse
your phone would have to be running a stock system image for the update to even install. if you have anything in the system thats altered it will halt the update and fail. I dont know if just having root will stop it.
Related
FXZ SU4.21 Thanks to @stras1234 for the initial FXZ! Thanks to @Skrilax_CZ for posting them to the SBF site!
Use my RSD Flasher to flash it.
I guess it still needs to be spelled out in this day and age, but, yes, you WILL lose root if you use this. It's an FXZ that overwrites all partitions with stock. So uh, yea, there's that.
I love you.
In a not creepy way.
Sent from my XT1080DE
LOL you're welcome.
Thanks, I hope somebody finds a way to root it.
LMAO! It's not even out of soak yet. Here are the challenges you face for root on a locked bootloader:
1. Finding a new priv escalation vulnerability that works on the kernel that ships with 4.4.4. The pie exploit no longer works.
2. Finding someone to exploit the vulnerability once you find one that applies.
3. Finding a WP off exploit so you can persist su to the system partition for permanent, non-tethered, root.
I'm gonna say that's probably not all going to happen "soon". ROFLMAO
SamuriHL said:
LMAO! It's not even out of soak yet. Here are the challenges you face for root on a locked bootloader:
1. Finding a new priv escalation vulnerability that works on the kernel that ships with 4.4.4. The pie exploit no longer works.
2. Finding someone to exploit the vulnerability once you find one that applies.
3. Finding a WP off exploit so you can persist su to the system partition for permanent, non-tethered, root.
I'm gonna say that's probably not all going to happen "soon". ROFLMAO
Click to expand...
Click to collapse
v4.4.4 would not install and this fixed it ... all without losing any data ... big thanks!
NP enjoy! Stras1234 is the man for giving me the FXZ and allowing me to post it.
SamuriHL said:
LMAO! It's not even out of soak yet. Here are the challenges you face for root on a locked bootloader:
1. Finding a new priv escalation vulnerability that works on the kernel that ships with 4.4.4. The pie exploit no longer works.
2. Finding someone to exploit the vulnerability once you find one that applies.
3. Finding a WP off exploit so you can persist su to the system partition for permanent, non-tethered, root.
I'm gonna say that's probably not all going to happen "soon". ROFLMAO
Click to expand...
Click to collapse
Well, not easy! so far Im not needing root access, there are no roms and wifi tether works for me without doing anything, Im using the phone outside US of course. I would like to remove some bloatware.
I love modding and all that things but Im happy with stock kitkat. I think we could get android L sometime in the future.
SamuriHL said:
FXZ SU4.21 Thanks to @stras1234!
Use my RSD Flasher to flash it.
Click to expand...
Click to collapse
Great work samurihl! This isn't even out of soak and we already have the fxz!
I have no doubt these phones will get L. They'll only be a year old at that point so I'd not worry about it.
Does anyone know if you have to edit the xml file and remove the getvar line like in 4.4? Or just RSD Lite and go?
Is it supposed to take forever to flash the system.img?
I've let it go for between 5 and 10 minutes, and it's still on system.
ad fu said:
Does anyone know if you have to edit the xml file and remove the getvar line like in 4.4? Or just RSD Lite and go?
Click to expand...
Click to collapse
That's why I gave a link to my tool. It does all that for you plus allowing you to keep your data.
LunaticSerenade said:
Is it supposed to take forever to flash the system.img?
I've let it go for between 5 and 10 minutes, and it's still on system.
Click to expand...
Click to collapse
Yes, it's over a gig in size. It takes a while.
SamuriHL said:
That's why I gave a link to my tool. It does all that for you plus allowing you to keep your data.
Yes, it's over a gig in size. It takes a while.
Click to expand...
Click to collapse
Ah. Makes sense. Thanks!
Samuri thanks a lot I love you to but in a creepy way . This has to be a record for an fxz being available.
Sent from my XT1080 using XDA Premium 4 mobile app
Yea, stras1234 rocks on that FXZ front. He got the HD/M FXZ's early for us last time, too. You checked out my new tool yet, btw? I made it as easy to flash FXZ's as possible now.
Not yet I saw you were working on it. I will check it out when I get home and use it. I always like to run a fxz after an update.
Sent from my XT1080 using XDA Premium 4 mobile app
It's pretty simple to use.
I would like to know if this is the final version or when the final ota update is released there will be another?
I take it you don't know what a soak test is? Unless something goes wrong, which is unlikely, this will be pushed OTA in the next few days.
I am not sure what is holding up the root.. Or 5.1, but assuming that a bootloader unlock is not going to swiftly follow the root do you guys think the root will be released in 4.4.4 or will we have to wait until 5.1 is out in the wild for the turbo?
aka848 said:
I am not sure what is holding up the root.. Or 5.1, but assuming that a bootloader unlock is not going to swiftly follow the root do you guys think the root will be released in 4.4.4 or will we have to wait until 5.1 is out in the wild for the turbo?
Click to expand...
Click to collapse
Nobody really knows anything at this point about root, bootloader unlock, or the Lollipop update. I'm assuming (more often than not, though, assumptions are not correct) that the root will be released on KitKat as that is what it was tested on (in the videos you can see he's using KitKat, not a prerelease Lollipop build or anything).
Droid Turbo video uploading to the Root Junky YT channel tonight, according to RJ's G+ post. Here's another post:
EDITED - an XT1095 owner on the 60.16 bootloader from a 5.1 soak bricked when he downgraded to 4.4.4 then took the 5.0 OTA. Several Brazilian XT1097 owners have done the same on the 60.14 or 60.16 bootloader.
THERE IS NO REASON TO DOWNGRADE TO 4.4.4 AFTER TAKING THE 5.1 SOAK IF THE 5.0 STOCK IMAGES ARE AVAILABLE FOR YOUR DEVICE!!!! Just flash the 5.0 stock images instead (system, kernel, modems, baseband, recovery - but not bootloader (motoboot) or partition table (gpt)).
Quite a few posters on the Q&A forum have hard bricked by taking the 5.1 soak, then downgrading to 4.4.4 then taking the 5.0 OTA. And unfortunately, the files that are necessary to restore their bootloaders are not available.
Obviously, taking an OTA after downgrading is dangerous. I would only flash the firmware myself or use Motorola Device Manager to upgrade if you have downgraded in the past.
Update - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I would not take the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
The bricks are caused when doing OTA after a downgrade. Not when flashing.
Sent from my XT1095
eqjunkie829 said:
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
Click to expand...
Click to collapse
It happens when they downgrade to 4.4.4 then take the 5.0 OTA as stated in the OP.
AGISCI said:
The bricks are caused when doing OTA after a downgrade. Not when flashing.
Click to expand...
Click to collapse
Right, so I would never take an OTA after downgrading - I would only flash the firmware or use MDM (which is the same as flashing but has checks in it).
,,,
wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
I've gone back and forth a few times on my 1095 and the one thing I notice is my software status always says official.
Click to expand...
Click to collapse
I responded in the other thread.
wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
Click to expand...
Click to collapse
The issue is with taking the 5.1 soak, downgrading to 4.4.4 then taking the 5.0 OTA. The OTAs are supposed to fail if your system and recovery are not stock. I am sure the issue is taking the 5.0 update with the 5.1 bootloader and partition table - the OTA updater script does not adequately protect you from a hard brick when you have a higher version BL and PT than the system/recovery version you are running.
You simply cannot downgrade the bootloader despite what some people are saying here - it doesn't happen. Neither fastboot nor mfastboot will downgrade your bootloader. If people were on 5.0 system and then went back to 4.4.4 system and they are still on the 4.4.4 bootloader, then it is because they never successfully flashed the 5.0 bootloader. If they had successfully flashed the 5.0 bootloader, their bootloader would not flash back to the 4.4.4 bootloader using either fastboot or mfastboot.
What is going on with the OTAs that I have seen is that once you upgrade to 5.1 via the soak OTA, you flash back to 4.4.4, which will flash your system/kernel/ramdisk/modems/baseband/recovery back to 4.4.4 but not your bootloader or partition table. Then when they take the 5.0 OTA, which is a patch, the OTA updater script is trying to patch the 5.1 bootloader and partition table as if they were the 4.4.4. This should never happen - it is totally a Motorola mistake. The 5.0 updater script should detect that the person is on a different version bootloader and partition table than 4.4.4 and it should fail rather than hard brick the phone. But it doesn't.
It is infuriating that these people are hard bricking due to Motorola's bad coding and they are being denied warranty service due to having rooted. Root has nothing to do with it - the OTA updater scripts should be coded to fail if the person is on the wrong bootloader and partition table.
wolfu11 said:
The one thing I notice is my software status always says official.
Click to expand...
Click to collapse
Your qe however will show you have rooted in the past if you have ever rooted before.
[,,,
wolfu11 said:
Okay but when I've down graded before and after I sign into kitkat I get a message in the status bar saying to downgrade the firmware I click okay and it reboots. What is that downgrading?
Click to expand...
Click to collapse
Not the bootloader and partition table. I explained that in my other thread.
,,,
wolfu11 said:
That doesn't answer the question, which was what does it downgrade? Anyone know ?
Click to expand...
Click to collapse
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
JulesJam said:
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
Click to expand...
Click to collapse
Actually you didn't nor did anyone else, I'll just downgrade again and see what that Motorola firmware thing is all about.
No big deal since my phone doesn't seem to brick anyway.
wolfu11 said:
Actually you didn't nor did anyone else,
Click to expand...
Click to collapse
Yeah I did, but I am not repeating it b/c I am tired of spoonfeeding people who don't know basic things yet want to argue with me. You can read the thread or don't. No sweat off of my back either way.
wolfu11 said:
No big deal since my phone doesn't seem to brick anyway.
Click to expand...
Click to collapse
Because you aren't downgrading your BL or PT, lol!
Anyhow, please stop cluttering this thread. I suggest you read and learn what you are flashing then you will know. And please don't encourage other people to do dangerous things with their device when you don't even know what it is that you did with yours.
,,,
wolfu11 said:
Was just curious if you actually downgraded yourself
Click to expand...
Click to collapse
Why would I do something stupid?
wolfu11 said:
or was going by hearsay.
Click to expand...
Click to collapse
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
wolfu11 said:
I won't clutter your thread any longer
Peace
Click to expand...
Click to collapse
Thanks.
JulesJam said:
Why would I do something stupid?
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
Thanks.
Click to expand...
Click to collapse
That clears up a lot .
Thanks
FYI - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I am not taking the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.
Heads up peeps - the XT1095 5.1 soak OTA updater script does not have adequate checks in it to prevent a hard brick if you have downgraded and then attempt to upgrade again.
http://forum.xda-developers.com/showpost.php?p=60941697&postcount=132
So this is just like the Brazilian XT1097 5.0 OTA.
Please read the edit to the OP!!!
This happened to me and I'm so frocking pissed I didn't see this thread beforehand!! Does anyone know if a JTAG service could fix this or how Mich Motorola would charge to repair?
*EDIT*
Disregard PSA, SunShine works on SU4TL-44 and SU4TL-49 now.
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
Where is this or what is this beta u speak of?
Sent from my XT1254 using XDA-Developers mobile app
hm,i only choose to update the offical mm...but thx to warning us
gangrenius said:
Where is this or what is this beta u speak of?
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a soak test.
No! It's a OTA update. You should have it right now. Check for updates. I just installed it last night with no problems. I installed a stock rom. Ran the update, Then rooted again. Simple
@ChazzMatt is speaking of the Marshmallow soak test. @smooth781 is speaking of the Droid Turbo OTA that is still 5.1 (23.21.49.en.US). Both were mentioned in op.
jcase said:
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
gangrenius said:
Where is this or what is this beta u speak of?
Click to expand...
Click to collapse
ChazzMatt said:
It's a soak test.
Click to expand...
Click to collapse
smooth781 said:
No! It's a OTA update. You should have it right now. Check for updates. I just installed it last night with no problems. I installed a stock rom. Ran the update, Then rooted again. Simple
Click to expand...
Click to collapse
Please actually read the thread before replying. The op clearly mentioned the 6.0 beta and someone asked about it. I answered.
6.0 beta = the Marshmallow soak test.
The Marshmallow soak test is by invitation only and is not an OTA update. Emails went out several days ago.
One of the Quarks (XT1225) already has Marshmallow, and now the Verizon Droid Turbo is being tested for Marshmallow. Chop Chop action is removed in official Marshmallow ROM, or at least it was by the final soak test of the Brazil XT1225 Soak Test #3. It was still there in Soak Test #1.
It's also being removed from the Marshmallow custom ROMs (CM13 and Resurection Remix), at least until the CM dev figures out why Motorola removed it and if it's safe to put back.
Thanks to XDA devs, we've had Marshmallow for months now -- no thanks to Motorola.
ChazzMatt said:
It's also being removed from the Marshmallow custom ROMs (CM13 and Resurection Remix), at least until the CM dev figures out why Motorola removed it and if it's safe to put back.
Thanks to XDA devs, we've had Marshmallow for months now -- no thanks to Motorola.
Click to expand...
Click to collapse
Do you have any idea what the rationale is for removing it from CM, and therefore RR? Why would a feature like this be considered "unsafe?" I use it pretty regularly and if the next RR update implements this, I will not be updating.
@baybutcher27, what are your thoughts on this?
TheSt33v said:
Do you have any idea what the rationale is for removing it from CM, and therefore RR? Why would a feature like this be considered "unsafe?" I use it pretty regularly and if the next RR update implements this, I will not be updating.
@baybutcher27, what are your thoughts on this?
Click to expand...
Click to collapse
Motorola removed it from the Quark Marshmallow ROM, final soak test #3.
CM dev then removed it -- at least for now. Resurrection Remix is CM based.
Skrilax_CZ said:
The reason is proprietaries have been updated to soak #3 as well. It'll keep it disabled until I learn more about why it was disabled.
Click to expand...
Click to collapse
It may be added back in the future.
Wait, Would I be able to update? I've unlocked the bootloader, and am rooted on stock rom.
What would I need to do?
KOAO said:
Wait, Would I be able to update? I've unlocked the bootloader, and am rooted on stock rom.
What would I need to do?
Click to expand...
Click to collapse
I assume if your bootloader is unlocked and you are rooted that you have TWRP custom recovery. Pretty sure OTA would fail. But that's not a bad thing. You don't want to be the one to find out the OTA locks your bootloader permanently. (Probably wouldn't, since you are already unlocked, and having custom recovery will prevent the OTA from installing -- but still you don't want to be the one to find out this time Verizon did something very sneaky.)
If your bootloader is unlocked, you would manually flash the eventual official Marshmallow XT1254 update manually -- not taking it as an "OTA". There will be download links available here on XDA. And you would wait until others have done it first.
Or you would flash a custom Marshmallow ROM, again manually -- either one by @computerfreek274 which would be stock-based (not available yet) or a CM13-based ROM (CM13 or Resurrection Remix) or an AOSP-based ROM (Mokee).
We already have three custom Marshmallow ROMs for ALL Quarks -- CM13, Resurrection Remix, Mokee and Motorola recently finalized stock ROM for the other Quark, the XT1225.
As soon as Motorola/Verizon get their act together for the XT1254/XT1250, you will have a stock Marshmallow ROM available to flash for the XT1254 and @computerfreek274 will also release a "stock-based" ROM for people to flash -- if you want to stay with pure stock or stock-based.
My cell standby battery drain has taken a turn for the worse since updating the modem. It worked fine (comparatively) in the past. Anyone else have this issue? I'm going to flash back the old modem and see if it fixes things.
Edit: Yup, flashed back to 44 and it's back to normal.
drizzzzzz said:
My cell standby battery drain has taken a turn for the worse since updating the modem. It worked fine (comparatively) in the past. Anyone else have this issue? I'm going to flash back the old modem and see if it fixes things.
Edit: Yup, flashed back to 44 and it's back to normal.
Click to expand...
Click to collapse
Yeah, the OTA update was basically worthless -- just an excuse to prevent Sunshine from working to unlock the bootloader.
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
i need relock the bootloader , my power botom is broke somebody knows how i can relock it , thanks
sorry for my bad english...
jorgkrkmo said:
i need relock the bootloader , my power botom is broke somebody knows how i can relock it , thanks
sorry for my bad english...
Click to expand...
Click to collapse
Don't lock it. Leave it unlocked, even if you send it in.
is there a chance sunshine will be updated to unlock the new version as well?
rhcreed said:
is there a chance sunshine will be updated to unlock the new version as well?
Click to expand...
Click to collapse
Theres a "chance" but a very slim one. The sunshine devs are not going to pour time and effort into it, but if they do find an exploit they will update it
rhcreed said:
is there a chance sunshine will be updated to unlock the new version as well?
Click to expand...
Click to collapse
The exploit they used has been closed.
Wynnded said:
The exploit they used has been closed.
Click to expand...
Click to collapse
can the phone be reverted to an unlock able version?
rhcreed said:
can the phone be reverted to an unlock able version?
Click to expand...
Click to collapse
No. Stock firmware with locked bootloader is not downgradeable.
People were told from the very beginning NOT to take the update unless your bootloader was unlocked first. Not just in this thread but several others.
Anyone who took the SU4TL-49 update with a locked bootloader does not care about unlocking their bootloader.
1) the Sunshine exploit has been available since November 2015. People have had six months to unlock their bootloaders! Why is it suddenly important now?
2) the Android SU4TL-49 update only showed up less than two weeks ago (early May 2016). It's the first firmware update since the exploit was released.
3) People were warned Android SU4TL-49 would close the Sunshine exploit. But even common sense would tell people that -- knowing control freak Verizon and their locked down bootloaders.
Looks to be some type of security updates.
Just popped on mine. Installed the update.
Matches this Software Version: MMB29M.N910VVRU2CPG2
https://www.verizonwireless.com/support/samsung-galaxy-note-4-update/
Kernel 3.10.40
Android Version 6.0.1
Android Patch Level September 1,2016
Baseband Version N910VVRU2CPG2
Will this update break Foxfi for Verizon Note 4?
Anyone know if PG2 does anything to the bootloader to prevent rolling back?
Sent from my SM-N910V using Tapatalk
subzero2000 said:
Anyone know if PG2 does anything to the bootloader to prevent rolling back?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
It appears to be a boot.img update. Flashfire rejected it as a safe OTA and I proceeded to freeze System Updates with Titanium Backup to eliminate future notifications. A bootloader update for sure.
Hopefully someone can tell if it's locking the bootloader down to prevent downgrading or the bootloader unlock method. Is there a way to freeze the update prompts if I'm not rooted yet? Just got the phone and haven't had a chance to unlock and root this bad boy.
Sent from my VS990 using Tapatalk
corporal_hades said:
Hopefully someone can tell if it's locking the bootloader down to prevent downgrading or the bootloader unlock method. Is there a way to freeze the update prompts if I'm not rooted yet? Just got the phone and haven't had a chance to unlock and root this bad boy.
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
buy package disabler. it is well worth the $1 price tag
Use Debloater, then freeze SDM.apk.
Root not required, very easy.
No, it does not break Foxfi.
Could someone please upload the ota zip file
Could you provide more details on how to do this please? I download it and disabled the package listed in the post below yours but I still get the stupid notification to update. Thanks
Edit. Oops, meant to quote hwaa18, not sure why it didn't let me, thanks
Nobody around here anymore?
PapaDocta said:
Could someone please upload the ota zip file
Click to expand...
Click to collapse
I'm relatively new here, with regard to uploads. I am on a vzw Note 4, running Jasminerom 7.0, with an unlocked bootloader. I don't even have an SDM, as it wasn't present on the ROM, however I found a post for shutting off Samsung updates that required shutting off two system update modules, and one or two other software and security modules. I'm beginning to think Samsung is in collusion with the carriers to make our phones obsolete, and prevent further mods. If you let me know how and where to upload to you, I can send you the file, if you still want it.
Sent from my SM-N910V using XDA-Developers Legacy app
Renegade_2k said:
I'm relatively new here, with regard to uploads. I am on a vzw Note 4, running Jasminerom 7.0, with an unlocked bootloader. I don't even have an SDM, as it wasn't present on the ROM, however I found a post for shutting off Samsung updates that required shutting off two system update modules, and one or two other software and security modules. I'm beginning to think Samsung is in collusion with the carriers to make our phones obsolete, and prevent further mods. If you let me know how and where to upload to you, I can send you the file, if you still want it.
Click to expand...
Click to collapse
Thank you so much, I already sold my Note 4 and got s7 edge till they release note 8.