Develop Bugs

Updated to 4.3 months ago using international version, how to update to 4.3 knox-free

I updated to 4.3 using the international method months ago because I was tired of waiting for the new tmobile update so I could put apps on my sd card. Now that tmobile officially updated everything, I want to update it so I can use wifi calling. I might follow this guide http://forum.xda-developers.com/showthread.php?t=2546024 so I wont break my warranty in an irreversible way. I just dont know if it will work because the guide states I need to be on 4.2.2. Currently my phone is not working correctly. It will boot but my home screen is blank and all screwed up and then it just restarts a few seconds later. I don't know what I should do. I want to keep my root. Should I do a full restore? I might try to load an old backup from the recovery for now just so its usable. Any help will definitely be appreciated. Thank you!!!!

coolpepp said:
I updated to 4.3 using the international method months ago because I was tired of waiting for the new tmobile update so I could put apps on my sd card. Now that tmobile officially updated everything, I want to update it so I can use wifi calling. I might follow this guide http://forum.xda-developers.com/showthread.php?t=2546024 so I wont break my warranty in an irreversible way. I just dont know if it will work because the guide states I need to be on 4.2.2. Currently my phone is not working correctly. It will boot but my home screen is blank and all screwed up and then it just restarts a few seconds later. I don't know what I should do. I want to keep my root. Should I do a full restore? I might try to load an old backup from the recovery for now just so its usable. Any help will definitely be appreciated. Thank you!!!!
Click to expand...
Click to collapse
IMPORTANT
Follow these steps if you want a fully working 4.3 ROM on your Galaxy S4 (M919) with all the benefits of the 4.3 update, WITHOUT KNOX. These steps should provide you with a 100% KNOX free setup so you can continue to keep root and flash new ROMs to your heart's content! THIS GUIDE WILL ONLY WORK FOR YOU IF YOU HAVE NOT ALREADY UPDATED TO 4.3 USING THE OTA UPDATE AND ARE STILL USING THE 4.2 BOOTLOADER. IF YOU HAVE THE NEW BOOTLOADER THAT READS "KNOX WARRANTY" THEN THIS WILL NOT WORK FOR YOU.​
STANDARD DISCLAIMER APPLIES! YOU KNOW THIS CAN BREAK YOUR PHONE, THERE ARE PLENTY OF PEOPLE WHO HAVE HAD NO ISSUES, THERE ARE SOME WHO HAVE. THIS IS A RISK YOU, AND YOU ALONE TAKE, I HAVE NOT HELD A GUN TO YOUR HEAD AND TOLD YOU TO FOLLOW THESE STEPS.
---------- Post added at 01:52 AM ---------- Previous post was at 01:49 AM ----------
An yes I would recommend you do a full restore first an see if that helps solve whatever issues you are having now.

Is my root preventing the official update?

I have the AT&T Galaxy Note 2, rooted, which is why I think it has been unable to install the last software update from AT&T. Every time I try, my phone will download the update but will fail 28% of the way through the install, I think this may be due to the root but I don’t know enough about this stuff to be sure. This is why I joined XDA, so that I could ask people smarter than me how to do the things I’m looking to do. If it is the root that’s the problem, then I imagine I’ll need a custom FW instead, there are a lot of listings here and I don’t know what is what or which update would be right for me, so I am asking for some help;
My phone is the SGH-I317
Android version; 4.3
Baseband version; I317UCUBMK6
Kernel Version; 3.0.31-2048209 [email protected] #1 Tue Nov 19 16:46:45 KST 2013
I don’t know if any of the info above is useful, I just want to keep the device up to date, nothing fancy, just whatever the most recent AT&T update is I want. I’m just not sure which of the many custom ROMs I should focus on.

watchdog-prime said:
I have the AT&T Galaxy Note 2, rooted, which is why I think it has been unable to install the last software update from AT&T. Every time I try, my phone will download the update but will fail 28% of the way through the install, I think this may be due to the root but I don’t know enough about this stuff to be sure. This is why I joined XDA, so that I could ask people smarter than me how to do the things I’m looking to do. If it is the root that’s the problem, then I imagine I’ll need a custom FW instead, there are a lot of listings here and I don’t know what is what or which update would be right for me, so I am asking for some help;
My phone is the SGH-I317
Android version; 4.3
Baseband version; I317UCUBMK6
Kernel Version; 3.0.31-2048209 [email protected] #1 Tue Nov 19 16:46:45 KST 2013
I don’t know if any of the info above is useful, I just want to keep the device up to date, nothing fancy, just whatever the most recent AT&T update is I want. I’m just not sure which of the many custom ROMs I should focus on.
Click to expand...
Click to collapse
Ya idk y usually it just unrooted the phone and flashed it are you on stock recovery?
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
This will help you get to 4.4.2
http://forum.xda-developers.com/showthread.php?t=2618447

