Related
I updated my Motorbike X XT1058 for 4.4.4 (KXA21.12 VZW_XT1060_4.4.4-KXA21.12-L1.26_1FF) and it wanted to do the DOWNGRADE for 4.4.3 or 4.4.2. Some way for that?
The GPT.BIN in 4.4.4 is different from 4.4.3, which is different from 4.4.2, which is different from 4.4.0's.
Motoboot.img is different between 4.4.3 and 4.4.2. 4.4.2's is different from 4.4.0.
These will prevent a complete, successful and safe downgrade of the rom version.
If you've seen all the "don't downgrade or you'll brick" warnings, this is what its talking about.
This ^^^
But a better question is WHY would you want to downgrade?
I did not like because of the modification Verizon
Christian Correia said:
I did not like because of the modification Verizon
Click to expand...
Click to collapse
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Darth said:
Well, you really can't downgrade without great risk.
So better to live with it, or try the Chinese seller and unlock your bootloader for a fee. Then you can root, and change things that you can't change without root. Here is a long thread about the unlock code seller...
http://forum.xda-developers.com/showthread.php?t=2751177
Otherwise, there isn't much you can do.
Click to expand...
Click to collapse
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
DROID_4_UsEr said:
Actually you can do something that is risk because everything is a risk you can take and you never know what can happen but here it is: you can flash the 4.4.3 or 4.4.2 or 4.4.0 update over the 4.4.4 by using minimal adb flash tool and then just flash the 4.4.2 or desired version over but DO NOT FLASH THE gpt.bin!!!!!!!!That will screw up everything so after you flash everything but the gpt.bin you should do a cmd to reboot then you will be on the downgraded version!!! I'm not responsible for any bricked phones OK I tried this and the it worked for me so yea its a working procedure that YeS is a risky task so be careful!!!!:laugh:
Click to expand...
Click to collapse
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
KidJoe said:
First this is an old thread...
Next, skipping gpt.bin and/or motoboot.img(or its components) HAS been a cause for bricks, and when it didn't brick, it caused extra bugs (like trying to go App Drawer -> Settings -> Security kicks you back to settings menu... and some having issues toggling wifi on/off... and some who tried skipping gpt/motoboot when applying the 5.1 update also had speaker phone issues).
For more, see the link in my signature on downgrading..
Click to expand...
Click to collapse
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
DROID_4_UsEr said:
My mistake you need to flash the 4.4.4 gpt.bin over the 4.4.2 gpt.bin so the device thinks your flashing a 4.4.4 firmware but in reality your flashing the 4.4.2 firmware..I think its easier to use RSD lite to flash the firmware but you need to do a couple of modifications to the 4.4.2 firmware.All you got to do is move the 4.4.4 gpt.bin to the 4.4.2 firmware then flash it if you get the moto.bin error just do the same step as said above with the gpt.bin but with the moto.bin file..Hopefully it worked out for you ?
Click to expand...
Click to collapse
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
I did try but no succes
KidJoe said:
Not sure why you are quoting me saying "hopefully it worked out..." as I'm not the one trying to downgrade.
I can assure you... mixing GPT.BIN/Motoboot.img parts from one Stock rom, with the GPT.BIN/Motoboot.img of another STOCK rom is not a good idea.. it has been cause for bricks and/or features not working correctly.
To suggest otherwise, without acknowledging the risks, is irresponsible, especially if you take some time to search the forums and see all the posts of people who have either soft or hard bricked their device while trying various processes to downgrade. And especially if you are someone willing to help those who have bricked following your advice.
Click to expand...
Click to collapse
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
DejanPet said:
How can you downgrade from 4.4.4 to 4.4.2? I did try to downgrade the XT1060 Verizon,but it cannot be done,did try all options cut a line here ,edit a line there but still end up with the same 4.4.4 version.The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------
DROID_4_UsEr said:
It all depends on what rom you wanna flash if you flash cyanogenmod 12.1 you'll get the Lollipop update if you flash Cyanogenmod 11 you'll get back to kit-kat.
Click to expand...
Click to collapse
But you should know Sunshine developers charge a fee of 25 bucks to unlock and it works but you need to have a pay pal account and enough money for it
DejanPet said:
The idea i have is to downgrade to 4.4.2 and the use the sunshine to unlock the bootloader and after that to flash any ROM out there ,but never upgrade back to 4.4.4...Any help would be helpful...
Best Regards!
Click to expand...
Click to collapse
its documented in the sunshine thread that once 4.4.4 is on your phone its too late. even if you manage to downgrade it without bricking, the parts sunshine relies on will already have been patched and cant be downgraded. so downgrading wont help you to get sunshine to work
Help me regarding going back to4.4.3... I have the package and everything ( rsd lite stuff) but boot loader seems updated while i did ota to 4.4.4 .. its keep saying downgraded security pre flash vvalidation error while flashing 4.4.3.
4.4.3 was silky smooth. 4.4.4 is stuttery horrible in many apps and also generally to some extent
Theoretically this should be possible right to install old boot loader and then fash 4.4.3??
How and where to get boot loader old one.??.. I mean this is the thing they do in factories no?? Before flashing a firmware...
That would remove security downgrade verification right??
Reason is 4.4.4 is horribly stuttering Feels like a cheap china mobile
Search this forum for "downgrade brick" and see what others have had happen.
Long story short: just. don't. do it.
Problem. Is while doing an it's update after downgrading . which causes different kernel and system IMG to cause problems they say.
Still wonder why no one is into what causes the security check , how to get an old boot loader into the phone ... Wat they do I manufacturing? No phone comes with any software.. They are uploaded into it after emptiness. .. So why not 4.4.3 now .. if its the bootloader that causes problems why can't we install a boot loader that will match 4.4.3 ?? ...
All the forum is full f bricked moto x when there was no 4.4.4 firmware available. Nowthey are available.. So its not much problem now as it used to be.
Pls some one look into it... No one curious enough to decode the way?? I mean is this acceptable ? That we can't match 4.4.3 in a moto x ..
4.4.4 stuttering? User error
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
KidJoe said:
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
Click to expand...
Click to collapse
The problem is boot.IMG which has the kernel also has the dowbhrade security check error ... So when I falshed 4.4.3 over the 4.4.4 phone , ended up having kernel of 4.4.4 with system of 4.4.3.. ( I had to skip boot.IMG of kernel, motoboot.IMG , and got.bin)
Kernel is where interface comes...
Is there a way to flash the boot.IMG of 4.4.3 ... I would be satisfied with that... No need got.bin and motoboot.IMG flashing...
Also when I see this forum no one mention boot.IMG only motoboot and got.bin are mentioned.. Am I the only one having prob with boot.IMG flashingflashing.. If so pls tell kidjoe, iwould be happy
And AM NOT OTA OR MANUALLY UPDATIG TO LOLLIPOP IF I HAVE 4.4.3...
I HAVE OTA UPDATED 4.4.4 after having 4.4.3 system and 4.4.4 kernel .. To attain full 4.4.4 and it doesn't cause brickig .
Brickin occurs only when u update to next release it seems. 4.4.4 update is easy with the device it seems
nhizzat said:
4.4.4 stuttering? User error
Click to expand...
Click to collapse
Pls help me .. Wats user error.. I mean wat u mean by my error??
govardhan87 said:
Pls help me .. Wats user error.. I mean wat u mean by my error??
Click to expand...
Click to collapse
Most likely something you've modified or installed is causing the stuttering.
govardhan87 said:
The problem is boot.IMG which has the kernel also has the dowbhrade security check error ... So when I falshed 4.4.3 over the 4.4.4 phone , ended up having kernel of 4.4.4 with system of 4.4.3.. ( I had to skip boot.IMG of kernel, motoboot.IMG , and got.bin)
Kernel is where interface comes...
Is there a way to flash the boot.IMG of 4.4.3 ... I would be satisfied with that... No need got.bin and motoboot.IMG flashing...
Also when I see this forum no one mention boot.IMG only motoboot and got.bin are mentioned.. Am I the only one having prob with boot.IMG flashingflashing.. If so pls tell kidjoe, iwould be happy
And AM NOT OTA OR MANUALLY UPDATIG TO LOLLIPOP IF I HAVE 4.4.3...
I HAVE OTA UPDATED 4.4.4 after having 4.4.3 system and 4.4.4 kernel .. To attain full 4.4.4 and it doesn't cause brickig .
Brickin occurs only when u update to next release it seems. 4.4.4 update is easy with the device it seems
Click to expand...
Click to collapse
Most reference only GPT.BIN and MOTOBOOT.IMG because they are the partition table, bootloader, trusted zone, etc. Those two fail with an error that stops RSDlite, and those two error when trying to flash older versions via mFastboot. After getting those errors, that is usually when people start posting their phone is bricked and asking for help.
I've seen some downgrade everything but those two (meaning, yes they did even flash boot.img) using mfastboot (latest being from the 4.4.2 and 4.4.4 dev edition roms). But again, if you get forgetful and take an OTA, or sell it to someone in that state, you could cause a brick later.
You could be able to downgrade parts without bricking, we've seen that happen... In addition, like when people on 4.4.2 downgraded this way to 4.4, we saw features not work (I mentioned the security menu earlier) if they managed to not brick.
In some cases, when in the bricked or non-booting state from attempting to downgrade, flashing the full SBF of the newest version (4.4.4) manually via mFastboot with a few extra commands was enough to recover the phone and get it working. (at least check the phone's bootloader version and flash the SBF for that bootloader or a higher/newer SBF version). On some occasions they've bricked bad enough that they've needed to follow -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 and other times nothing worked and their phone was dead.
That being said, the many many threads asking for help due to phones not booting, being bricked, etc from attempting to downgrade are why we caution people to not downgrade and why you wont get much help doing it. Its not 100% safe or fool proof. If it goes wrong you could have a lot of work on your hands or a non-usable phone. Just because it has worked for you, doesn't mean it works and others can/should try it. We've seen too many times how people have bricked. For example a while ago there was someone claiming its possible to downgrade the XT1052 without issues, it was 100% safe, he did it without failure so it must be safe. Then XT1052 people who tried it started creating threads that their phone was bricked from following his steps asking for help. The thread was closed/locked.
But its your phone, do what you want. If you advise others to downgrade, or claim its safe to downgrade, make sure you include a clear warning that there are risks!!
govardhan87 said:
Help me regarding going back to4.4.3... I have the package and everything ( rsd lite stuff) but boot loader seems updated while i did ota to 4.4.4 .. its keep saying downgraded security pre flash vvalidation error while flashing 4.4.3.
4.4.3 was silky smooth. 4.4.4 is stuttery horrible in many apps and also generally to some extent
Theoretically this should be possible right to install old boot loader and then fash 4.4.3??
How and where to get boot loader old one.??.. I mean this is the thing they do in factories no?? Before flashing a firmware...
That would remove security downgrade verification right??
Reason is 4.4.4 is horribly stuttering Feels like a cheap china mobile
Click to expand...
Click to collapse
You do realize the ONLY change between 4.4.3 and 4.4.4 is the security fix for ssl right. It was less then 16 meg for the update so your issues are NOT related to 4.4.3 vs 44.4 I would look elsewhere for the cause of your issues before you completely brick your phone
adm1jtg said:
You do realize the ONLY change between 4.4.3 and 4.4.4 is the security fix for ssl right. It was less then 16 meg for the update so your issues are NOT related to 4.4.3 vs 44.4 I would look elsewhere for the cause of your issues before you completely brick your phone
Click to expand...
Click to collapse
dear adm1jtg... Am not a developer in android or even a software guy. I will be unable to see these things or verify that its only security update and will not affect kernel of the os- although they said wat u said..
That's y I posted here. Thanks for replying.
Would be happy if u tell if kernel is same in 4.4.3 And 4.4.4. ( if u know)
govardhan87 said:
dear adm1jtg... Am not a developer in android or even a software guy. I will be unable to see these things or verify that its only security update and will not affect kernel of the os- although they said wat u said..
That's y I posted here. Thanks for replying.
Would be happy if u tell if kernel is same in 4.4.3 And 4.4.4. ( if u know)
Click to expand...
Click to collapse
Kernel is not identical but close as far as i know as the security fix was kernel based. Ok that said instead of trying to change your stock rom i would try a custom kenrel. Which one you ask.... I am currently using zwliew. There is a thread for it in the dev area. You could also try a custom stock based rom like krypton or epsilon (also have threads in dev section).
Downgrading really shoudnt EVER be considered for any reason as you have a very good chance or permanently bricking your phone.
Agree with many here...
Even tho some say they've downgraded OK... Let's see how the next ota works out for them. Oops!
So .... Here's my 2 cents on downgrading........ DON'T !
?
Okay, I have to ask. Has anyone successfully downgraded a 4.4.4 KitKat Moto X (2013) to a previous firmware version?
I have the XT1058 "ghost" if that matters.
Seriously? This has only been covered nearly everyday since 4.4.2 became available. In other words, the answers are out there if you simply open your eyes or search.
No not possible to downgrade from 4.4.4
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Darth said:
Yes, but for every one that claim they did.... 10 others have bricked.
And the ones that say they downgraded OK, may be in for a bad surprise next time they take an ota.
So, don't... Unless you are able to replace it if you need to. ?
Click to expand...
Click to collapse
This is the info I wanted. Thanks.
Hi, my phone is xt1056, BL unlocked, I was fully flashed (enabled all the options in the xml file) the ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4 once.
Then I fully flashed my xt1056 with the xt1060 rom (VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml) in rsd. Now the phone is 4.4.2 and no signal, but it is 4.4.2, I can get my SPC with the app SPCUtility.apk.
After get my SPC, I was fully flashed the xt1056 (ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml with rsd to upgrade 4.4.4) again and works well (need to unlock the network again).
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Downgrading with an unlocked bootloader is no different than locked... Extremely dangerous.
And the poster above who downgraded, then upgraded again... I would not take any OTA's going forward. Or you might get an unfortunate surprise.
DarkWolffe said:
It really doesn't help me that you have the Sprint version. The AT&T bootloader can't be unlocked. At least not to my knowledge.
Click to expand...
Click to collapse
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
KidJoe said:
The moto x is not a nexus device. Unlike gaining S-off on an HTC phone, unlocking the bootloader on a moto x doesn't disable its security checks.
You can't downgrade got.bin and motoboot.img, or their internal components due to the phone's security checks.
People try downgrade by skipping those, BUT too often people brick when attempting this, or taking an OTA update in this state.
When you have mismatched parts on the phone, things don't work (like the issue of going settings-> security kicking you out) and you are at risk for bricking.
Click to expand...
Click to collapse
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
KidJoe said:
If you have 4.4.4 on an ATT device, right its bootloader can not be unlocked at this point.
As for flashing, as many have said IT IS NOT SAFE to downgrade, unlocked and locked bootloader included.
There are parts that are included with 4.4.2 and up that prevent downgrading. Because of this, under certain circumstances when trying to downgrade (like from 4.4.2 to 4.4 or lower, or 4.4.4 to 4.4.2 or lower), you could either brick your phone, or set it up to brick in the future when you take an upgrade.
In the case of some who have bricked by downgrading, flashing the latest (4.4.4 currently) SBF via mFastboot commands, with a few extra steps, has been enough to revive the phone. Other times, not.
For as many stories you might see of "its safe" or "I've done it", a future OTA will likely get them. Plus there are many more who have created "I bricked when trying to downgrade, HELP!!" threads.
A few Examples of bricked while downgrading:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt-1053-to4-4-4-to-4-4-3-prob-wit-t2967182
http://forum.xda-developers.com/moto-x/moto-x-qa/expert-opinion-to-stock-t2944721
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-bricked-t2952064
http://forum.xda-developers.com/moto-x/general/load-os-moto-x-t2942785
(keep looking in the Q&A section, or General section, you'll see lots more of them!)
And why do you think this thread exists? -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
I'll quote myself from another thread (in reply to someone that had an Unlocked bootloader)...
Again, this info applies whether you have an unlocked or locked bootloader.
So it is suggested you just stick with what is on your phone once you get on 4.4.2 or newer.
Click to expand...
Click to collapse
Perfect answer. Thank you for the clarity.
I just got my new Moto X 2014 2 days ago. It came with KitKat installed on it. I remember that on the Moto X 2013 that downgrading caused a lot of bricks. Is this the case with the new 2014 Moto X? Also, has anybody downgraded, then taken the OTA again and it still works?
During the downgrade process would I need to flash all the parts? Or do I need to skip some?
Have you read this thread? http://forum.xda-developers.com/moto-x-2014/help/lollipop-to-kit-kat-t2986044
Yes I have but it didn't answer all my questions. For example if upgrading via ota will cause a brick? If it's necessary to flash all files or if they all can even be flashed.
Sent from my XT1095 using Tapatalk
AGISCI said:
Yes I have but it didn't answer all my questions. For example if upgrading via ota will cause a brick? If it's necessary to flash all files or if they all can even be flashed.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I downgraded to kitkat and took the OTA to lollipop with no issues. When downgrading, you don't really have to skip any commands. If you try to flash an old bootloader (as was the case when I downgraded to kitkat after getting the newer bootloader from the OTA, well, I think it was a newer bootloader anyways), it will just fail to flash. No harm done, at least not on my XT1095). You can skip flashing the bootloader altogether, which is what I did the first time I downgraded to kitkat, and I had no issues.
Thank you, I took the plunge and installed lollipop. I was worried about downgrading since I was not sure if everything would work or not. So far so good.
Sent from my XT1095 using Tapatalk
I would like to know if the process is the same downgrading back to kitkat from lollipo 5.1???
Hi - a year or so ago I degraded from 5.1 to 4.x
I am now looking to upgrade to 6.1.
I need to be able to get 6.1 on, and then remove root & SU.
Can anyone help me with a guide on how to do this?
Faramire said:
Hi - a year or so ago I degraded from 5.1 to 4.x
I am now looking to upgrade to 6.1.
I need to be able to get 6.1 on, and then remove root & SU.
Can anyone help me with a guide on how to do this?
Click to expand...
Click to collapse
Read the GUIDES.
Devo7v said:
Read the GUIDES.
Click to expand...
Click to collapse
All of the guides seem pretty convoluted/outdated. I click the 5.0.1 and the thread is empty...
All I want to do is flash 5.0.1, or 6.1, or whatever is easiest.
I am currently on a flashed 4.4.2 - Rooted w/ Towelroot, but I would prefer NOT to be rooted when I upgrade.
Just a simple flash of the OTA 5.0.1 will do nicely, preferably with a security patch update prior to March 1, 2019. Having a hard time finding a simple guide to just simply flash it. Everything seems to be very complicated trying to keeproot, etc, which I am just not really trying to do.
I just want 5.0.1 or greater on an already flash 4.4.2 device. (I can't to OTA from device.)
Faramire said:
All of the guides seem pretty convoluted/outdated. I click the 5.0.1 and the thread is empty...
All I want to do is flash 5.0.1, or 6.1, or whatever is easiest.
I am currently on a flashed 4.4.2 - Rooted w/ Towelroot, but I would prefer NOT to be rooted when I upgrade.
Just a simple flash of the OTA 5.0.1 will do nicely, preferably with a security patch update prior to March 1, 2019. Having a hard time finding a simple guide to just simply flash it. Everything seems to be very complicated trying to keeproot, etc, which I am just not really trying to do.
I just want 5.0.1 or greater on an already flash 4.4.2 device. (I can't to OTA from device.)
Click to expand...
Click to collapse
The threads definitely aren't blank, I just looked at them. Since you're rooted it's not as simple as just flashing the update, you need to be on unrooted firmware to start with. The guides explain everything. Make sure you read everything and follow the directions exactly. You'll have to completely wipe your phone since you're rooted, but it's all explained in the guides.