Related
Hi everyone,
I have D6603 with with Android 5.1.1 (23.4.A.0.546) with an unlocked bootloader (done per instructions on Sony's website).
For a while now I've noticed that the device overheats when I use the camera for a few minutes. According to this article,
the new update Sony have released, is supposed to mitigate the problem.
I cannot update my phone to the new Android version, because of the unlocked bootloader.
Can/should I re-lock the bootloader? Or is there a way to stop the overheating issue?
beentold82 said:
Hi everyone,
I have D6603 with with Android 5.1.1 (23.4.A.0.546) with an unlocked bootloader (done per instructions on Sony's website).
For a while now I've noticed that the device overheats when I use the camera for a few minutes. According to this article,
the new update Sony have released, is supposed to mitigate the problem.
I cannot update my phone to the new Android version, because of the unlocked bootloader.
Can/should I re-lock the bootloader? Or is there a way to stop the overheating issue?
Click to expand...
Click to collapse
You can still update to the latest firmware with flashtool.
Beetle84 said:
You can still update to the latest firmware with flashtool.
Click to expand...
Click to collapse
Thanks for the info Beetle. May I be so rude to ask you, where I can get the most up to date flashable ROM?
I did unlock the bootloader, but never managed to install a recovery mod or get root.
[/COLOR]
beentold82 said:
Thanks for the info Beetle. May I be so rude to ask you, where I can get the most up to date flashable ROM?
I did unlock the bootloader, but never managed to install a recovery mod or get root.
Click to expand...
Click to collapse
In flashtool theres a button labelled xperifirm, if you click that and follow the instructions you can download a ftf directly.
As for root and recovery, you can use this guide http://forum.xda-developers.com/z3/general/guide-rootrecovery-how-to-root-install-t3017056 , and then create a pre rooted 5.1.1 firmware from here http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Or you can install androplus kernel http://forum.xda-developers.com/z3/development/kernel-andropluskernel-t2925999 after you upgrade to stock 5.1.1 with fastboot, and skip the whole downgrade to kit kat which would be alot quicker.
Wow, that seems easy enough. I'll try it later tonight. Thanks again!
beentold82 said:
Wow, that seems easy enough. I'll try it later tonight. Thanks again!
Click to expand...
Click to collapse
No worries, good luck. You may have to disable virus protection to download xz dual recovery installer, well, I have to anyway, my VP doesnt like the install.bat file.
EDIT: isn't the .546 the latest?
Not sure... My phone tells me there is a system update, but it always fails because of the unlocked bootloader.
robogo1982 said:
EDIT: isn't the .546 the latest?
Click to expand...
Click to collapse
23.4.A.1.264 is I believe.
I've a device that is S-ON , TWRP 3.0.2-0 recovery installed , unlocked USA. Was running CM13 and later a lineage build...i just wiped/ reflashed the stock boot and system image so i've got things more or less back to original. All's good. However my bootloader remains unlocked. Do i need to relock it to get Android Pay working again? I was able to add a card, but have not tested it in the real world yet. My understanding is locking the bootloader will erase my data. Given I'd like to try that Nougat flavor and I don't think that will come OTA with an unlocked bootloader, maybe now's the time sense I think i'll have to flash that manually
Sorry, still new to joy of working with these devices. Fun tho
mlecho said:
I've a device that is S-ON , TWRP 3.0.2-0 recovery installed , unlocked USA. Was running CM13 and later a lineage build...i just wiped/ reflashed the stock boot and system image so i've got things more or less back to original. All's good. However my bootloader remains unlocked. Do i need to relock it to get Android Pay working again? I was able to add a card, but have not tested it in the real world yet. My understanding is locking the bootloader will erase my data. Given I'd like to try that Nougat flavor and I don't think that will come OTA with an unlocked bootloader, maybe now's the time sense I think i'll have to flash that manually
Sorry, still new to joy of working with these devices. Fun tho
Click to expand...
Click to collapse
No, if Android pay has a problem, it will reject you DURING the process of adding a card, if you add a card sucussfully, your good to go.
If you want to try nougat, please note that that change is irreversible. The firmware is non-downgradeable. I don't think locking the bootloader will erase data, but if it does it PROBABLY will warn you.
The_scam said:
No, if Android pay has a problem, it will reject you DURING the process of adding a card, if you add a card sucussfully, your good to go.
If you want to try nougat, please note that that change is irreversible. The firmware is non-downgradeable. I don't think locking the bootloader will erase data, but if it does it PROBABLY will warn you.
Click to expand...
Click to collapse
Thanks for all that...just to be clear, the only way to get Nougat is to flash it ? or is it also OTA?
mlecho said:
Thanks for all that...just to be clear, the only way to get Nougat is to flash it ? or is it also OTA?
Click to expand...
Click to collapse
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
The_scam said:
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
Click to expand...
Click to collapse
Sorry I have a question, I have an A9 (European model) S-ON with CM 14.1 and I would like to get S-OFF in order to back to stock. The problem is that I have read that Sunshine only works with stock ROM and, out of the box, my phone came with vodafone uk ROM and I can't find, on the internet, the exact same ROM as mine ( I have found an older version but because I have S-ON I can't downgrade ). There is another way to make Sunshine works? Thanks in advance
Lolli26 said:
Sorry I have a question, I have an A9 (European model) S-ON with CM 14.1 and I would like to get S-OFF in order to back to stock. The problem is that I have read that Sunshine only works with stock ROM and, out of the box, my phone came with vodafone uk ROM and I can't find, on the internet, the exact same ROM as mine ( I have found an older version but because I have S-ON I can't downgrade ). There is another way to make Sunshine works? Thanks in advance
Click to expand...
Click to collapse
what is your rom version number/firmware version 1.57?
The_scam said:
what is your rom version number/firmware version 1.57?
Click to expand...
Click to collapse
No my firmware version is 1.62.161.2
Lolli26 said:
No my firmware version is 1.62.161.2
Click to expand...
Click to collapse
i cant find anything either, i guess you'll have to wait until the rom is released.
The_scam said:
It is an OTA, you can have s-on, but you can't have an unlocked bootloader, root, or system modifications if any kind.
Click to expand...
Click to collapse
ahh, so i will need to re-lock if i want this OTA.
And btw, Android Pay worked, just as you said it would!
mlecho said:
ahh, so i will need to re-lock if i want this OTA.
And btw, Android Pay worked, just as you said it would!
Click to expand...
Click to collapse
Good, I think you can download the ota and sideload it, should be in one of the general threads. Think it's called any news on 7.0
So, after all this, i had Android Pay (AP) working great w/ 1.57.617.60 flashed back to my phone. I never re-locked my bootloader. This a.m. i flashed nougat, both boot and system (RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1) - All's great. However while shopping i was rejected by AP with the message in the attached screen shot. Is this because i never re-locked the bootloader? What are the consequences by doing so? Can I eventually re-unlock for future flashing?
NOTE - my device is not rooted, despite the accusations from the modal!
mlecho said:
So, after all this, i had Android Pay (AP) working great w/ 1.57.617.60 flashed back to my phone. I never re-locked my bootloader. This a.m. i flashed nougat, both boot and system (RUU_HIA_AERO_UL_N70_SENSE80GP_ATT_MR_NA_Gen_Unlock_2.18.617.1) - All's great. However while shopping i was rejected by AP with the message in the attached screen shot. Is this because i never re-locked the bootloader? What are the consequences by doing so? Can I eventually re-unlock for future flashing?
NOTE - my device is not rooted, despite the accusations from the modal!
Click to expand...
Click to collapse
In nougat, it checks for unlocked bootloaders sadly you can't relock bootloader in nougat.
The_scam said:
In nougat, it checks for unlocked bootloaders sadly you can't relock bootloader in nougat.
Click to expand...
Click to collapse
oh no...really? no 'fastboot oem lock'? crap. Perhaps the "upgrade" was a mistake. So i'm without?
mlecho said:
oh no...really? no 'fastboot oem lock'? crap. Perhaps the "upgrade" was a mistake. So i'm without?
Click to expand...
Click to collapse
Yep, looks like it unless you downgrade and relock bootloader, then upgrade back to nougat
MGfusion said:
Yep, looks like it unless you downgrade and relock bootloader, then upgrade back to nougat
Click to expand...
Click to collapse
My goal was keep su and also get nougat. A9 has the bug about OEM unlocking just like all other 7.0 devices. It will most likely get fixed at 7.1.1, the nexuses and all other devices running 7.0 seem to have this "bug"
The_scam said:
My goal was keep su and also get nougat. A9 has the bug about OEM unlocking just like all other 7.0 devices. It will most likely get fixed at 7.1.1, the nexuses and all other devices running 7.0 seem to have this "bug"
Click to expand...
Click to collapse
ahh, so that means, as i understand it, if all goes to plan, we should one day expect a 7.1.1 update that will allow me to finally get back to AP?
mlecho said:
ahh, so that means, as i understand it, if all goes to plan, we should one day expect a 7.1.1 update that will allow me to finally get back to AP?
Click to expand...
Click to collapse
As long as you don't care about root. You can always downgrade to mm, lock, and OTA back to nougat
The_scam said:
As long as you don't care about root. You can always downgrade to mm, lock, and OTA back to nougat
Click to expand...
Click to collapse
ok, but just so i am clear , if i lock while in nougat, there's no going back ? i can not then unlock and downgrade?
mlecho said:
ok, but just so i am clear , if i lock while in nougat, there's no going back ? i can not then unlock and downgrade?
Click to expand...
Click to collapse
No, you can only UNLOCK in nougat. If you want to relock the bootloader, you will have to downgrade to marshmallow and loose your root, or wait for Android 7.1.1
downgrade means i have to wipe data, right? The upgrade that was not the case. I am only assuming
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:
Hi, is It possible to relock bootloader for to have warranty back?
Thanks
once you flash the stock img, it will be locked again.
Till Nougat, we had dload method which locks it fully (other method for unlocking it would just re-lock it)
shashank1320 said:
once you flash the stock img, it will be locked again.
Till Nougat, we had dload method which locks it fully (other method for unlocking it would just re-lock it)
Click to expand...
Click to collapse
Hey, i am in the same situation and after flashing the stock rom + stock recovery my bootloader is still unlocked, and i still get that "This device has been unlocked and can't be trusted" screen on boot.
Is there any way to manually lock the bootloader?
Edit: i found this SRKTool and i was able to easily relock the bootloader. You need the Unlock code though and it resets your phone, so backup your data.
https://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797 @alboz83
Arrandale said:
Hey, i am in the same situation and after flashing the stock rom + stock recovery my bootloader is still unlocked, and i still get that "This device has been unlocked and can't be trusted" screen on boot.
Is there any way to manually lock the bootloader?
Edit: i found this SRKTool and i was able to easily relock the bootloader. You need the Unlock code though and it resets your phone, so backup your data.
https://forum.xda-developers.com/mate-8/development/[email protected]
Click to expand...
Click to collapse
Yes it will only relock the bootloader but not lock. Anyone experienced with this can get this that you had unlocked your bootloader earlier
Arrandale said:
Hey, i am in the same situation and after flashing the stock rom + stock recovery my bootloader is still unlocked, and i still get that "This device has been unlocked and can't be trusted" screen on boot.
Is there any way to manually lock the bootloader?
Edit: i found this SRKTool and i was able to easily relock the bootloader. You need the Unlock code though and it resets your phone, so backup your data.
https://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797 @alboz83
Click to expand...
Click to collapse
I relocked yesterday bootloader and my relocated easily. I can not find the update of stock firmware. Once found update. I clicked on update, update failed. I have not got the update since then. So I did relock. Very easy to relock. But my mobile update is not happening. Please give me some help
Sent from my [device_name] using XDA-Developers Legacy app
shashank1320 said:
once you flash the stock img, it will be locked again.
Till Nougat, we had dload method which locks it fully (other method for unlocking it would just re-lock it)
Click to expand...
Click to collapse
Many people say that if we flash stock rom the bootloader stay unlock. Or i have to flash in a particular mode?
With the tool i can relock but not lock, right?
alboz83 said:
Many people say that if we flash stock rom the bootloader stay unlock. Or i have to flash in a particular mode?
With the tool i can relock but not lock, right?
Click to expand...
Click to collapse
Yup
i Read somewhere that if u flash the stock rom using dload after u have relocked the bootloader, the bootloader status will change from relock to locked. does this work? can anyone try and confirm this? i want to make sure of this before i unlock. I would be greatful forever.
Thanks
Anzee said:
i Read somewhere that if u flash the stock rom using dload after u have relocked the bootloader, the bootloader status will change from relock to locked. does this work? can anyone try and confirm this? i want to make sure of this before i unlock. I would be greatful forever.
Thanks
Click to expand...
Click to collapse
Have tried to this more than 100 times and it works fine. It will be locked BL rather than relock
shashank1320 said:
Have tried to this more than 100 times and it works fine. It will be locked BL rather than relock
Click to expand...
Click to collapse
If u flash stock?
Thank you thank you thank you you're a life saver ♥
Anzee said:
If u flash stock?
Thank you thank you thank you you're a life saver ♥
Click to expand...
Click to collapse
Yes. Did you solve the BL state?
shashank1320 said:
Yes. Did you solve the BL state?
Click to expand...
Click to collapse
No I haven't even unlocked the bl yet. I just wanted to make sure it the relock to lock state was possible before I unlock. I will do so soon when I get some time.
Anzee said:
No I haven't even unlocked the bl yet. I just wanted to make sure it the relock to lock state was possible before I unlock. I will do so soon when I get some time.
Click to expand...
Click to collapse
Yes you can always do via full ota or flashing the stock firmware via dload. Not hard to do to retain warranty:silly:
shashank1320 said:
Have tried to this more than 100 times and it works fine. It will be locked BL rather than relock
Click to expand...
Click to collapse
But dload method not work only for a single update.app file? With view 10 there are 3 files
alboz83 said:
But dload method not work only for a single update.app file? With view 10 there are 3 files
Click to expand...
Click to collapse
Use the first file, update.zip. it will contain a update.app file around 3 GB. Can use this single file.
shashank1320 said:
Use the first file, update.zip. it will contain a update.app file around 3 GB. Can use this single file.
Click to expand...
Click to collapse
Really? And I have to install over the same firmware, not an update? For example, now I'm on 162 build with unlock bootloader. If I install only update.zip of 162 build with dload method, I obtain the lock bootloader?
alboz83 said:
Really? And I have to install over the same firmware, not an update? For example, now I'm on 162 build with unlock bootloader. If I install only update.zip of 162 build with dload method, I obtain the lock bootloader?
Click to expand...
Click to collapse
Yes.
hello all guys!
i have honor 10 (now col-l29)
before rebranding (col-tl10)
may i relock the BL safety?? i have official rom
ecsalos said:
hello all guys!
i have honor 10 (now col-l29)
before rebranding (col-tl10)
may i relock the BL safety?? i have official rom
Click to expand...
Click to collapse
Why you want to relock, to gain warranty?
If so, better dload the current firmware and it will lock it safely.
because, i dont want to see everytime when i reboot my phone,this stupid message, who tells me that i have unlock bl...
i have 8.1.0.151 (c432)
i was downloaded this version when im trying to rebranding.. for official site..
if i relock with this version, the worse scenario it will be...??? brick???
if i dload the current firmware, i will install it with TWRP again? and after it will be locked safety?
and what firmware i must to dload?
hi, anyone has some kind of advice to flash old firmware as the newest have a lot of problems in terms of camera quality ? i don't have rooted my pixel 7 pro ...
Albi Lukaj said:
hi, anyone has some kind of advice to flash old firmware as the newest have a lot of problems in terms of camera quality ? i don't have rooted my pixel 7 pro ...
Click to expand...
Click to collapse
You can install the OTA update from here. Just follow the instructions Google provided at the top of the page and you should be all updated. It's only the full images that require the bootloader to be unlocked.
Just go look up factory images for Pixel phones. You can install firmware right from the web browser. You don't need to have root. Root is optional.
Do you mean without an unlocked bootloader? Root is not the same thing and does not determine how you can flash firmware.
If your bootloader is unlocked, you can use the Android Flash Tool. If your bootloader is not unlocked, downgrading is impossible.
UltimateGamer83 said:
Just go look up factory images for Pixel phones. You can install firmware right from the web browser. You don't need to have root. Root is optional.
Click to expand...
Click to collapse
This only works if OEM Unlocking is enabled in Developer Options.
V0latyle said:
Do you mean without an unlocked bootloader? Root is not the same thing and does not determine how you can flash firmware.
If your bootloader is unlocked, you can use the Android Flash Tool. If your bootloader is not unlocked, downgrading is impossible.
This only works if OEM Unlocking is enabled in Developer Options.
Click to expand...
Click to collapse
so i just need to unlock the bootloader and then i can install old firmware following the procedure ?
Albi Lukaj said:
so i just need to unlock the bootloader and then i can install old firmware following the procedure ?
Click to expand...
Click to collapse
Yes
Albi Lukaj said:
so i just need to unlock the bootloader and then i can install old firmware following the procedure ?
Click to expand...
Click to collapse
@Albi Lukaj, Please be aware that unlocking your bootloader WILL WIPE YOUR DEVICE AND RETURN IT TO STOCK!!!
If that is not preferable, you might try applying the OTA like stated in Post #2, but I am not sure if it works downgrading a version (it probably doesn't)...