terpin32 said:
Ya idk y usually it just unrooted the phone and flashed it are you on stock recovery?
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
This will help you get to 4.4.2
http://forum.xda-developers.com/showthread.php?t=2618447
Click to expand...
Click to collapse
I'll give it a go, one question though, will it cancel my root? Am I going to have to root the phone again afterwards?

Yes it will unroot but after you get to 4.4.2 just use cf autoroot and you'll be rooted again

It's not the root access it's the custom recovery that stops the Ota update.

How does that happen?

The Ota update runs a script that downloads the rom, attempts to boot into recovery, where it does a system wipe, then installs the rom. So it fails at that point, and continues to boot loop, because it's stuck on that step in the script.

OK, well is there a repair for that? That sounds like an error in the program itself, or is it because reversing a "root" is an involved process.

It's not an error. Samsung doesn't support people messing with the phone, and the scripts they write won't support custom recoveries. Just follow the steps in the link above.

red triangle while trying to update OTA lollipop while on TWRP...

Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376

jfreshh330 said:
Hey guys, I was rooted but on my stock 4.4.2 Sense Rom. I wanted to flash the OTA lollipop update. I had TWRP so i could not update the OTA. So i found a video on youtube that said i had to...
1 - Replace custom recovery with stock recovery
2 - Process OTA Update
3 - Replace stock recovery with custom recovery
I was at step 2 and my htc one m8 is tmobile US and was T-MOB010 so i downloaded "stock+recovery+1.12.531.19+recovery" there was two different ones for me to choose from. There was that one and then "2.22.531.5" however i could not find that DL link. I then flashed the stock recovery thru ADB and rebooted my phone, and it started to update but then i got a red triangle. I saw a comment on the youtube video that said i needed to find the OTA update and transfer to my PC and find the "recovery.img" file and then extract that and flash that to my phone. I looked thru the entire zip file however there is a folder i could not access, the last one named "firmware" I try to extract but i get an error message saying "cannot open, file is invalid" The OTA update i found in my internal storage in download folder and it is named "OTA_M8_UL_L50_SENSE60_MR_TMOUS_4.20.531.4-3.32.531.2_release_420432xio08y7xuups2gkl" that's got to be it because that's the only thing that could be the update any help??
youtube video: https://www.youtube.com/watch?v=PPPT5J8xG6w
Thread i was going off: http://forum.xda-developers.com/show....php?t=2701376
Click to expand...
Click to collapse
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triangle deal.
So try and find one thats a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the T-Mobile files. As mentioned though, just make sure the stock recovery is from Android 4.4.X or 5.X.X and you will be fine.

flexfulton said:
It sounds like the stock recovery that you loaded wasn't a new enough version. To update to lollipop you need to install a lollipop or a 4.4.X stock recovery. If you install anything that was released prior to that you will get the red triange deal.
So try and find one that a little newer. Perhaps see if someone has posted the lollipop one for your carrier. You can use that one. Should be easy to find as it's the latest. Then the OTA should take just fine. Perhaps the other stock one you mentioned would work. You just need to find it. I'm on Rogers in Canada so I'm not too familiar with the AT&T files. As mentioned though, just make sure the stock recovery in from Android 4.4.X or 5.X.X and you will be fine.
Click to expand...
Click to collapse
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.

jfreshh330 said:
Thank you for the reply! Is there a chance of bricking by trying to change out the stock recovery? Or would the worst that would happen is I get the red triangle. I mean obviously I'm not going to be flashing stock recoverys from different devices but u know.
Click to expand...
Click to collapse
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
Click to expand...
Click to collapse
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?

flexfulton said:
You mentioned stripping out the recovery.img from the OTA update. This shouldn't be a problem. Not sure why it wouldn't let you access it. Perhaps you have a bad download?
Look around XDA a little more. You should be able to find the OTA you are looking for.
As for flashing a wrong branded stock recovery, I don't really want to say cause I'm not sure what would happen. Just to be safe I'd stick to your carrier's files but perhaps someone else can speak on that.
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2714456
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Let me know if you need anything else. If you still can't get it to work, those would be the guys to consult.
Happy flashing!
Click to expand...
Click to collapse
Awesome thanks so much!

