I'm currently on a custom 5.1 ROM with the new bootloader and radio. I read about issues when flashing the CM12 ROM with this setup. Is this still a problem? Do I have to go back to the 5.0 stock android (with full wipe) before flashing CM12?
Would like to know something similar of the sort, also have the 5.1 boot loader and radio and am on resurrection remix 5.1. Would like to go to CM12 if possible.
Solution found:
http://forum.xda-developers.com/showthread.php?t=2958222
I already installed CM12 after flashing the 5.0 bootloader and radio from the thread without any problems.
daniel.1983 said:
Solution found:
http://forum.xda-developers.com/showthread.php?t=2958222
I already installed CM12 after flashing the 5.0 bootloader and radio from the thread without any problems.
Click to expand...
Click to collapse
So what was the process you wnet through? Flash the 5.1 radio and bootloader, then CM12, then gapps? I thought downgrading the bootloader would result in a hard brick? Also did you flash the latest CM12 nightly?
KentuckyGuy447 said:
So what was the process you wnet through? Flash the 5.1 radio and bootloader, then CM12, then gapps? I thought downgrading the bootloader would result in a hard brick? Also did you flash the latest CM12 nightly?
Click to expand...
Click to collapse
I flashed the zip file from post one with the 5.0 bootloader (https://www.androidfilehost.com/?fid=95916177934545628). Afterwards I flashed the latest CM12 nightly and the Gapps on top. I'm not sure about which action/configuration could brick the device. I have seen much positive feedback in the other thread, so I tried this too.
KentuckyGuy447 said:
I thought downgrading the bootloader would result in a hard brick?
Click to expand...
Click to collapse
Think. Why would Google still make available older factory images, if downgrading (which would include the bootloader) bricked a updated device?
beekay201 said:
Think. Why would Google still make available older factory images, if downgrading (which would include the bootloader) bricked a updated device?
Click to expand...
Click to collapse
It is more of a concern you know. My knowledge is very limited as all this is new to me. I don't have money to throw around for a new device but thanks! I'm taking this as its safe to. Just hard bricking would permenatly destroy a device so don't wanna do that you know...
EDIT: Tested and Confirmed Woking! Big thanks to Daniel!
Related
What is the latest right now and is Oxygen avail without rooting or rom?
cell2011 said:
What is the latest right now and is Oxygen avail without rooting or rom?
Click to expand...
Click to collapse
Latest for CM11S is 05Q and Oxygen is only available through a flashable zip. So you will need to unlock the bootloader in order to flash it.
You can also wait for CM12S to come out "later this week," which should be available through an OTA.
The_Symbiote said:
Latest for CM11S is 05Q and Oxygen is only available through a flashable zip. So you will need to unlock the bootloader in order to flash it.
You can also wait for CM12S to come out "later this week," which should be available through an OTA.
Click to expand...
Click to collapse
Ok ty im new to OPO so since the phone i get is still on 4.4.4 i can you use the toolkit thats on here in the forum for unlocking boot and root? Then i can flash Ox OS Can i still take 12s if im rooted when its avail on OTA?
cell2011 said:
Ok ty im new to OPO so since the phone i get is still on 4.4.4 i can you use the toolkit thats on here in the forum for unlocking boot and root? Then i can flash Ox OS Can i still take 12s if im rooted when its avail on OTA?
Click to expand...
Click to collapse
You can use a toolkit, but I would suggest against it.
@timmaaa has an excellent thread that has been posted here which gives you literally everything you need to unlock your bootloader, install a custom recovery, etc.
If you flash Oxygen, you will not be able to OTA to 12S. However, I'm sure there will be flashable zips up the same day it comes out.
The_Symbiote said:
You can use a toolkit, but I would suggest against it.
@timmaaa has an excellent thread that has been posted here which gives you literally everything you need to unlock your bootloader, install a custom recovery, etc.
If you flash Oxygen, you will not be able to OTA to 12S. However, I'm sure there will be flashable zips up the same day it comes out.
Click to expand...
Click to collapse
This look ok this is what im buying
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
matanp said:
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
Click to expand...
Click to collapse
A few questions:
What method are you using to switch between KK and LP? Fastboot (flashing stock images) or recovery?
If it's recovery, are you flashing the correct firmware/modem?
Are you still able to see your baseband and IMEI in About Phone?
IF you haven't flashed the stock images with fastboot that's the first thing you should try. I have detailed instructions in my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
matanp said:
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
Click to expand...
Click to collapse
Have you flashed the latest Lollipop build with fastboot as outlined in my guide?
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
matanp said:
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
Click to expand...
Click to collapse
That's because the LP images don't usually contain it, but the ones I link to do.
i'll try and report
thanks
i just got a message from oneplus support:
Hi Matan,
Thank you for reaching out. Sorry for the inconvenience that has caused to you. Rest assured that we will be providing you solutions in solving the issue.
You can also try to flash the device to the latest Oxygen OS, it is designed to fix common bugs that causes the issue.
To install OxygenOS on your OnePlus One, you need to flash the device. You may follow the guidance here:
https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/
Please also note that since OxygenOS is a product from OnePlus therefore it is currently only available for OnePlus One.
Please don't hesitate to contact us for any update and feedback.
Thank you and have a good day.
Regards,
Jefflee
Click to expand...
Click to collapse
can i flash oxyOS (to check if it solve the problem) and after that flash your COS12 img with the fastboot commands or is there anything else i should know about?
flashed the latest COS12 version with your guide and i still have bootloops
Having this exact problem.... No wifi in CM11 and when updating tot CM12 getting boot looped.
Found a solution to your problem?
It's because of the modem files.. When u downgrade or upgrade from/to lollipop/kitkat u must flash the appropriate files!! Pm me if u want more info
Sent from my A0001 using Tapatalk
yes, i've open a ticket with oneplus one and their tech guy installed oxygenOS and it works well
I was using cm 12.1 and wanted to update it to newer version, but after flashing it stuck in bootloop.
Now i can only flash cm 12.1 and don't know why ?
I've tried many types of different rom's but all end up in bootloop, only version 12.1 works.#
Thanks for help.
Fastboot doesn't work for me, when im trying start it, screen flashes and goes back to bootloader.
I dont care about any files so i've tried wiping everything mounting unmounting, factory resets etc. but still it boots only cm 12.1
Will someone be able to help me please ?
It's really important.
eskejpmi said:
Will someone be able to help me please ?
It's really important.
Click to expand...
Click to collapse
well you can only flash lollipop roms until you update your bootloader as far as I know. I haven't messed with any custom rom though, but I at least read the threads.
lafester said:
well you can only flash lollipop roms until you update your bootloader as far as I know. I haven't messed with any custom rom though, but I at least read the threads.
Click to expand...
Click to collapse
When I search for " bootloader update nvidia shield " there is no such thing on the internet.
I read a lot of threads and still haven't found a solution to my problem.
Still thanks for the reply.
So basically i can only boot CyanogenMod 12.1 on mine device. No other ROM boots.
You can find the Marshmallow bootloader (4.2.0) under Firmware Update of the OP of the CM13 thread. First, make sure you're using the latest official TWRP 3.0.2-2 before flashing the bootloader.
*PROBLEM RESOLVED*
Firstly i had to unlock bootloader through fastboot - I haven't checked it at first.
After that I flashed updated firmware from upper post.
Had a lot of problems making fastboot working on my pc, but after few hours spent on searching I finally got it running.
Then I flashed CM13 and it worked !
Thanks for help !
hi, i really want to downgrade my S6 to lollipop but i have one of the latest bootloader (DPFX).
Downgrade was perfectly possible when i was on first build of marshmallow, but now, since i upgraded to DPFX bootloader, i have only fails with odin, and bootloops with custom roms...
is there any solution? if only i could flash an older bootloader, then i will be saved.
but if i flash an old bootloader with odin, i have a fail, so i don't know what to do
Some people suggested to me to use an old TWRP backup and i found it on my pc (with all partitions files: bootloader,system,radio and data, but i didn't use data) but using it, it's the same of flashing a custom rom: bootloop, and i suspect that the old bootloader never was flashed.
help
cescof said:
hi, i really want to downgrade my S6 to lollipop but i have one of the latest bootloader (DPFX).
Downgrade was perfectly possible when i was on first build of marshmallow, but now, since i upgraded to DPFX bootloader, i have only fails with odin, and bootloops with custom roms...
is there any solution? if only i could flash an older bootloader, then i will be saved.
but if i flash an old bootloader with odin, i have a fail, so i don't know what to do
Some people suggested to me to use an old TWRP backup and i found it on my pc (with all partitions files: bootloader,system,radio and data, but i didn't use data) but using it, it's the same of flashing a custom rom: bootloop, and i suspect that the old bootloader never was flashed.
help
Click to expand...
Click to collapse
If you are on a newer mm bootloader then downgrading to lollipop is not possible
sofir786 said:
If you are on a newer mm bootloader then downgrading to lollipop is not possible
Click to expand...
Click to collapse
I knew this, but i want to know if there is a way, a not official way, like reinstalling bootloader in a forced way that doesn't care about security problems... this thing has no sense.... why totally prevent to downgrade? However, i thing it's NORMALLY impossible, but not
TOTALLY impossible
cescof said:
I knew this, but i want to know if there is a way, a not official way, like reinstalling bootloader in a forced way that doesn't care about security problems... this thing has no sense.... why totally prevent to downgrade? However, i thing it's NORMALLY impossible, but not
TOTALLY impossible
Click to expand...
Click to collapse
As far as I know if you're on a newer bootloader official or not there is no current method to downgrade. Maybe a phone shop has specialist equipment to do this but that's me taking a shot in the air
I was able to downgrade but not because i wanted, i flashed a corrupt firmware with ODIN and i have to do an emergency recovery with Smart Switch, my carrier doesn't have Marshmallow on the S6 so my phone restored in Lollipop
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: