link :HERE
For XT1572 (Indian Variant Only)
tested works fine.
ADB Sideload
1. Place the ZIP file in your adb/fastboot directory
2. Reboot to the bootloader and start (stock) recovery
3. At the "dead Andy" with a red exclamation, press POWER+VolUp to get to the stock recovery menu
4. Select "Apply update from ADB"
5. On computer, enter "adb sideload <filename>" but replace <filename> with the OTA ZIP image
6. Wait for the process to finish...
There is other sd card method also but i don't recommend you to follow that as it is a bit tricky.
Edit: this will only work for Blur_Version.24.231.16.clark_retasia_ds.retasia.en .03
Do not attempt to flash or your device will be hard bricked
Thanks a lot. Will try flashing this tomorrow
Working for XT1575?
I have a Moto X Style (XT1572) Double SIM Android 6.0.1 Rom Stock (24.231.13.clark_retasia_ds.retasia.en.03 retmea).
Does it fit for this version?
Sagar_1401 said:
link :HERE
tested works fine.
ADB Sideload
1. Place the ZIP file in your adb/fastboot directory
2. Reboot to the bootloader and start (stock) recovery
3. At the "dead Andy" with a red exclamation, press POWER+VolUp to get to the stock recovery menu
4. Select "Apply update from ADB"
5. On computer, enter "adb sideload <filename>" but replace <filename> with the OTA ZIP image
6. Wait for the process to finish...
There is other sd card method also but i don't recommend you to follow that as it is a bit tricky.
Click to expand...
Click to collapse
Why is the SD card method trickier? You put the OTA(blur) file on your SD card and in stock recovery select "apply update from sd card" and you don't even need a computer. What's so tricky in this?
Javi_Racing said:
I have a Moto X Style (XT1572) Double SIM Android 6.0.1 Rom Stock (24.231.13.clark_retasia_ds.retasia.en.03 retmea).
Does it fit for this version?
Click to expand...
Click to collapse
It does not correspond to my version, I have to keep waiting. :crying:
oliake said:
Working for XT1575?
Click to expand...
Click to collapse
Not sure, but I think if you do use the OTA for the style it will change your phone model in "about phone". Not sure if it changes anything else or if that negatively affects anything though
redemptionx11 said:
Not sure, but I think if you do use the OTA for the style it will change your phone model in "about phone". Not sure if it changes anything else or if that negatively affects anything though
Click to expand...
Click to collapse
The only thing I want to know is if it can boot. I see you don't have an answer for that but let's hope someone dares to try before me
oliake said:
The only thing I want to know is if it can boot. I see you don't have an answer for that but let's hope someone dares to try before me
Click to expand...
Click to collapse
Well, I tried to use one of the first style nougat updates that came out. Couldn't get it to boot. Ended up having to wipe everything and revert to stock 6.0, then reflash the ROM I wanted. It was enough trouble that I'm waiting for some solid answers before I try again. Lol.
redemptionx11 said:
Well, I tried to use one of the first style nougat updates that came out. Couldn't get it to boot. Ended up having to wipe everything and revert to stock 6.0, then reflash the ROM I wanted. It was enough trouble that I'm waiting for some solid answers before I try again. Lol.
Click to expand...
Click to collapse
Unlucky you You flashed it on the XT1575 right?
oliake said:
Unlucky you You flashed it on the XT1575 right?
Click to expand...
Click to collapse
The one I did was that nandroid restore thing.
redemptionx11 said:
The one I did was that nandroid restore thing.
Click to expand...
Click to collapse
Yea but what I meant was what the actual version of the phone you have
Because this always comes up, I downloaded and looked at this OTA...
Your device MUST have the following release keys to work:
motorola/clark_retasia_ds/clark_ds:6.0/MPHS24.49-18-16/12:user/release-keys, also know as Blur_Version.24.231.16.clark_retasia_ds.retasia.en.03
That is the ONLY version this OTA will work on, you must be on build MPHS24.49-18-16 retasia dual SIM, this OTA cannot be applied to ANY OTHER DEVICE or BUILD... don't do it, don't try, don't force it... if it does somehow magically work (or you figure how to force it) you device will be inoperable, possibly hard bricked.
Moto OTA's are differential files, so each piece for each file only includes what is different than the known value from the previous build, that is why these OTA's are so dangerous, they do not replace entire file but patch existing ones with the specific bits that are different only... if it fails or the files are not as expected bad things can and will happen.
BTW, the informtion to decipher what build you have to be on and what it will go to is inside the OTA zip file, in a file called metadata.json
acejavelin said:
Because this always comes up, I downloaded and looked at this OTA...
Your device MUST have the following release keys to work:
motorola/clark_retasia_ds/clark_ds:6.0/MPHS24.49-18-16/12:user/release-keys, also know as Blur_Version.24.231.16.clark_retasia_ds.retasia.en.03
That is the ONLY version this OTA will work on, you must be on build MPHS24.49-18-16 retasia dual SIM, this OTA cannot be applied to ANY OTHER DEVICE or BUILD... don't do it, don't try, don't force it... if it does somehow magically work (or you figure how to force it) you device will be inoperable, possibly hard bricked.
Moto OTA's are differential files, so each piece for each file only includes what is different than the known value from the previous build, that is why these OTA's are so dangerous, they do replace entire file but patch existing ones... if it fails or the files are not as expected bad things can and will happen.
BTW, the informtion to decipher what build you have to be on and what it will go to is inside the OTA zip file, in a file called metadata.json
Click to expand...
Click to collapse
Exactly I have "I have a Moto X Style (XT1572) Double SIM Android 6.0.1 Rom Stock (24.231.13.clark_retasia_ds.retasia.en.03 retmea)" so I could not perform the update of this OTA
Javi_Racing said:
Exactly I have "I have a Moto X Style (XT1572) Double SIM Android 6.0.1 Rom Stock (24.231.13.clark_retasia_ds.retasia.en.03 retmea)" so I could not perform the update of this OTA
Click to expand...
Click to collapse
Yes, as long as you are on the correct build stated previously, and you are unmodified stock, no root, stock recovery, untouched /system, radio, and /boot partitions, then you can just install with adb sideload and go.
Was I unclear in my previous post?
acejavelin said:
Because this always comes up, I downloaded and looked at this OTA...
Your device MUST have the following release keys to work:
motorola/clark_retasia_ds/clark_ds:6.0/MPHS24.49-18-16/12:user/release-keys, also know as Blur_Version.24.231.16.clark_retasia_ds.retasia.en.03
That is the ONLY version this OTA will work on, you must be on build MPHS24.49-18-16 retasia dual SIM, this OTA cannot be applied to ANY OTHER DEVICE or BUILD... don't do it, don't try, don't force it... if it does somehow magically work (or you figure how to force it) you device will be inoperable, possibly hard bricked.
Moto OTA's are differential files, so each piece for each file only includes what is different than the known value from the previous build, that is why these OTA's are so dangerous, they do not replace entire file but patch existing ones with the specific bits that are different only... if it fails or the files are not as expected bad things can and will happen.
BTW, the informtion to decipher what build you have to be on and what it will go to is inside the OTA zip file, in a file called metadata.json
Click to expand...
Click to collapse
Should have added that but now I've added this.. Thank you
@Sagar_1401 thanks for capturing and uploading the OTA
Though it's really sad there is no VoLTE support
aakashverma0007 said:
@Sagar_1401 thanks for capturing and uploading the OTA
Though it's really sad there is no VoLTE support
Click to expand...
Click to collapse
yeah we need volte feature
Sagar_1401 said:
yeah we need volte feature
Click to expand...
Click to collapse
Could you explain me why it's so important to you? What are real benefits of Volte
Sent from my XT1572 using XDA-Developers Legacy app
2be3_80 said:
Could you explain me why it's so important to you? What are real benefits of Volte
Sent from my XT1572 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Last year one of the biggest Mobile Service Provider launched 4G/LTE Services with Free Internet for about 6-7months straight. Also with Free Unlimited International over VoLTE feature. Currently the Free Data Services has ended but the Free Calling is still there.
It was kinda Wreaking Ball for other providers. Basically VoLTE is important for Indian users.
Hope they give us update for Modem supporting VoLTE.
P.S: It's Reliance Jio, Google it.
Related
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Hi. I don't suppose the end result would be different, whatever method you choose.
athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
athani said:
Hi. I don't suppose the end result would be different, whatever method you choose.
Click to expand...
Click to collapse
AFAICT this seems true, you I could run a leak#2/soak based ROM as a second system (first system too?) with boot menu manager by following the guides:
http://forum.xda-developers.com/showthread.php?t=1779968
http://forum.xda-developers.com/showthread.php?t=1882335
jboxer said:
Where does moto put the zip file so I can try putting it where the OTA would have downloaded to? Then when I go to check for update it should say an update is ready for installing. Do they put it in the cache directory? Someone who knows please let me know. Thanks.
Click to expand...
Click to collapse
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
alteredlikeness said:
Yes, it is /cache... but I think you also need the .crc file of the same name along with the actual .zip - not positive though. And, it can take a little while for it to recognize it - but I have done it that way, by putting it in the cache folder - also, it will disappear if you reboot.
But, you do know what you are doing, right? There is no fxz yet...
---------- Post added at 08:17 AM ---------- Previous post was at 08:12 AM ----------
Edit.. since it's the same files as leak#2.. for the .crc file, you could just make your own if you don't have it:
-Just create a new blank file with notepad++
-Add this as the first and only line (no blank lines after)
Code:
3114145323
-Then, save it as Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
jboxer said:
Yes, I know what I am doing. I used to develop roms for LG P999 but have not played around with my Atrix much. LG does their OTA updates very differently and downloads them in pieces all over the place so no way to use the method I am suggesting for the Atrix. I don't care about being able to fxz back as I just want the phone on official ICS; but I do appreciate your caveat. Thanks for the reply.
If anyone has the .crc file please upload somewhere so I can grab it. Thanks.
Click to expand...
Click to collapse
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
alteredlikeness said:
I know you know what you are doing.. just had to throw that in there..
Here's the .crc file from the last leak from 9/5/12... should be the same as the soak one: https://dl.dropbox.com/u/61960599/Leak_09.05.12/Blur_Version.55.13.25.MB865.ATT.en.US.crc
Click to expand...
Click to collapse
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Also I do not think you can be rooted to update the check will prevent you from updating, also you have to be as close as stock as you can..... Meaning all bloat must be unfroze.....
One more note there is a Q&A section now so try to post questions there.....
jboxer said:
I was supposed to be part of the soak but for some reason my phone is invisible to the Moto update servers and they cannot push the update to me. I have the update file someone gave me a link to download. I have two questions about how to install it.
1. Since I am rooted can I just put it where Moto would have downloaded it to and then my phone will update it like it got the OTA?
or
2. If I install it off the SD card will it just do recovery first and then display injured android man, and then have to reselect the zip package again to finish instlling the update?
I would prefer method 1 if possible. If one of the devs or a knowledgeable person could respond I would appreciate it. I'll give Moto about six more hours to get this straightened out, otherwise I am tired of waiting to get my Atrix 2 onto ICS.
Click to expand...
Click to collapse
Can you share the link of the update file?
Thanks
jboxer said:
Thanks. I will give them a few hours to get to work and see if my phone is visible to the update servers now that I have done an FDR as they requested. If so, I will just let the OTA do its thing. If not I will manually update my phone.
Click to expand...
Click to collapse
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
You can be rooted. The update asserts only check for the original system files to make sure they have not been modified or deleted. It does not check for extra files like superuser.apk or busybox. Rooting is not a problem. I set superuser to OTA protect and it worked. After the update my ICS was still rooted without me having to root it.
For the person that wants the leak the OTA is leak # 2. It is exactly the same. Just find thread with download link for leak # 2 and you are good to go.
Would installing beats audio drivers using the app be considered tampering with system files? And would it prevent me from receiving a ota?
Sent from my MB865 using xda premium
athani said:
Could the fact that you're not in the US, are now unlocked and on another network have something with failure to get the OTA!?
Click to expand...
Click to collapse
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
ramosquera said:
Can you share the link of the update file?
Thanks
Click to expand...
Click to collapse
The devs have confirmed that the soak test OTA is identical to ICS leak #2.
jboxer said:
No, they wanted people like that to make sure it worked. Just had to do an FDR and then was good to go. Got the OTA and on ICS now.
Click to expand...
Click to collapse
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
You have to be someone that was invited and filled out a survey about six weeks ago. If you are you need to go to the Motorola Private forum. Go see how others are requesting it (not allowed to really talk about it). FDR means Factory Data Reset and it is an option in Privacy in Settings. It erases all your user settings, app data and you are back to square one like when the phone came out of the box. For many people it was required to get what they wanted.
If you were not invited don't worry. Usually the official rollout of the OTA will come within a week of a soak test if no problems are found. It is the same as leak # 2 so just look on this forum and you can install that manually. The release is solid so I see no reason the OTA won't be going live to all AT&T Atrix 2 devices very soon.
nelsonalfo said:
Sorrry but what mean FDR? because I'm in that situation: Im not in US and I have the phone unlocked, and I'm using it with other operator... Is just ended the soak test?... because the phone say me "Your phone is updated, Is not required a update in this moment" (Translated from Spanish) when I look in Settings -> About the phone -> Update, and I'm have the system version 55.13.25.MB865.ATT.en.US.
Click to expand...
Click to collapse
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
alteredlikeness said:
I think he means Factory Data Reset.. found in settings>backup & reset (?) forgot where it was on GB, but it's in the settings.
Edit: Lol.. jboxer - I've been too slow a lot recently
Click to expand...
Click to collapse
I hated doing it but it was necessary for some reason. Before it my phone was invisible to the update servers. After it was and I got a push notification to begin the download. Loving ICS.
In Firmware Finder is new ROM with build number 389. Unfortunately, no flashable
Hopefully that means that they will release an update soon
Please stop creating new threads for every non flashable update.
I noticed it too...hope they'll make some of it flashable someday... a lot of updates and i'm stuck on B380 lol.
P.s i know that B381 is avaible and flashable but i don't know how to do it. First time with Huawei/Honor device xD
morpheus302 said:
Please stop creating new threads for every non flashable update.
Click to expand...
Click to collapse
OK, I acknowledge. Good note.
Giuskiller said:
I noticed it too...hope they'll make some of it flashable someday... a lot of updates and i'm stuck on B380 lol.
P.s i know that B381 is avaible and flashable but i don't know how to do it. First time with Huawei/Honor device xD
Click to expand...
Click to collapse
Download Firmware FRD-L09C432B381 from here:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v83537/f1/full/changelog.xml
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v83537/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...3537/f1/full/hw/eu/update_data_full_hw_eu.zip
Update process:
1. Unzip [extract] the update.zip to the SD card into the dload folder (if folder is not present, create it yourself)
2. In the phone app, enter the combination *#*#2846579#*#*, then select "Software Upgrade" and the update from SD start
3. Delete the data in the dload folder
4. Repeat point 1-3 with the update_data_full_hw_eu.zip
5. WipeCache (personal recommendation)
zephyrteam said:
Download Firmware FRD-L09C432B381 from here:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v83537/f1/full/changelog.xml
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v83537/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...3537/f1/full/hw/eu/update_data_full_hw_eu.zip
Update process:
1. Unzip [extract] the update.zip to the SD card into the dload folder (if folder is not present, create it yourself)
2. In the phone app, enter the combination *#*#2846579#*#*, then select "Software Upgrade" and the update from SD start
3. Delete the data in the dload folder
4. Repeat point 1-3 with the update_data_full_hw_eu.zip
5. WipeCache (personal recommendation)
Click to expand...
Click to collapse
Thank you very much, before trying i wish to ask you something. I'm rooted so, this will erase the root i think? And this is like clean install or not? Thank you for your patience
Giuskiller said:
Thank you very much, before trying i wish to ask you something. I'm rooted so, this will erase the root i think? And this is like clean install or not? Thank you for your patience
Click to expand...
Click to collapse
I'm not 100% sure but I believe you need stock boot and recovery + unrooted.
+1
horizophon said:
I'm not 100% sure but I believe you need stock boot and recovery + unrooted.
Click to expand...
Click to collapse
And if you're running TWRP 3.1 just flash the zips from there. First the update.zip, then the hw_eu one, and then flash supersu for root. https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
That's how i upgraded from B380 and it works perfectly.
horizophon said:
I'm not 100% sure but I believe you need stock boot and recovery + unrooted.
Click to expand...
Click to collapse
This method don't require twrp or root, this is the same process of the original ota upgrade application, but in manual mode.
Disregard this comment, posted to wrong thread.
hi
Can someone explain me, why is there this kind of update published, non flashable one? internal testing purpose?
Is there a way to update my phone to b389, b388 or other, more than b381, with or without root, even if I have to factory reset my phone, reinstall stock recovery?
You just have to try reading. This topic here and more ...
Hi guys, i've update correctly with twrp to B381 (forgot to flash supersu so...no root. Lol) but i have a problem. On B360 in "Smart assistence" I had the function "Smart Key" to choose ehat to do when the fingerprint key was pressed. Now, after this update i have no more this function. It doesn't show up, even if i try to search it. It has been disabled or should i try to factory reset?
Giuskiller said:
Hi guys, i've update correctly with twrp to B381 (forgot to flash supersu so...no root. Lol) but i have a problem. On B360 in "Smart assistence" I had the function "Smart Key" to choose ehat to do when the fingerprint key was pressed. Now, after this update i have no more this function. It doesn't show up, even if i try to search it. It has been disabled or should i try to factory reset?
Click to expand...
Click to collapse
It's in b381, In settings (use the settings search bar)
pix106 said:
It's in b381, In settings (use the settings search bar)
Click to expand...
Click to collapse
No, isn't here. And it isn't in the proper section. Maybe something went wrong. I tried to search, tried every section...
Giuskiller said:
No, isn't here. And it isn't in the proper section. Maybe something went wrong. I tried to search, tried every section...
Click to expand...
Click to collapse
Well I still have it in settings under Smart Assistance.
sltwp said:
Well I still have it in settings under Smart Assistance.
Click to expand...
Click to collapse
My internet connection sucks, i cannot upload pics, but in my smart assistance the voice "Smart Key" is completely missing. I'm unlucky as always uff..
Giuskiller said:
My internet connection sucks, i cannot upload pics, but in my smart assistance the voice "Smart Key" is completely missing. I'm unlucky as always uff..
Click to expand...
Click to collapse
Well if that's the case I would try re-flashing the 381 FW.
Hey everyone, I managed to download the OTA update bin file from FOTA server for the S8 Unlocked (US Version). If anyone is interested in testing and post the update I will leave the link to the OTA bin file. I am actually working on it as well. I am assuming it should be flashable as long as you have latest Nougat 7.0 for the unlocked S8 or if you have installed Unlocked firmware in your Carrier branded Galaxy S8. I will be doing some test as well but I need some rest before I start working on it again. Will keep you all posted and hope some of you guys would like to do some test with it. I am pretty sure we will figure out how to flash it.
As far as I know from last year you could flash update.zip file which was extracted from the Verizon S7 Edge. Since its unlocked firmware/OTA file I would assume it will be doable.
Normally you will have to keep the file in your sdCard and go to recovery mode and apply update from SD card but we will definitely have to do some testing if that doesn't work out.
Link for the OTA update bin file: https://mega.nz/#F!k6IjlJoC!VJJ3gyVaF8ofphE1fZvD8A
EDIT: found a way to download whole firmware will post sometime after midnight once I get off from work.
we cant flash .bin files. Doesnt work. We already tried.
thank you! I would love to know how to flash this if possible?
badboy47 said:
thank you! I would love to know how to flash this if possible?
Click to expand...
Click to collapse
1 possible way might be to extract the content of bin with 7zip. then compress it with 7zip as a zip file. name it the same name. put on sdcard and reboot to recovery. then apply update from sdcard and prey to what ever god you like that it works.
trying to help.
MrSteelX said:
1 possible way might be to extract the content of bin with 7zip. then compress it with 7zip as a zip file. name it the same name. put on sdcard and reboot to recovery. then apply update from sdcard and prey to what ever god you like that it works.
trying to help.
Click to expand...
Click to collapse
Nope is not working there are two errors 1st is e.footer is wrong and 2nd is signature verification failed
If someone has a Snapdragon S8 with bootloader unlocked and TWRP, maybe you can sideload it by disabling signature verification?
When flashing updates via stock recovery create a folder call FOTA in SD card and place file there rename it update.zip just make sure you don't end up with update.zip.zip
tlopez1973 said:
When flashing updates via stock recovery create a folder call FOTA in SD card and place file there rename it update.zip just make sure you don't end up with update.zip.zip
Click to expand...
Click to collapse
No, an error is displayed. Nothing is set.
55andrey55 said:
No, an error is displayed. Nothing is set.
Click to expand...
Click to collapse
what's the error you got?
MishaalRahman said:
If someone has a Snapdragon S8 with bootloader unlocked and TWRP, maybe you can sideload it by disabling signature verification?
Click to expand...
Click to collapse
Only snapdragons that have bootloader unlock is the Chinese edition and loading that would probably brick them or best casensrio perma lock their bootloader
Cameron581 said:
Only snapdragons that have bootloader unlock is the Chinese edition and loading that would probably brick them or best casensrio perma lock their bootloader
Click to expand...
Click to collapse
It wouldn't do either of those. It would just fail.
suyash1629 said:
what's the error you got?
Click to expand...
Click to collapse
Just went live in the US man through the Samsung plus app and I got in. Only 10k spots
Stevieboy02008 said:
Just went live in the US man through the Samsung plus app and I got in. Only 10k spots
Click to expand...
Click to collapse
Yup I saw it just went live. I reverted back to Nougat and was trying to get the OTA update.zip file. And noticed that it just went live. For some reason it did not detect that I was already registered and asked me to registered again. I wonder if everyone who did it by bypassing server has to register again to claim their actual spot for later updates.
suyash1629 said:
Yup I saw it just went live. I reverted back to Nougat and was trying to get the OTA update.zip file. And noticed that it just went live. For some reason it did not detect that I was already registered and asked me to registered again. I wonder if everyone who did it by bypassing server has to register again to claim their actual spot for later updates.
Click to expand...
Click to collapse
Don't know and don't care. It's downloading officially now brother and I'm a happy camper lol once it download I will do factory reset and have it fresh
Does anyone know if we can use SamPWND root method but without clearing cache? I am assuming I can do that by not flashing CSC which contains the cache partition.
I am trying to grab update.zip from cache partition.
Turns out my assumption of update.zip file being stored in /cache were wrong its actually stored in /data/fota folder. I guess we are out of luck here. I was thinking what is that converts .bin file to .zip file instantly after downloading onto Galaxy S8. I don't see any other way beside renaming and adding signature (though it already has the signature from Samsung.
suyash1629 said:
Turns out my assumption of update.zip file being stored in /cache were wrong its actually stored in /data/fota folder. I guess we are out of luck here. I was thinking what is that converts .bin file to .zip file instantly after downloading onto Galaxy S8. I don't see any other way beside renaming and adding signature (though it already has the signature from Samsung.
Click to expand...
Click to collapse
Well I have a question for you brother.
I just officially download and installed it. But wanted to do a fresh start basically a factory reset and download everything from scratch. If I do the factory reset would it kick me out of beta and take me back to 7.0 or just take me back to 7.0 or will start with 8.0?
Stevieboy02008 said:
Well I have a question for you brother.
I just officially download and installed it. But wanted to do a fresh start basically a factory reset and download everything from scratch. If I do the factory reset would it kick me out of beta and take me back to 7.0 or just take me back to 7.0 or will start with 8.0?
Click to expand...
Click to collapse
factory reset will stay on 8.0
Would it kick me out of the beta program though. That's the most important thing for me ?
---------- Post added at 08:34 PM ---------- Previous post was at 08:03 PM ----------
cam30era said:
factory reset will stay on 8.0
Click to expand...
Click to collapse
Please advice on my earlier question brother.
You guys think FlashFire could flash it?
I reverted to stock after messing up my BLN-L24. The ROM is a bit different than the one that shipped with the phone. Some apps are missing. The play store doesn't seem to detect updates even though they can be updated manually when searched. The phone also wont let me update to the latest version. The os it shipped with could update to the latest security update. The play store also says the phone is uncertified. Why is this ROM different? Is there any way i can force an update?
is model number and everything in about section still the same ?
sreekantt said:
is model number and everything in about section still the same ?
Click to expand...
Click to collapse
Yea. I figured it out. I flashed the updates in the wrong order. So i was missing all of the USA files because they were flashed before the actual ROM
sreekantt said:
is model number and everything in about section still the same ?
Click to expand...
Click to collapse
Nevermind. Its still messed up. I dont understand why im not getting any of the USA features installed. i believe its all stock. BLN-L24C567B342 is the build number. BLN-L24 is the model number.
BakedOnSomeSour said:
Nevermind. Its still messed up. I dont understand why im not getting any of the USA features installed. i believe its all stock. BLN-L24C567B342 is the build number. BLN-L24 is the model number.
Click to expand...
Click to collapse
Don't u have any old TWRP backup which consists of OEM info, vendor, product, boot ???
If not, i think you have to use Huawei update extractor on US firmware
Twrp backup would have made the process easy and reliable
There is something very screwed up with the OTA updates for this model phone right now. Consider yourself lucky that your phone still works, I'm dealing with a BLN-L24 that is more than likely unrecoverable all due to some wierd firmware that the official updater installed on the phone on Christmas Eve. Its like the servers are sending bad firmware that isn't for this model but the phone accepts it since it's OTA.
If you haven't read it yet please check out my thread and tell me if you are experiencing anything similar since your OTA. Check out the 3rd post too.
https://forum.xda-developers.com/honor-6x/help/bln-l24-stuck-device-booting-rollback-t3725319
I forgot to mention in my post that overall the phone ran extremely sluggish for a fresh update even though I have no idea what firmware was on the phone. All I know is it was completely foreign to me in all aspects....it was just very wierd overall and in pretty sure you know exactly what I mean since you said it was different.
As for uncertified in play store, try clearing app data for play store and see if it changes to certified.
sreekantt said:
Don't u have any old TWRP backup which consists of OEM info, vendor, product, boot ???
If not, i think you have to use Huawei update extractor on US firmware
Twrp backup would have made the process easy and reliable
Click to expand...
Click to collapse
Unfortunately i don't. I will try to flash the files from the update file with the extractor.
BakedOnSomeSour said:
Unfortunately i don't. I will try to flash the files from the update file with the extractor.
Click to expand...
Click to collapse
Yeah...try
Verify if u downloaded from the appropriate firmware
http://pro-teammt.ru/firmware-database/?firmware_model=BLN-L24C567&firmware_page=0
sreekantt said:
Yeah...try
Verify if u downloaded from the appropriate firmware
http://pro-teammt.ru/firmware-database/?firmware_model=BLN-L24C567&firmware_page=0
Click to expand...
Click to collapse
I flashed the vendor, boot, recovery, and system images with fastboot and then installed the update through erecovery. First i flashed update.zip. Then i flashed update_data_full_BLN-L24_hw_usa. Im still missing all of the USA features. I know all of the apks are in the update_data_full_BLN-L24_hw_usa folder but they arent being put on the system. Is there something i could be missing? Also the install time for update_data_full_BLN-L24_hw_usa is rather short for its size. Is it just being skipped?
BakedOnSomeSour said:
I flashed the vendor, boot, recovery, and system images with fastboot and then installed the update through erecovery. First i flashed update.zip. Then i flashed update_data_full_BLN-L24_hw_usa. Im still missing all of the USA features. I know all of the apks are in the update_data_full_BLN-L24_hw_usa folder but they arent being put on the system. Is there something i could be missing? Also the install time for update_data_full_BLN-L24_hw_usa is rather short for its size. Is it just being skipped?
Click to expand...
Click to collapse
Just to confirm we r on the same lines
U just mentioned that u flashed update.zip
Did u mean 'install it via dload method' .....If installing via dload method...u need to extract update.zip and place the contents in dload folder of sd card.
If u r doing the same....what are the exact apps and features which are missing ?
sreekantt said:
Just to confirm we r on the same lines
U just mentioned that u flashed update.zip
Did u mean 'install it via dload method' .....If installing via dload method...u need to extract update.zip and place the contents in dload folder of sd card.
If u r doing the same....what are the exact apps and features which are missing ?
Click to expand...
Click to collapse
Yes by flash i mean using the dload method. I extracted the content of the update.zip and put it in the dload folder on the sd card. After that i put the files from update_data_full_BLN-L24_hw_usa folder into dload and run the update. When the phone boots i am taken to a rather boring stock setup without any bloat apps. Its missing default wallpapers and themes. The play store fails to detect that the preinstalled apps need updates. Its almost like a completely different phone. A completely different broken phone. The apps below should be on the phone
UPDATe: Got an OTA and everything is back to normal. Thanks for the help
BakedOnSomeSour said:
Yes by flash i mean using the dload method. I extracted the content of the update.zip and put it in the dload folder on the sd card. After that i put the files from update_data_full_BLN-L24_hw_usa folder into dload and run the update. When the phone boots i am taken to a rather boring stock setup without any bloat apps. Its missing default wallpapers and themes. The play store fails to detect that the preinstalled apps need updates. Its almost like a completely different phone. A completely different broken phone. The apps below should be on the phone
UPDATe: Got an OTA and everything is back to normal. Thanks for the help
Click to expand...
Click to collapse
:highfive: nice
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Superorb said:
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Click to expand...
Click to collapse
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
BakedOnSomeSour said:
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
Click to expand...
Click to collapse
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Superorb said:
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
BakedOnSomeSour said:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
Click to expand...
Click to collapse
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Superorb said:
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Click to expand...
Click to collapse
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
BakedOnSomeSour said:
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
Click to expand...
Click to collapse
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Superorb said:
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Click to expand...
Click to collapse
Same. if you need any additional help with the process just let me know.
BakedOnSomeSour said:
Same. if you need any additional help with the process just let me know.
Click to expand...
Click to collapse
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Superorb said:
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Click to expand...
Click to collapse
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
BakedOnSomeSour said:
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
Click to expand...
Click to collapse
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Superorb said:
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Click to expand...
Click to collapse
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
BakedOnSomeSour said:
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
Click to expand...
Click to collapse
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Superorb said:
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Click to expand...
Click to collapse
Ok now extract the files from the update.zip folder. Then take the UPDATE.app from the extracted files and open it with update extractor: https://forum.xda-developers.com/showthread.php?t=2433454
After that your ready to follow the steps on the other guide.
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Superorb said:
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Click to expand...
Click to collapse
Edit: Before trying below steps. Just put the files from "BLN-L24_hw_usa"(b360) into dload folder and flash with dload. It might update the version.img without the needs for the steps below. if that brings the build number back to b360 use the hisui(PC) application to connect to the phone and update
Ok i forgot to mention something. The reason you dont have a update option is because you are on b360 which never had a button. Your build number on your phone will say b366 but thats incorrect. You cant receive an ota automatically because the phone thinks its already on the latest version. You need to take the UPDATE.APP from the "BLN-L24_hw_usa" (b360) folder and extract the VERSION.IMG file. It needs to be flashed with TWRP because fastboot wont work for some reason. That file will fix the build number and change it back to b360 so you can receive the OTA which will also restore the missing apps and features. That means you have to unlock the bootloader. Flash twrp. Flash the vendor.img with twrp and then do the dload method.
You have all the files and have done it already so this time will be easier. Ive done this way too many times with this phone. Sorry i forgot the mention the one step
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Superorb said:
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Click to expand...
Click to collapse
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
BakedOnSomeSour said:
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
Click to expand...
Click to collapse
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Superorb said:
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Click to expand...
Click to collapse
Its not difficult. In order to connect to hisuite you need to enable developer settings and allow usb debugging or type hisuite in the settings search bar and click "allow HiSuite to use HDB". I got this phone for christmas and i already know a ton about it. It may seem complicated now but its really nothing.