jfreshh330 said:
So I was going to try and download the official Rom off the HTC website. I've found the download link for the Rom. 4.16.1540.8 do you really think of I just use the recovery. IMG file it will work?
Click to expand...
Click to collapse
Sideload the latest recovery as found in the thread I linked to above. Reboot and the OTA should take no problems. It was downloading and everything fine for you before but was unable to flash because of an outdated recovery you installed.
So my recommened method to update OTA, is to follow the first route you were taking but with the newest recovery.img file in place of what you used in step 1.
If you already have the OTA downloaded on your phone, you shouldn't have to download it again either. It should see that it's already downloaded ready to be installed.
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
jfreshh330 said:
Awesome thanks so much!
Click to expand...
Click to collapse
No problem. Let me know how it turns out for you.

If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).

redpoint73 said:
If you don't mind wiping your personal data (you can of course back it up first,and restore later by a variety of methods) and setting up the phone again; it would be much easier to just update by RUU. Relocking the bootloader required if s-on.
The method of returning to stock ROM and recovery will work to update OTA. But its just a lot more potential pitfalls, as you have found (finding the right stock recovery, stock ROM, and even then there is no guarantee your data will be retained, although it should).
Click to expand...
Click to collapse
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.

flexfulton said:
If you flash the stock recovery and let the OS do the OTA update there will be no issues. Relocking bootloaders etc sounds like a lot more work to me.
He is already on stock ROM and has the instructions to do the stock recovery OTA update so I think that's the best route. I provided him with the correct recovery so there should be no problems now.
Click to expand...
Click to collapse
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
flexfulton said:
Also I don't see how in any case doing an OTA would cause you to lose your data. People would have a S$%t fit if they lost data on OTA updates.
Click to expand...
Click to collapse
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.

redpoint73 said:
Its a matter of opinion which approach is easier or "best". I just gave it as another option.
Relocking the bootloader is a single fastboot command. Yes, the OP would then need to unlock the bootloader again after the RUU.
On the other hand, the OTA approach requires flashing stock recovery, then installing 3 OTA updates in order to get up to Lollipop (opposed to just a single RUU that would take the OP up to LP).
Its not "supposed" to happen. But I have seen it happen to folks, on more than a few occasions. And yes, those folk have a S$%t fit when it happens.
In any case, everyone should backup their data and be prepared to have to restore it (and its all that much easier on a phone that is already rooted). No data is immune from loss, even from day-to-day use, and all the more for a major system change like an OS update.
Click to expand...
Click to collapse
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.

flexfulton said:
That link will be of great help to you. Has the recovery you require (3.32.531.2 - I just downloaded it myself with no issues) and much discussion on the subject of OTA Lollipop updates etc for T-Mobile.
Click to expand...
Click to collapse
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
flexfulton said:
Agreed backups are good.
Why 3 OTA updates? Is that a T-Mobile thing? I only had 1 when I made the jump on the Rogers network.
Click to expand...
Click to collapse
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.

redpoint73 said:
The OP is presently on Android 4.4.2, which is software number 1.xx. He will need a recovery corresponding to 1.xx software, as he seems to have already figured out, but its not working.
---------- Post added at 09:53 AM ---------- Previous post was at 09:50 AM ----------
Not just a T-Mob thing.
He is on Android 4.4.2 (software 1.x). Unless T-Mob skipped a software version (and I don't think they did) he needs to update in sequence to software 2.x, then 3.x, then finally up to the current 4.x.
OTAs need to be installed in sequence; opposed to RUUs which are complete factory images, so you can skip software numbers.
Not sure about Rogers. But my guess is that you only had to update from 4.4.4 to 5.0; or something to that effect.
Click to expand...
Click to collapse
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
I was trying to help out as I had the same issue when I went to update. I installed a recovery that was too old, determined that I needed to flash a recovery from either 4.4.X or lollipop and my OTA update was fine after that. Point being, I could go ahead and flash a newer recovery to get the OTA to download.
Anyway I applogize if I was in error in my help. No one else was helping and based on my own experiences it sounded like the same issue.

flexfulton said:
Makes sense. I only had to go up one level. I figured that the carriers would package all of the older updates in with new one but apparently I'm wrong. I appologize.
Click to expand...
Click to collapse
OTAs will normally only allow you to install from the immediate previous version (you cannot skip a version). Sometimes they are complete packages; but often they are not. Sometimes the OTA just contains what has been changed; basically a "patch". And for that reason, the updates need to be installed sequentially. In fact, I've seen folks brick due to unwittingly installing partial firmware packages from OTAs (with s-off, which bypasses such safety checks).
flexfulton said:
Anyway I applogize if I was in error in my help.
Click to expand...
Click to collapse
There's no need to apologize. As you are well aware, this is a self-supporting community that flourishes due to the contributions of its members. Your answers may not have been 100% correct. But it was well intended; and you answered to the best of your knowledge. At least you learned something and can pass it along now. I'm just a member who passes along what I've learned here also (don't have any specialized developer knowledge or anything); and I'm certainly not right all the time.

