Currently on 33r but hoping to downgrade back to 30o or lower? Can this be done. All I can find is the flash for 33r. Thanks
Find the fastboot images and then flash them (or flash XNPH25R and then apply 30O OTA update and not accept 33).
Is there a particular reason why you want to downgrade?
zephiK said:
Find the fastboot images and then flash them (or flash XNPH25R and then apply 30O OTA update and not accept 33).
Is there a particular reason why you want to downgrade?
Click to expand...
Click to collapse
Seem to be getting low call problem on 33r and recent app switcher problem.
Go to my index thread on my signature. In the stock images section you'll find a link to a that that holds all versions of CM11S that have been released. You can flash to your heart's content.
Transmitted via Bacon
Related
So Cyanogen sent out the 44R ota today and I am rooted with a custom recovery. My current software version is 38R android 4.4.4. So in order to do the ota:
1. I need to go into SuperSU and do the permanant unroot.
2. Reboot
3. Flash stock recovery.
So for step 3 I downloaded the 38R stock firmware from cygen's site. Can I extract it and flash just the recovery? Will this work?
skyguy126 said:
So Cyanogen sent out the 44R ota today and I am rooted with a custom recovery. My current software version is 38R android 4.4.4. So in order to do the ota:
1. I need to go into SuperSU and do the permanant unroot.
2. Reboot
3. Flash stock recovery.
So for step 3 I downloaded the 38R stock firmware from cygen's site. Can I extract it and flash just the recovery? Will this work?
Click to expand...
Click to collapse
You don't need to do any of that. No unrooting is required. You can flash the OTA with a custom recovery. All you need to do is initiate the update process through your Settings menu.
Transmitted via Bacon
I'll try that next time but I used my method and it worked fine
skyguy126 said:
I'll try that next time but I used my method and it worked fine
Click to expand...
Click to collapse
Of course it did, but what I'm saying is it's completely unnecessary to do all that.
Transmitted via Bacon
timmaaa, what do you mean with
All you need to do is initiate the update process through your Settings menu.
Click to expand...
Click to collapse
with rooted OPO, custom recovery and xposed i don't can flash the regular OTA right? i need to take the modified OTA and uninstall xposed? is this the correct way?
RotesMeerJogger said:
timmaaa, what do you mean with
with rooted OPO, custom recovery and xposed i don't can flash the regular OTA right? i need to take the modified OTA and uninstall xposed? is this the correct way?
Click to expand...
Click to collapse
If you uninstall Xposed you can use the normal OTA. If you don't want to uninstall Xposed you can use the modified OTA. The custom recovery and root make no difference either way.
Transmitted via Bacon
hey thank you very much timmaaa! works perfect after update i only need root again
Thanks for the help everyone!
[EDIT: Fixed]"Data Too Large" when installing stock 44S firmware (US device)
So, my device just came in today. I wanted to have the final version before I started playing with it. As the device was saying there wasn't any OTAs beyond 30O, I unlocked the bootloader to flash the 44S version (I was going to unlock it anyway).
After the whole process of flash many files, it gives me an error when I try to flash the system itself:
Sending "system"
FAILED <remote: data too large>
And it ends up there. The phone currently does not boot, but I can get to fastboot mode easily.
So, how can I fix this? Does flashing a different recovery and flashing stock 44S work? How can I push files with fastboot?
EDIT: Fixed. I just needed an updated fastboot package. You can use this one: http://forum.xda-developers.com/showthread.php?t=2317790
It usually means you have an outdated version of adb installed. How did you go about installing adb/fastboot?
Transmitted via Bacon
timmaaa said:
It usually means you have an outdated version of adb installed. How did you go about installing adb/fastboot?
Transmitted via Bacon
Click to expand...
Click to collapse
It was indeed outdated. Just fixed it. Also provided a link to the one that worked for me.
Thanks for the help.
I'm on the original CM12s rom, rooted with TWRP recovery. I just got the notification for the latest OTA. Is it safe to go ahead and install this or not? (i have turned off updating the stock recovery in Developer settings)
Cheers
It's safe.
Transmitted via Bacon
Agree, don't forget to flash root again after flashing the OTA. (in case you use an external root)
Where is the OTA downloaded to? When i press update it goes into TWRP..
Thanks
GalaxyWhy said:
Where is the OTA downloaded to? When i press update it goes into TWRP..
Click to expand...
Click to collapse
Check this out:
http://forum.xda-developers.com/showpost.php?p=60325143&postcount=4
Hi all,
I have a rooted Z3 with dual recovery and locked bootloader running firmware 23.1.A.0.690.
Since the OTA to firmware 23.1.A.1.28 is minor, I was wondering if it is possible to flash an update zip file while keeping root and modified recovery.
any idea ?
thanks
benjieb said:
Hi all,
I have a rooted Z3 with dual recovery and locked bootloader running firmware 23.1.A.0.690.
Since the OTA to firmware 23.1.A.1.28 is minor, I was wondering if it is possible to flash an update zip file while keeping root and modified bootloader.
any idea ?
thanks
Click to expand...
Click to collapse
Modified bootloader? Do you mean unlocked? If so then you cannot do OTA, is says so explicitly on the Sony site about unlocked bootloaders. But you can make a backup in recovery, flash a stock FTF of that version (System only) then just flash back your custom kernel (Before booting the phone) and restore data from a backup
If you mean locked bootloader then you can OTA, if its a small update then the chances are it wont format system so you will keep root, but if its a large file the chances are it will format system then re-install it so you will lose root.
Just flash a pre-rooted version of the updated ROM in recovery
Sorry, i meant keeping root and modified recovery (not bootloader).
My bootloader is locked indeed and i am on stock kernel.
So, to your point, i should be safe upgrading minor OTAs?
If so can I anticipate sony's rollout of the OTA and flash the update zip? And where can it be found?
Thx
benjieb said:
Sorry, i meant keeping root and modified recovery (not bootloader).
My bootloader is locked indeed and i am on stock kernel.
So, to your point, i should be safe upgrading minor OTAs?
If so can I anticipate sony's rollout of the OTA and flash the update zip? And where can it be found?
Thx
Click to expand...
Click to collapse
Maybe.... it all depends on whether or not the OTA formats system and reinstalls it. If it a minor update they may not do that so root and recovery (Which is in system for locked bootloaders) are not deleted.
Its a gamble...
to be 100% safe, you will need to get a prerooted flashable zip and flash it
Hmmm... Ok, but upgrading with a prerooted zip involves flashing a full rom not just the update right?
I am ok with that but would rather save the hassle.
Thanks for the advise
Hi,
Happy to report back that OTA process went smooth.
I am now running 23.1.A.1.28 and still have full root & dual recovery!
benjieb said:
Hi,
Happy to report back that OTA process went smooth.
I am not running 23.1.A.1.28 and still have full root & dual recovery!
Click to expand...
Click to collapse
Benjieb,
Sorry friend but it was not clear to me... you updated via OTA and keep the root?
Yes that's right. I fixed the typo in my last post.
benjieb said:
Yes that's right. I fixed the typo in my last post.
Click to expand...
Click to collapse
How do you do it? I mean,you were stock .690 berofe ota?you delete anything of stocks apps??because i test to do the ota update but at the end of processus it's says "verrification impossible" and i saw somewhere that's if we touch or delete stock apps we can't ota ....ans if possible,nobody van do a flashable ZIP with just ota update????
I was stock indeed, and you are right playing with system apps probably prevent OTAs.
That's why I deactivate system apps rather then delete them.
I guess you will have to do a full rom flash.
I'm on stock ROM rooted. Updated to. 28 via OTA just only. Root access still available!!
Sent from my D6653 using Tapatalk 2
No possible to create a flashable ZIP with just ota update???it will be wonderfull
I believe this is just minor update. So lucky for me haha
Sent from my D6653 using Tapatalk 2
hi guys i'm brasilian and my english is pretty poor but lets try. i was flash 4.4.4 rom br retail. and i update via ota for lollipop.. and brick .. i search in forums here ... and i go it to put in boot loader without robot.. already try many ways to recovery my boot loader but always get error remote failure.. and already used 6.0.1 stock .. maybe i need to files atualy for this? i'm very sad my maxx is dead .. someone give me light .. help me fix this ... thank you guys
Is your bootloader locked or unlocked?
ChazzMatt said:
Is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
kenedi jr said:
unlocked
Click to expand...
Click to collapse
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
ChazzMatt said:
Good.
What version Android was your phone on before the problem?
Were you on stock (factory) or on custom ROM?
Surely you weren't on Kitkat for almost 3 years?
Click to expand...
Click to collapse
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
kenedi jr said:
I was in a custom rom and went to 4.4.4 and tried to upgrade via ota .. and brinck so I was able to make boot loader appear more without the robot
Click to expand...
Click to collapse
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
So I'm stuck on the bootloader. If I connect charger or pc it will already pro boot loader without the robot. I have already tried to pass stock 4.4.4 and 6.0 and more etc always from the failure remote failure in bootloader appears in the log something with gt bin downgrade
ChazzMatt said:
When you downgrade back to lower stock, you have to omit gpt.bin command. Because you have a newer bootloader.
This is also why you can't take OTA. Because it tries to install a different bootloader (which is probably still older than what you had with custom ROM). If you wanted stock 5.0.2 again, you have to flash full stock image and omit the gpt.bin command.
Are you able to use volume and power button to the bootloader screen?
Click to expand...
Click to collapse
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
kenedi jr said:
My question is if I crashed from 4.4.4 trying to upgrade to 5.1 which version files do I need to adapt to my bootloader that seems to be corrupted?
Click to expand...
Click to collapse
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
ChazzMatt said:
Before this trouble, were you ever on stock Marshmallow 6.0.1? If so, you can flash back to full firmware of that, but needs to be the very latest. I'll find a link for you.
Also, do you have TWRP installed and did you have a backup you can restore?
Click to expand...
Click to collapse
I do not have twrp backup and I can not even install the recovery stock
kenedi jr said:
Yes before this problem I was in the latest 6.0.1 and the stock I have here when I installed had a security update
Click to expand...
Click to collapse
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that version to repair. Just reflash the entire full firmware.
Click to expand...
Click to collapse
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
thanks bro you saved me
kenedi jr said:
This is the most likely because all the methods say so old and not one was and when I try to pass any old stock also will not always get that error in the bootloader in the gptbin downgrade logs
Click to expand...
Click to collapse
You can not flash any older gpt.bin files. You have to omit (leave out) that flash command.
Your gpt.bin file is 6.0.1, and you cannot downgrade. Even on 4.4.4, trying to accept the 5.0.2 OTA update is still older gpt.bin file in that OTA than your 6.0.1.
ChazzMatt said:
OK, then that's the bootloader you were on and will always be on. You need to reflash that latest version (with the security update) to repair. Just reflash the entire full firmware.
There's a link to it here in this forum. I'll find it when I get home, if you don't have it.
Then in the future, if you try to downgrade, you always have to flash full stock version EXCEPT you omit the gpt.bin file. Whether 4.4.4 Kitkat or 5.0.2 Lollipop.
And you can never take OTA.
Because you really have 6.0.1 bootloader.
Click to expand...
Click to collapse
i don't have link .. i will wanting you so
kenedi jr said:
i don't have link .. i will wanting you so
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=72846593
ChazzMatt said:
https://forum.xda-developers.com/showthread.php?p=72846593
Click to expand...
Click to collapse
I was a bit confused with this link which is the last one? I discovered because I am Brazilian and my English was developed only by playing
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
ChazzMatt said:
http://ftpeil.eil.com.br/vip/motoro...S24.107-70.2-7_cid12_subsidy-DEFAULT_CFC.xml/
Click to expand...
Click to collapse
Face first you're a myth. I just passed gpt.bin and got the bootloader ... I'm very happy. Do I need to pass the entire rom ??
:good::laugh: