Hi,
It seems I was over zelaous in trying the updated ROMs that were posted on Huawei and NeedRom (didn't look at the file names that stated they Chinese versions).
Looking to see if anyone has a copy or a backup or their original ENGlish or international ROM that I can use to recover mine so I get GAPPS back, being able to define which slot is the 4G slot rather that being told the top one, etc.
I will be eternally grateful if someone can assist.
MT7 firmware
sketchykingy said:
Hi,
It seems I was over zelaous in trying the updated ROMs that were posted on Huawei and NeedRom (didn't look at the file names that stated they Chinese versions).
Looking to see if anyone has a copy or a backup or their original ENGlish or international ROM that I can use to recover mine so I get GAPPS back, being able to define which slot is the 4G slot rather that being told the top one, etc.
I will be eternally grateful if someone can assist.
Click to expand...
Click to collapse
The first link is for the L09 variant. The other, I'm not sure. Saw the TL10 Southeast Asia firmware a couple of days ago over at the official Huawei Philippines website, but it's no longer there now.
http://consumer.huawei.com/it/support/downloads/detail/index.htm?id=31149
http://consumer.huawei.com/pl/support/downloads/detail/index.htm?id=32122
monchinglopez said:
The first link is for the L09 variant. The other, I'm not sure. Saw the TL10 Southeast Asia firmware a couple of days ago over at the official Huawei Philippines website, but it's no longer there now.
Thanks for the links, I have tried no success, they all fail in the upgrade/install.
I went through all the locations/countries on the website looking for the TL10 version, I was unable to find one, even the Generic one that was listed didn't install and came out as a fail (assuming it is meant for TL09).
Oh well will just have to wait for an upload by someone or wait for Huawei to post the ENG ROM update.
Click to expand...
Click to collapse
sketchykingy said:
monchinglopez said:
The first link is for the L09 variant. The other, I'm not sure. Saw the TL10 Southeast Asia firmware a couple of days ago over at the official Huawei Philippines website, but it's no longer there now.
Thanks for the links, I have tried no success, they all fail in the upgrade/install.
I went through all the locations/countries on the website looking for the TL10 version, I was unable to find one, even the Generic one that was listed didn't install and came out as a fail (assuming it is meant for TL09).
Oh well will just have to wait for an upload by someone or wait for Huawei to post the ENG ROM update.
Click to expand...
Click to collapse
Here it is: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Click to expand...
Click to collapse
monchinglopez said:
sketchykingy said:
Here it is: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Click to expand...
Click to collapse
LEGEND!!!
Click to expand...
Click to collapse
Do you've already flashed it? Version 119 looks a little old, but the upload date seems to be 29th nov. I've patched my cust partition with the files from this version. SIM config, etc. is all there now and Vodafone 4G is selectable now, too. And it shows vodafone.de now instead of vodafone.de 3G. But it looks like it's still not activating 4G. Modem file size looks a little different, well i would try to flash modem, but i'm not sure to which partition, there are several partitions with modem in the name and the space used on these partitions isn't matching the size of the modem.img in the update.app file. Anybody flashed this is living in a 800Mhz lte area? Is it working? Any ideas about the modem partition?
pappschlumpf said:
Do you've already flashed it? Version 119 looks a little old, but the upload date seems to be 29th nov. I've patched my cust partition with the files from this version. SIM config, etc. is all there now and Vodafone 4G is selectable now, too. And it shows vodafone.de now instead of vodafone.de 3G. But it looks like it's still not activating 4G. Modem file size looks a little different, well i would try to flash modem, but i'm not sure to which partition, there are several partitions with modem in the name and the space used on these partitions isn't matching the size of the modem.img in the update.app file. Anybody flashed this is living in a 800Mhz lte area? Is it working? Any ideas about the modem partition?
Click to expand...
Click to collapse
Hi,
Not sure to tell you the truth, mine is stuck on the last 2-3% on the upgrade, regardless of if I do it via the APP, Bootrom, SD or internal card, or if it is plugged into power or PC. Never seems to complete, I have left it for an hour at a time. The Chinese ROMs completed in under 5 minutes so I am not sure what the issue is, I also tried a different SD card, formatted, cleared cache, reset to factory everything My Telstra Sims have the 800hz range but cant confirm at the moment.
Any guidance on the steps you took would be handy.
I've only modified cust partition with the files from the b119 update.app. I've tried to flash it and ended up like you, flashing process immediately stops. For sure this update checks build.prop and stops there. I'll have a look if i could find and mod the update script.
I have the latest version 120sp07 china
to me it does not "return" to that release .. dload fails
For sure because of checking rom version in build.prob in your system partition. You could try to replace it with the one in the update.app before flashing. Should i upload it for you?
I think so too, I can change the build prop ..
according to you which lines need to be changed?
I noticed that the model has changed in JAZZ
currently are with version 120sp07
among other things, now is the output 121sp02
I think the Chinese versions also complicate life here in europe, what do you think?
on the German site they say that you can not load the various firmware
Please and the steps taken.
sketchykingy said:
Please and the steps taken.
Click to expand...
Click to collapse
I received the phone from china with a rom in English already with root and cwm
I had the updates are ready to install rieusciva but not because there was cwm
I wanted to upgrade to a rom Chinese 120sp07 in a forced dload
I had to first remove the cwm recovery and put the original taken by unzipping the SP07
I installed the 120sp07 function forced dload
iI saw that after the phone has changed names in "jazz"
now I can not install the rom General English with dload why not complete the installation
I would go back to the general version eng
andytom69 said:
I received the phone from china with a rom in English already with root and cwm
I had the updates are ready to install rieusciva but not because there was cwm
I wanted to upgrade to a rom Chinese 120sp07 in a forced dload
I had to first remove the cwm recovery and put the original taken by unzipping the SP07
I installed the 120sp07 function forced dload
iI saw that after the phone has changed names in "jazz"
now I can not install the rom General English with dload why not complete the installation
I would go back to the general version eng
Click to expand...
Click to collapse
Andy,
As pappschlumpf said it is a difference in the build.prop file.
He is going to post up the one that he modified to work on his mobile and hopefully the steps taken to replace the file as well.
Then we can use the normal English version.
sketchykingy said:
Andy,
As pappschlumpf said it is a difference in the build.prop file.
He is going to post up the one that he modified to work on his mobile and hopefully the steps taken to replace the file as well.
Then we can use the normal English version.
Click to expand...
Click to collapse
Here's the build.prop as attachement. Extract and replace the one in /system with it. Permissions have to be set to rwrr. If it's still not working, other files are checked by the updater, too.
pappschlumpf said:
Here's the build.prop as attachement. Extract and replace the one in /system with it. Permissions have to be set to rwrr. If it's still not working, other files are checked by the updater, too.
Click to expand...
Click to collapse
@pappschlumpf did you have to root first, or can we get around it by doing something funky?
or do i just rebuild the UPDATE.APP with this new build.prop file?
You need root to replace files in the /system partition.
That's the build.prop from the B119 ROM. If you replace your B121/120 build.prop with it and start flash it could work if build.prop is the only file that is checked before starting flash procedure. I can not say that surely because of not finding an update script in huawei's update.app file.
So let's recap
discharge of the buildprop 119sp3 general attached
I replace this file on my 120sp07 I copy it over with write permissions
after restart or I can immediately update the dload 19sp03 eng general?
andytom69 said:
So let's recap
discharge of the buildprop 119sp3 general attached
I replace this file on my 120sp07 I copy it over with write permissions
after restart or I can immediately update the dload 19sp03 eng general?
Click to expand...
Click to collapse
Yes, i hope so. After replacing the file don't forget to set permissions for build.prop to rw-r-r again! And save a copy of your B120 build.prop to your external SD.
Related
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.
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
Hello all,
Does anyone have a vendor.img file for US variant BLN-L24? I am attempting to get back to stock, and I have the boot, recovery, and system files, but my update.app seems to not have vendor.img for some reason. Any help on this is much appreciated.
Hi, a reason because your update.app wouldn't have the vendor.img could be that you're trying to extract the vendor from the wrong update package; which one you used? The vendor is present only in the biggest update.zip file around 1,64GB; are you sure you didn't tried to extract it from one of the other two packages (update data full public/update data hw region code)? The vendor is present only in the package labeled with FULL, and not in normals OTA that you receive through system update. Write me up here your build number for extended, and I'll provide you a download link for a package that will surely contain the vendor.img for BLN-L24
Thanks for the reply. I actually downloaded a new update.app last night that contained the necessary vendor.img.
I now have the issue that when I attempt to go back to stock via dload, my install will get to 5%, fail with a red exclamation point in the middle of the screen, and then only give an option to reboot.
From reading the rolling back to stock thread, it appears my version of update.app just may not be working correctly for dload. I have no clue what build number I was on previously, but it should be the latest update that was available as of a week ago. If you can direct me to a valid working update.app for this variant (BLN-L24), that should get me back to stock. Thanks again for any help.
You should try dload with the latest build available here for BLN-L24Cxxx that has "PV" at the end of the package name http://pro-teammt.ru/firmware-database/ (can't know code region so except if there is only one variant, like C583 for example, be careful on which package you download) i suppose that you could be on this USA variant, but i can't ensure it http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v103272/f1/full/update.zip
RedSkull23 said:
You should try dload with the latest build available here for BLN-L24Cxxx that has "PV" at the end of the package name http://pro-teammt.ru/firmware-database/ (can't know code region so except if there is only one variant, like C583 for example, be careful on which package you download) i suppose that you could be on this USA variant, but i can't ensure it http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v103272/f1/full/update.zip
Click to expand...
Click to collapse
Thanks for the link. I will double check when I get home later and try to use dload again.
TurtlePwr82 said:
Thanks for the link. I will double check when I get home later and try to use dload again.
Click to expand...
Click to collapse
You're welcome dude. Let me know if you can solve that out.
RedSkull23 said:
You're welcome dude. Let me know if you can solve that out.
Click to expand...
Click to collapse
So attempting to use the two latest updates available on that site for a basis, I did attempt to use the update.app from each one to attempt install, and get an error message each time when installing package (fail at 5%). At this point, I'm not sure where exactly the fault lies. Just wanted to give you an update.
TurtlePwr82 said:
So attempting to use the two latest updates available on that site for a basis, I did attempt to use the update.app from each one to attempt install, and get an error message each time when installing package (fail at 5%). At this point, I'm not sure where exactly the fault lies. Just wanted to give you an update.
Click to expand...
Click to collapse
I'm sorry that you still are in trouble. I never had luck using dload too, i tried 3 times but I remember that time ago, the thing about using the package with PV at the end was still unknown, so maybe that was the fault. I'll look for users who owns a BLN-L24 to call in cause, in way to ask them to provide a vendor.img for your build and solve this.
RedSkull23 said:
I'm sorry that you still are in trouble. I never had luck using dload too, i tried 3 times but I remember that time ago, the thing about using the package with PV at the end was still unknown, so maybe that was the fault. I'll look for users who owns a BLN-L24 to call in cause, in way to ask them to provide a vendor.img for your build and solve this.
Click to expand...
Click to collapse
Thanks for the help. I've pretty much gone to my backup phone at this point, though I am still trying to fix this one. I thought I had a breakthrough in getting back to stock last night, but upon boot the EliteRom without sound was still flashed. If I could get sound on the EliteRom when I flash it I could live with the phone. I did see that was a reported problem apparently with some of the rooms (loss of sound and video playback).
It's almost as if maybe the custom kernel can no longer be wiped from the phone once it is flashed, and I think that may be where my issue is stemming from, as I have attempted all update.apps from the most recent through to 7/31, all of which fail at 5% through dload, though flashing in fastboot for everything else goes smoothly. I will continue to try to work on it, or just sell the phone. Thanks again for all of your help, it is much appreciated.
Hello ,
Maybe someone will be interested
I assembled firmware based on Miui8 from Honor 7
Download https://drive.google.com/open?id=1RN3Dht7GapLq0TdeBuUSGSEX0mlHMc7R
Installation
1 Android 6 must be installed on the phone
2 boot into twrp https://drive.google.com/open?id=1EPnvT6cJFZXEeUcZT1t72FO5TAAJWAsh
3 Install rom
4 After installation, make a wipe cache and dalvik cache
5 boot into the system
The download will be long.
Wait for the phone to turn on.
I installed on GEM-703 C223B228
Files for models GEM-701 and GEM-702 are added to the CUST section.
Try it, but do not forget to backup
I am not a developer of this firmware!
I just tried to install it on my phone and slightly improved it.
The original took here https://forum.xda-developers.com/honor-7/development/miui-honor-7-wbt-t3656413
gaguga said:
Hello ,
Maybe someone will be interested
I assembled firmware based on Miui from Honor 7
Click to expand...
Click to collapse
Any link to download?
Any instructions to install?
Multi-languages?
Known bugs?
Thanks for opening this thread! Do not hesitate to edit post #1 above
Communication is working. Camera works. Wifi works. Gps works.
This looks great，Thank u!
gaguga said:
Hello ,
Maybe someone will be interested
I assembled firmware based on Miui8 from Honor 7
Download https://drive.google.com/open?id=1RN3Dht7GapLq0TdeBuUSGSEX0mlHMc7R
Installation
1 Android 6 must be installed on the phone
2 boot into twrp https://drive.google.com/open?id=1EPnvT6cJFZXEeUcZT1t72FO5TAAJWAsh
3 Install rom
4 After installation, make a wipe cache and dalvik cache
5 boot into the system
The download will be long.
Wait for the phone to turn on.
I installed on GEM-703 C223B228
Files for models GEM-701 and GEM-702 are added to the CUST section.
Try it, but do not forget to backup
I am not a developer of this firmware!
I just tried to install it on my phone and slightly improved it.
The original took here https://forum.xda-developers.com/honor-7/development/miui-honor-7-wbt-t3656413
Click to expand...
Click to collapse
What program are you using to repack the img files?
ajsmsg78 said:
What program are you using to repack the img files?
Click to expand...
Click to collapse
I did not quite understand your question.
I install the firmware on the phone.
Then I bring everything to work on the phone,
Then when everything works for me - then I make a backup in the TWRP section of the system.img
I collect archive for twrp
Then I install the archive and check that everything works.
gaguga said:
I did not quite understand your question.
I install the firmware on the phone.
Then I bring everything to work on the phone,
Then when everything works for me - then I make a backup in the TWRP section of the ij system.img
I collect archive for twrp
Then I install the archive and check that everything works.
Click to expand...
Click to collapse
OK, I understand now, thanks.
I flashed the system-image on a clean device, it worked but it is full of chinese bloatware. there are two camera-apps and two phone apps. Went back to the original B207.
my device is 702L, I flash this Mi-Rom from B206 first, but not successful (keep stay at TWRP page). then, I change to flesh to China Rom B212 first, after then, to flesh to this Mi-Rom, and I got this Mi-rom working on my device.. also, as there are two camera-apps and two phone apps. I think this Mi-rom is not yet "complete", so, I flesh back to the original B206.
Tried it on my 702. Loong start but all works.
Unfortunately there are no some features like auto power on/off so i have to go back to kangvip4 by restoring backup.
请问这个rom还有更新么？之前的链接挂了，还有我刷入这个rom后一直卡在开机引导这里，每次到显示登录小米账户这就闪退回前一个页面，无论如何也进不了系统，请问这是怎么回事？如何解决
Lakr_190O said:
请问这个rom还有更新么？之前的链接挂了，还有我刷入这个rom后一直卡在开机引导这里，每次到显示登录小米账户这就闪退回前一个页面，无论如何也进不了系统，请问这是怎么回事？如何解决
Click to expand...
Click to collapse
please write in english in xda forums. thx
you should contact gaguga by MP to know about any update. I'll have a look at his russian forum....
you need a xiaomi account to boot MIUI roms ?
gaguga said:
Hello ,
Maybe someone will be interested
I assembled firmware based on Miui8 from Honor 7
Download https://drive.google.com/open?id=1RN3Dht7GapLq0TdeBuUSGSEX0mlHMc7R
Click to expand...
Click to collapse
Hey @gaguga , link is dead. Can you provide the file again please, I'll put it and leave it online if you want.
thx.
If someone else still has it, let me know !
Hi every one. I managed to contact @gaguga on VK.com . He has lost the file of this MIUI rom for X2, but gave me the exact MUI rom for HONOR 7 he customised to boot it on X2 (note that other versions of this MIUI are available on original thread fot Honor 7, like this one)
I wonder if @ajsmsg78 would be kind enough to have a look to recreate the work of gaguga on this MIUI for X2, as a couple of users asked me the file. I can give to ajsmsg78 the file provided by gaguga. And also his direct contact as he doesn't read his xda messages.
I'd like myself to install it in, fact !
let me know!
Send me a link to the file and I'll download it and see what I can do.
ajsmsg78 said:
Send me a link to the file and I'll download it and see what I can do.
Click to expand...
Click to collapse
so nice from you, Here is the file that gaguga used to build the firmware for X2:
miui_Honor7_7.2.28_wvijheq2h4_6.0.zip
drive.google.com
Djiban said:
so nice from you, Here is the file that gaguga used to build the firmware for X2:
miui_Honor7_7.2.28_wvijheq2h4_6.0.zip
drive.google.com
Click to expand...
Click to collapse
Take the file out of your trash and I'll download it.
ajsmsg78 said:
Take the file out of your trash and I'll download it.
Click to expand...
Click to collapse
That is gaguga drive, I'll share you the download I've made
so here is the Honor 7 ROM that Gaguga used a a basis:
miui_Honor7_7.2.28_wvijheq2h4_6.0.zip
Compressed (zipped) Folder
1drv.ms