Hi, I just received my axon 7 today, everything works fine and I notice that it's been installing with such a chinese custom rom that has google enabled and international languages including my native, but this cant be updated through OTA.
I have downloaded the firmware from official site, B17 build version but through SD card installing the firmware will always get failed because of couldnt verify, file corrupt, installation aborted and it says the firmware doent match with my phone.
I've done factory reset, clear cache and partition but none of them worked. I want the official rom so I can get the latest update easily.
Related
Dear XDA members, my friend have bricked his phone after trying to update to lollipop 5.1.1 from 5.0.1.
Error message: "Unfortunately, the process com.google.process.location has stopped"
I have wiped cache via recovery,boot into safe mode, and even factory reset wipe data but still getting the same error.
I have searched for ways to flash stock using google/xda and i was instructed to download the stock firmware and flash via adb in recovery.
However in my recovery, there was no option to "Update via ADB".
The only options available are, 1)reboot system now 2)Apply update from internal storage 3)Apply update from external storage 4)Wipe data/factory reset 5)Wipe cache partition 6)Apply update from cache.
Current phone model Asus A500KL, WW variant ( i suppose? got it from recovery version as stated below.)
Recovery version 1.8 KOT49H.WW_Phone-11.4.6.94-20141218
From here, i believe the updated firmware the phone is running on is 11.4.6.94, and thus, i have downloaded 3 version of the stock firmware to flash, UL-ASUS_T00P-WW-12.4.5.58-user, UL-ASUS_T00P-WW-11.4.6.88-user and UL-ASUS_T00P-WW-11.4.6.94-user
I also have the downgrade version from Android L to KK which is WW_A500KL-11.4.6.94-20141218_M3.5.22-ota-user.zip
I am uncertain which version will unbrick the phone and put it into the brand new state. (Also, please tell me if the version i downloaded is correct for the phone)
*All of the versions are downloaded from Asus itself.
I would appreciate if someone can tell me how and which version of the stock rom to be flashed.
*Note that the phone is stuck at the error i have mentioned above, and there is no option to sideload or flash via adb in the recovery. It was running on android 5.0.1 before the update, and the 5.1.1 update caused it to be soft bricked.
Will it be possible if i were to just move the 11.4.6.94 downgrade version into my SD card and choose on "Apply update from External storage?",, likewise for the other older version?
Would it be wise if i were to flash the same version again (not the downgrade version) and see if it works?
Does it sound like a Hardware of software issue?
Any reply will be greatly appreciated!
Have you tried reflashing the firmware?
dgadelha said:
Have you tried reflashing the firmware?
Click to expand...
Click to collapse
didi you try to install the rom from external storage
dgadelha said:
Have you tried reflashing the firmware?
Click to expand...
Click to collapse
Ps: i am the OP friend with the bricked phone
I am unable to use the phone at all
That is my question.
Which version should I flash via adb Fast boot ( I don't have update via adb option in recovery).
Will it work If I transfer the same firmware version to the phone sd And update from there? ( does same version allow update from external storage?)
Menoobone said:
Ps: i am the OP friend with the bricked phone
I am unable to use the phone at all
That is my question.
Which version should I flash via adb Fast boot ( I don't have update via adb option in recovery).
Will it work If I transfer the same firmware version to the phone sd And update from there? ( does same version allow update from external storage?)
Click to expand...
Click to collapse
Try flashing UL-ASUS_T00P-WW-11.4.6.94-user via adb sideload.
dgadelha said:
Try flashing UL-ASUS_T00P-WW-11.4.6.94-user via adb sideload.
Click to expand...
Click to collapse
i mentioned twice in both the first post and the 3rd post that i don't have that option in my recovery. I only have update from cache, update from internal storage, and update from external storage. I would appreciate to know if using the apply update from external storage option would fix the phone as the version number is exactly the same and thus, it would be not installed as it is not "an update". Currently we do not have an sd card with us, and is unable to push the file into the internal memory, so would really appreciate if someone can guide me on whether getting an sd card and moving the same firmware version into the sd to apply update from external storage will works.
khoojunxiang said:
Dear XDA members, my friend have bricked his phone after trying to update to lollipop 5.1.1 from 5.0.1.
Error message: "Unfortunately, the process com.google.process.location has stopped"
I have wiped cache via recovery,boot into safe mode, and even factory reset wipe data but still getting the same error.
I have searched for ways to flash stock using google/xda and i was instructed to download the stock firmware and flash via adb in recovery.
However in my recovery, there was no option to "Update via ADB".
The only options available are, 1)reboot system now 2)Apply update from internal storage 3)Apply update from external storage 4)Wipe data/factory reset 5)Wipe cache partition 6)Apply update from cache.
Current phone model Asus A500KL, WW variant ( i suppose? got it from recovery version as stated below.)
Recovery version 1.8 KOT49H.WW_Phone-11.4.6.94-20141218
From here, i believe the updated firmware the phone is running on is 11.4.6.94, and thus, i have downloaded 3 version of the stock firmware to flash, UL-ASUS_T00P-WW-12.4.5.58-user, UL-ASUS_T00P-WW-11.4.6.88-user and UL-ASUS_T00P-WW-11.4.6.94-user
I also have the downgrade version from Android L to KK which is WW_A500KL-11.4.6.94-20141218_M3.5.22-ota-user.zip
I am uncertain which version will unbrick the phone and put it into the brand new state. (Also, please tell me if the version i downloaded is correct for the phone)
*All of the versions are downloaded from Asus itself.
I would appreciate if someone can tell me how and which version of the stock rom to be flashed.
*Note that the phone is stuck at the error i have mentioned above, and there is no option to sideload or flash via adb in the recovery. It was running on android 5.0.1 before the update, and the 5.1.1 update caused it to be soft bricked.
Will it be possible if i were to just move the 11.4.6.94 downgrade version into my SD card and choose on "Apply update from External storage?",, likewise for the other older version?
Would it be wise if i were to flash the same version again (not the downgrade version) and see if it works?
Does it sound like a Hardware of software issue?
Any reply will be greatly appreciated!
Click to expand...
Click to collapse
i also have the same issue, i tried sd update but it fails, no sideload option in recovery and bootloader locked
did U found any solution??
I bought an axon 7 a2017 the chinese version from aliexpress, and the phone itself is great but the seller did something with the phone and I am not able to download updates for it, it says it's up to date but it's running Android 6.0 on mifavor 4.0 b07. I've looked at so many threads and tried to flash it, always says the installation is aborted. OEM is enabled, I think the problem is with the zip. Can someone please post a link for zip so I can update to nougat.
sellers from ali put G rom on chinize phone you need some how flash chinize recovery from bootloader via cmd if its unlocked then flash full B13 6.0 from recovery
In settings>about see if it says A2017 B07 rom. If it does and it's MM then you can just download the B13 (chinese) rom from XDA and put it on the sd card and flash - go to settings>update and it should find it or go to recovery, flash the rom but be prepared to wipe the phone or it will ask for a password when booting. This may erase your data so backup 1st...
I also got an Axon 7 from Ali-express and it was the base B07 rom that it shipped with....
Yep update to b013 then you're rocking into android 7 and OTA updates from then on
Ok
Hi, I met some problems with my Nova plus mla-al10.
In short, the phone cannot boot and I need help with getting the offical emui5.0 dload upgrade package. (probably)
Below is the whole story:
1. The phone is unlocked.
2. Upgraded emui4 180 to emui5 in the emui4 system. The system indicated the target version is emui5 352. After updated, my version turned into NRD 90M test-keys without many huawei custom apps. ( I think it's because of the lack of data-update package, but it's too late now)
3. I tried to solve the version problem and I flashed the phone through fastboot with RECOVERY, BOOT, SYSTEM & CUST extracted from the downloded update packages. ( First 358, later I tried several other versions, same failing)
4. Then I cannot boot my phone. Just enter erecovery after 2nd reboot, and I cannot get the Rom downloaded through erecovery. Error reported.
5. Then I tried the dload update mode with a certain emui4 dload rom which I can only got from the internet for the MLA version. I cannot make sure what the ROM version was, like b122 or b133, emui4. I failed during update in the official recovery. 5%, 45% ,several times.
6. So I tried to use the twrp and both lineage and asop rom from #Henkate. Thank you #Henkate, the phone booted again. The system worked fine, except for one problem: When I use the China mobile(TD-LTE) and China unicom(WCDMA/LTE), I cannot dial out or dial in ( busy line). The sms and data(internet) worked fine. The signal is good. The sim card seemed to be successfully registered. China telecom seems worked fine(FDD-LTE) with dialing, sms and network. By the way, the china telecom simcard is the first card I used in the first lineage's first boot. I just found it abnormal with the problem above recent days.
7. Then I flashed the asop from #Henkate after wiping the system, cache and data. The same problem.
8. Now I cannot get where the problem is. I guess maybe the baseband software got wrong, so I wanted to flash the modem.img into the phone. The only way I think possible is to flash the dload package with version above 358 (or 360 which I also flashed through fastboot)through the huawei official recovery. The question is where I can get the package and is it the right thing to do? If not, how can I get back to the offical EMUI or other roms functioning normally?
Please help!
Thank you in advance!
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
Most pie roms are base on the latest stock pie firmware, you probably need to flash that. Plus Ur twrp version is probably not the newest, all the links are available in the telegram group, and I'm not going to put them here out of respect for the devs. But .339 firmware is the Oreo firmware, I think the one u need to flash is the .050 firmware.
The telegram groups have them all and a little searching can give you all the links you need.
Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
The latest Pixel Experience works great!
So you are on the Stock Firmware then.
1) Unlock the bootloader by Unofficial method (It will help when you want to relock it in future.)
2) Flash the latest TWRP Recovery.
3) Download whatever ROM you want to install and read all the requirements first! The error 7 you mentioned was the Firmware issue and could have been fixed by flashing the Firmware first and then the ROM.
GApps are not required for Pixel Experience as it comes with all the necessary Google Apps.
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Sovjohn said:
Hello,
Recently a Huawei P9 lite VNS-L21 came into my hands. I experimented a bit with unofficial ROMs but eventually flashed the official back. I had flashed an earlier version, ending in 380 I believe, but because the phone attempted to upgrade to the next incremental update (say, -382) I decided to upgrade myself to the latest supported version (506). I used Firmware Finder to find the firmware and downloaded it to SD card.
Upgrade succeeded - since I had left TWRP recovery in the phone, I used the HuRUpdater which worked flawlessly.
The only small issue is that following this update, a red message is displayed on boot saying the device has failed verification.
Any way to solve this?
Click to expand...
Click to collapse
Hello,
my doubt is that you flashed a different firmware version from the one you had, thus corrupting the device's oem file. Could you post which was the latest complete firmware without this problem and the last one you downloaded and flashed? ( ex. L21CxxxB382 & LxxCxxxB506 ).
Let me know this info ...
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Sovjohn said:
Hi,
I went from l21c432b380 to l21c432b506 during this process. Stock OEM file was flashed before the -380 upgrade (no errors existed, the 380 upgrade followed a flash of -370).
I'm not sure why this is happening - I mean, both firmwares were from the firmware finder app... Weird, to say the least.
Click to expand...
Click to collapse
Yep, you used correct file but anyhow the firmware has been corrupted.
I think you have some ways to solve...
1 - if you have stock recovery, reboot into it and
download and flash the same latest firmware.
If you do not have it, you can extract (with huawei update extractor) it
(should be recovery1.img) from B506 firmware (update.zip) you already got,
then can be flashed via fastboot commands.
2 - Flash a previous or B380 firmware via HuRUpdater, then
update to latest via Firmware Finder with dns/vpn method.
3 - Repeat the whole job you done with B506 firmware. (via HuRupdater)
4 - Reboot recovery, reflash L21OEMinfo file, dual sim one, then the latest firmware again...
P.S.: method 1, 2, 4 will re-lock the bootloader, no problem if still you got the code...
Beware method 4, after you flash the oeminfo file do not shout down, reboot to bootloader
and unlock it again with the code. Device will reboot into twrp, then flash B506 firmware.
Good luck and let the community know..