So the recovery 3.32.5312 will not work? And i apologize i am on 4.4.4 not 4.4.2

downgrading from CM13 marshmallow 6.0.1 to stock rom - need help

Hi everyone. I need to know if it's possible to downgrade from CM13 to the stock rom/firmware my phone came with which is Jellybean 4.3. I decided to upgrade my OS so I could try out Pokemon Go. Originally I was just going to upgrade to 4.4 which is the minimum version required for the app but I decided I might as well upgrade to the newest one. The newer the better right? And I would also be future proof for any other apps that might require a newer OS. But not only did I not like Pokemon Go, which I ended up uninstalling, (I don't know how such a simple bare bones game like that is so popular) I also don't like marshmallow. Some features are missing that I had in 4.3 like Double Tap to Top where you can double tap the top of the phone to quickly scroll to the top of the screen or the option to hide folders in the gallery which is bare bones and has no options or features. I can't move apps from one screen to the next with my thumb like I used to because I have to push the app as far past the edge of the screen as possible in order for the screen to switch so I have to use my index finger to do it. I'm thinking this is because it was designed for the edge which has the screen going over the side of the phone. I also just don't like the look of Marshmallow compared to Jellybean. And my phone takes forever to boot up now clocking in at about a minute and a half. Instead of gaining access to something better that previously wasn't available to me I feel like I forced something on the phone that doesn't belong and shouldn't be there.
If anyone can help me downgrade I would appreciate that very much. I tried to do it with the same method I used to upgrade by rooting the phone again with odin and then just flashing the stock OS but odin didn't work (I already had CyanogenMod installed from when I upgraded). Odin gave me the confirmation that I successfully rooted my phone but when I checked it with a root verification app it said my phone wasn't properly rooted and SuperSU also says there's no root detected. I'm sure this has something to do with me having marshmallow this time instead of jellybean. I tried using google for help but I couldn't find anything about my situation. Now I don't know what to do which is why I'm here. This was my first time installing a different OS so I'm new at this.

I'm guessing you could use the root66 version to flash back to stock with root.
Sent from my Amazon Jem using Tapatalk
---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------
http://forum.xda-developers.com/showthread.php?t=1949687 for the root66 thread
Sent from my Amazon Jem using Tapatalk

Thanks for replying. I'll look into it. I also recently found something that might do the trick. It's a how-to guide for my phone on unrooting it and restoring the stock firmware.

Problem solved. Turns out all I had to do was install the stock firmware with odin. I didn't have to root my phone again. Then I updated to the latest version of Jellybean with Samsung Smart Switch. I'm glad I was able to figure it out.

[Qualcomm][MetroPCSXT1765]Do Not Take ANY Updates From March 2018 Onward

