i looked in xperifirm didn't see anything other than latest update reason i want old one for usa version now that we have bootloader unlock is to fix the stupid wifi 6e reboot bug that was added with the feb update i think still broken on the latest too.
billycar11 said:
i looked in xperifirm didn't see anything other than latest update reason i want old one for usa version now that we have bootloader unlock is to fix the stupid wifi 6e reboot bug that was added with the feb update i think still broken on the latest too.
Click to expand...
Click to collapse
HI @billycar11 were you able to downgrade the firmware on unlocked bootloader?. Please do let me know if it worked.
ralf_waldo said:
HI @billycar11 were you able to downgrade the firmware on unlocked bootloader?. Please do let me know if it worked.
Click to expand...
Click to collapse
Never found the firmware didn't get to try but I think it is possible with an unlocked bootloader.
But the may update fixed the reboot issue so now I have no need to downgrade
Related
Hi there,
sorry for bothering you with my problem but I really cannot figure out what I am doing wrong. I am running a pure stock version of 4.4.4 on my international version of the moto E, with no root and no unlocked bootloader. I am willing to update to the latest 5.1 build but whitout unlocking the bootloader and stuff.
From what I understand the first step to do so in the easiest way possible would be to download the first 5.0.2 soak (22.21.32 341MB) update and put it into the main SD card. From then the phone should detect the update from the settings, but mine isn't.
I have already tried sideloading the update by going to the recovery and choosing update from adb. Also I have developer options enabled.
Thanks for your help.
kGospel said:
Hi there,
sorry for bothering you with my problem but I really cannot figure out what I am doing wrong. I am running a pure stock version of 4.4.4 on my international version of the moto E, with no root and no unlocked bootloader. I am willing to update to the latest 5.1 build but whitout unlocking the bootloader and stuff.
From what I understand the first step to do so in the easiest way possible would be to download the first 5.0.2 soak (22.21.32 341MB) update and put it into the main SD card. From then the phone should detect the update from the settings, but mine isn't.
I have already tried sideloading the update by going to the recovery and choosing update from adb. Also I have developer options enabled.
Thanks for your help.
Click to expand...
Click to collapse
Well, 1st of all let me tell you, that you are completely going the wrong way.... You DO NOT need to flash 5.0.2.... From what I know, factory images of XT1021 for official Android 5.1 lollipop are available...
Check this LINK
There are three versions, choose the appropriate one. Download it, and use mfastboot to flash the latest FW (Don't worry, because these are signed images and will work on devices with locked bootloader)
If u think that these are quite complicated, just hit the play store, make sure that Motorola Update Services app is updated.... and wait for the OTA.
If you are 100% sure that you have not unlocked the bootloader, then pm me, I will give the instructions to flash the fw.
Cheers
Rohitagni said:
Well, 1st of all let me tell you, that you are completely going the wrong way.... You DO NOT need to flash 5.0.2.... From what I know, factory images of XT1021 for official Android 5.1 lollipop are available...
Check this LINK
There are three versions, choose the appropriate one. Download it, and use mfastboot to flash the latest FW (Don't worry, because these are signed images and will work on devices with locked bootloader)
If u think that these are quite complicated, just hit the play store, make sure that Motorola Update Services app is updated.... and wait for the OTA.
If you are 100% sure that you have not unlocked the bootloader, then pm me, I will give the instructions to flash the fw.
Cheers
Click to expand...
Click to collapse
Thank you for your quick reply. My current firmware is "21.12.40.condor_reteu_reteuall.en.EU reteu" do you think I can safely flash the us retail version via mfastboot?
kGospel said:
Thank you for your quick reply. My current firmware is "21.12.40.condor_reteu_reteuall.en.EU reteu" do you think I can safely flash the us retail version via mfastboot?
Click to expand...
Click to collapse
I am sorry, but I think I made a mistake
The official image is not available for your model at the moment. What u can try is wait for the update to be pushed.
Sorry for the inconvenience.
Rohitagni said:
I am sorry, but I think I made a mistake
The official image is not available for your model at the moment. What u can try is wait for the update to be pushed.
Sorry for the inconvenience.
Click to expand...
Click to collapse
Ok then, thank you anyway, I appreciate your help.
Just a heads up, the new OTA that At&t released has an updated bootloader.
VenomMOD said:
Just a heads up, the new OTA that At&t released has an updated bootloader.
Click to expand...
Click to collapse
Why didn't att just play nice and update to V3? Instead they update To V4 so I can't flip flop between t-mobile firmware and there's. Does root still work? On the other hand, I can flash Verizon firmware I guess.
Ph0nysk1nk said:
Why didn't att just play nice and update to V3? Instead they update To V4 so I can't flip flop between t-mobile firmware and there's. Does root still work? On the other hand, I can flash Verizon firmware I guess.
Click to expand...
Click to collapse
I haven't attempted rooting it, and I won't be. There might be a small chance that it may work but I'm not sure.
VenomMOD said:
I haven't attempted rooting it, and I won't be. There might be a small chance that it may work but I'm not sure.
Click to expand...
Click to collapse
Well ... if root doesn't work I know what my next firmware will be. (Tmobile)
I can't root, looks like it's back to the drawing board. It figures this happen as soon as I feel it necessary to root my device......
I advise everyone to not take any OTAs after the first August patch so you can still be able to root and flash roms. It isn't a problem for me since I wasn't planning on rooting this phone again anyways..
VenomMOD said:
I advise everyone to not take any OTAs after the first August patch so you can still be able to root and flash roms. It's sad to see this happen, but it isn't a problem for me since I wasn't planning on rooting this phone again anyways..
Click to expand...
Click to collapse
Pretty sure the eng boot will still work on the new BL, just no old ROMs. :^)
MFW just read those posts above me.
raremind said:
I can't root, looks like it's back to the drawing board. It figures this happen as soon as I feel it necessary to root my device......
Click to expand...
Click to collapse
Did you use the engboot root method?
SkyAttacksX said:
Pretty sure the eng boot will still work on the new BL, just no old ROMs. :^)
MFW just read those posts above me.
Click to expand...
Click to collapse
@raremind couldn't root on BL4. It's unfortunate how we can't root on API2, but if the developers are willing to find out a new way to gain root access on API2, then it wouldn't be the end of the world for anyone who wants the latest OTA but still want root.
Can someone post link to download latest update
sandeep.manugunta said:
Can someone post link to download latest update
Click to expand...
Click to collapse
I took the OTA to get the latest version, so unfortunately I don't have the actual firmware link.
Ph0nysk1nk said:
Why didn't att just play nice and update to V3? Instead they update To V4 so I can't flip flop between t-mobile firmware and there's. Does root still work? On the other hand, I can flash Verizon firmware I guess.
Click to expand...
Click to collapse
Tmobile also updated their firmware to V4 with the recent update from 9/27
http://www.sammobile.com/firmwares/database/SM-G930T/
I covered this here: http://forum.xda-developers.com/att-s7-edge/help/att-t-mobile-bootloader-version-t3473281
Can the U firmware still be flashed?
No, it cant.
joe3681 said:
Can the U firmware still be flashed?
No, it cant.
Click to expand...
Click to collapse
No one can until the U firmware is updated to bootloader 4.
VenomMOD said:
No one can until the U firmware is updated to bootloader 4.
Click to expand...
Click to collapse
Yeahhh, thought I'd give it a go
G930U firmware was just updated to API3 which has the incremented bootloader, so the individuals who updated to the latest AT&T firmware can use U firmware now. :victory:
EDIT: Here is @joe3681 's thread that has the download to the firmware.
http://forum.xda-developers.com/att...4api3-firmware-download-t3481159#post69147585
>Update: Links were taken down.
Hello,
I have the following phone:
Moto Z
XT1650-03
RETEU
Android 6.0.1 MPL24.246-45
When I got the phone I only unlocked the bootloader en flashed TWRP recovery.
Now the Android 7 OTA update is released. I got the popup for de OTA update but it wasn't able to install the update because of TWRP Recovery.
After that I flashed the recovery with a stock recovery from the stock Android 6.0.1 MPL24.246-17 ROM, found in a Moto Z official/stock ROM forum here on XDA. After that I downloaded the OTA update again on my Moto Z, it starts with installing the update, then it restarts in recovery, it seems work fine when I see the stock recovery screen with installing the update, but after a few minutes I get an "Error!" with the "Android man with open belly" symbol. Luckily the phone stil boots and is working fine.
What's going wrong with the OTA update? Mismatch between the rom (MPL24.246-45) and recovery (MPL24.246-17) version?
My goal is to get stock Android 7 on my Moto Z. Who can tell me what's the best step for me to achieve this? Should I try another recovery to get the OTA update working?
Thank you!
Same happened to me when i tried updating the new 540mb update over Nougat. I think it happened because of the kernel (disabling force encryption), not sure :/
Manish54 said:
Same happened to me when i tried updating the new 540mb update over Nougat. I think it happened because of the kernel (disabling force encryption), not sure :/
Click to expand...
Click to collapse
Ok, thank you for your answer. But I did not do anything with encryption... And how did you solve this, are you able to install that update now?
I gave my phone to the service center today and told them that it happened after the OTA update. I have my fingers crossed that they don't find out about the unlocked bootloader before fixing it.
wmerbe38 said:
...
What's going wrong with the OTA update? Mismatch between the rom (MPL24.246-45) and recovery (MPL24.246-17) version?
My goal is to get stock Android 7 on my Moto Z. Who can tell me what's the best step for me to achieve this? Should I try another recovery to get the OTA update working?
Thank you!
Click to expand...
Click to collapse
Possible. Flash stock recovery from Rogers firmware which is a -45 subrelease.
Anyway I wouldn't upgrade by OTA...
enetec said:
Possible. Flash stock recovery from Rogers firmware which is a -45 subrelease.
Anyway I wouldn't upgrade by OTA...
Click to expand...
Click to collapse
Do you mean the Rogers firmware from this forum?
https://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095
wmerbe38 said:
Do you mean the Rogers firmware from this forum?
https://forum.xda-developers.com/moto-z/how-to/update-to-7-0-nougat-xt1650-03-retus-t3513095
Click to expand...
Click to collapse
Yes, that one.
enetec said:
Yes, that one.
Click to expand...
Click to collapse
Ok, I already flashed de stock .45 Recovery from Rogers.
My plan is the following:
- Reset device to factory defaults
- Download the OTA update to the device, just how it's meant to be
- See if it wil update successfully now
Or what can you recommend me to get to fully stock Nougat? This one:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Or wait and stay on Android 6.0.1 till there is more information/ROM's/updates about this device? I know something about flashing/ROM's (before I had a OnePlus One with Cyanogen) but not as much as you guys do and I don't want to brick my device
wmerbe38 said:
Ok, I already flashed de stock .45 Recovery from Rogers.
My plan is the following:
- Reset device to factory defaults
- Download the OTA update to the device, just how it's meant to be
- See if it wil update successfully now
Or what can you recommend me to get to fully stock Nougat? This one:
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Or wait and stay on Android 6.0.1 till there is more information/ROM's/updates about this device? I know something about flashing/ROM's (before I had a OnePlus One with Cyanogen) but not as much as you guys do and I don't want to brick my device
Click to expand...
Click to collapse
Second choice is the (safe...) way to go...
Hi there,
Now that Magisk won't install on ALP-L29 8.0.0.138 C636patch01 (july 1st security patch), is there a way to root with this firmware and especially this security patch?
Regards,
Does anyone know how to root this firmware version? Been scouring the web all week with no information
You should be able to downgrade to B138 using eRecovery, this would remove Patch01.
ante0 said:
You should be able to downgrade to B138 using eRecovery, this would remove Patch01.
Click to expand...
Click to collapse
this need unlocked bootloader too? because i tried but faild to get package.
hamadazh said:
this need unlocked bootloader too? because i tried but faild to get package.
Click to expand...
Click to collapse
No, unlock is not needed for eRecovery.
However, if you rebranded eRecovery will usually fail to get package.
ante0 said:
No, unlock is not needed for eRecovery.
However, if you rebranded eRecovery will usually fail to get package.
Click to expand...
Click to collapse
yes it's debranded it was ALP-AL00 and now ALP-L29.
fastboot can flash stock RAMDISK without unlocked bootliader?
hamadazh said:
yes it's debranded it was ALP-AL00 and now ALP-L29.
fastboot can flash stock RAMDISK without unlocked bootliader?
Click to expand...
Click to collapse
No way to do it.
Only way you could try is dload to B138, BUT I'm not certain what happens if you're now on 02 xloader.
ante0 said:
No way to do it.
Only way you could try is dload to B138, BUT I'm not certain what happens if you're now on 02 xloader.
Click to expand...
Click to collapse
but i read in some places and someone confirm 8.0.0.138 01patch is 01xloader, but i think or maybe the problem is from the newer security patch 1 july 2018. Funky huwaei support team told me that they can't read bootloader or rebrand also said erecovery will not working after debrand since 01 july newer security patch.
the problem too is i went to teammt.ru site for downloading 8.0.0.138 full rom but it's not available to download. maybe FF working not tried, but anyway i think i have to live with this, until huawei open unlock bootloader service again.
How to root in Patch01 update : https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
does anyone have a ramdisk of alp 29 ?
Hi there everyone! I was wondering in what security patch are you at the moment and im what country did you get the latest update. I'm unable to find the ota file over internet so I'm doubting if in fact Nokia did release updates.
Greetings all!
I'm on September's, and I believe everyone else is too
Yup. September update too.
My MiA1 has already gotten November update ?
November 5th security update. Received OTA today.
Yup, got the Nov 5th update last night.
Was hoping it was Android10 update tho... ?
Does the OTA brick unlocked devices?
Does it remove the option to unlock the bootloader in the dev settings?
Ungewiss said:
Does it remove the option to unlock the bootloader in the dev settings?
Click to expand...
Click to collapse
To answer myself: upgraded my wife's Nokia 7.2 and the oem unlock option is still there.
Ungewiss said:
To answer myself: upgraded my wife's Nokia 7.2 and the oem unlock option is still there.
Click to expand...
Click to collapse
Thanks!
Was it already unlocked on hers? Just so I know if I can update my wife's without bricking the device.
Kikk0r said:
Thanks!
Was it already unlocked on hers? Just so I know if I can update my wife's without bricking the device.
Click to expand...
Click to collapse
No, I did not unlock, yet. Don't have time to backup/restore everything right now - without root access this is really cumbersome..