***Update August 31, 2018*** It has been reported from @Juanito216 that he's locked out of TWRP after taking an update, and this update is well past March when I first reported it. Be advised not to TAKE THE UPDATES OR YOU WILL LOSE ROOT/TWRP!
***Note*** Made a note of this under my Noob Metro PCS Guide.
This is for a MetroPCS XT1765 phone.
So the significant other finally let me get ahold of their phone (same model) because of bugs on the Stock Rom, and FINALLY I was able to unlock the bootloader. However, this phone had the forced update from March. (My phone didn't have this problem as I rooted out the box).
If you take the update, you have to push the Bootloader unlock. Motorola will give you the unlock code, but I had to keep doing it with the code until the phone "unlocked". Didn't happen on my phone out the box.
If you take the update, you WILL NOT BE ABLE TO FLASH Magisk v14. I also was unable to install @squid2 TWRP new version. Error 1 kept popping up. Did let me install the superuser and the no-verity just fine but you don't have root.
The only solution you will have to get root is to flash a custom rom and then flash Magisk. But the update did something to the root.
Hope this help you guys.

You seriously had to say that again??
Sent from my XT1766 using Tapatalk
---------- Post added at 12:44 AM ---------- Previous post was at 12:43 AM ----------
Articul8Madness said:
***Note*** Made a note of this under my Noob Metro PCS Guide.
This is for a MetroPCS XT1765 phone.
So the significant other finally let me get ahold of their phone (same model) because of bugs on the Stock Rom, and FINALLY I was able to unlock the bootloader. However, this phone had the forced update from March. (My phone didn't have this problem as I rooted out the box).
If you take the update, you have to push the Bootloader unlock. Motorola will give you the unlock code, but I had to keep doing it with the code until the phone "unlocked". Didn't happen on my phone out the box.
If you take the update, you WILL NOT BE ABLE TO FLASH Magisk v14. I also was unable to install @squid02 TWRP new version. Error 1 kept popping up. Did let me install the superuser and the no-verity just fine but you don't have root.
The only solution you will have to get root is to flash a custom rom and then flash Magisk. But the update did something to the root.
Hope this help you guys.
UPDATE 4/1/2018 - After finally being able to unlock the bootloader of the significant other and root it, I found something interesting. - if you take the pestering update that rolled out in March, you will be UNABLE to flash Magisk v14. You can flash No Verity and Superuser well, but you WILL NOT HAVE ROOT. The only alternative I have is to flash a custom rom and then flash Magisk.
Do Not Take the Update.
Click to expand...
Click to collapse
PimpMy5Ton said:
You seriously had to say that again?? Everyone I know uses custom roms anyway, just sayin'
Sent from my XT1766 using Tapatalk
Click to expand...
Click to collapse
Sent from my XT1766 using Tapatalk

PimpMy5Ton said:
You seriously had to say that again??
Sent from my XT1766 using Tapatalk
---------- Post added at 12:44 AM ---------- Previous post was at 12:43 AM ----------
Sent from my XT1766 using Tapatalk
Click to expand...
Click to collapse
Well, I said that because not everybody is going to read my guide. I've had such hell with this phone while others have sailed through it, I'm giving ALL the MetroPCS folks a head up. Most of the development is done on other variants of the phone as is, and a lot of info that is out there while Qualcomm does not really apply to us. Consider me like an ambassador for the Metro folks, lol.
If somebody said it, I haven't caught it in the threads. And honestly, hopefully this thread opens up a discussion on how we can flash back. I was completely unable to go back to the original stock on the significant other's phone AFTER that update too. Been tinkering with it since I posted that. Can't even flash some of the boot.img files successfully either that I explained in my post (in case of emergency section).
That update is something seriously nasty.
Update: Aaah...I see what I did there. Man, I'm doing too much in the middle of the night. Sorry bout that copy and paste thing. I was taking notes and writing and tinkering with the phone. Didn't want to forget the problem exactly.

Took the latest update that I know of and now I can't flash TWRP anymore. Locked the bootloader and everything back up because I thought I was going to sell this phone. It didn't sell and I decided to unlock it again and root. I hope some type of way someone can find out how to install TWRP after taking all the updates. This Metro PCS variant kind of sucks for rooting\roming.

Juanito216 said:
Took the latest update that I know of and now I can't flash TWRP anymore. Locked the bootloader and everything back up because I thought I was going to sell this phone. It didn't sell and I decided to unlock it again and root. I hope some type of way someone can find out how to install TWRP after taking all the updates. This Metro PCS variant kind of sucks for rooting\roming.
Click to expand...
Click to collapse
No, Juanito, no! That's why I said don't take the update. But now I'll correct it in my OP. Thanks for the info.
Can you follow my guide and see if you can get TWRP from ADB shell?

Im running Lineage OS, I can boot TWRP, but can no longer install it. I thought I would never root the phone again. So now at this point, I might not take it to stock ever again.

Juanito216 said:
Im running Lineage OS, I can boot TWRP, but can no longer install it. I thought I would never root the phone again. So now at this point, I might not take it to stock ever again.
Click to expand...
Click to collapse
I know you say you can't install TWRP. But can you load it through ADB Shell? If you can there's hope.
Did you start doing all this on Lineage or on Stock, or started back to stock and it crashed. You can always reunlock the bootloader through the Moto prompts on their website. It shouldn't be blacklisted.