Related
"Your device has failed verification..." after Firmware Finder update [SOLVED]
Hello to everyone!!
I have a problem with my Honor 8, it is the FRD-L09 model firmware B394.
I installed Firmware Finder from Playstore and tried to downloaded the B402 version, it downloaded a lot of packages ota and then tried to install the update without success.
After that, when I turn on the phone, there is this message. If I push the power button the phone starts.
I don't know if it can be useful but if I go into fastboot mode the phone says: phone unlocked and frp locked, but I haven't unlock the bootloader. The phone is new, purchase from the honor site.
Thank you in advance!!
EDIT: I was able to resolve the problem with the rollback guide of huawei, flashing MM via dload!!
When you update with FF, I recommend to use the change DNS thing. Just for the future.
Days Tech said:
When you update with FF, I recommend to use the change DNS thing. Just for the future.
Click to expand...
Click to collapse
I used that option, I did this before on the honor of my friend without issues. I don't understand what happened
xxfraxx said:
I used that option, I did this before on the honor of my friend without issues. I don't understand what happened
Click to expand...
Click to collapse
You can try to reinstall EMUI on it. There is a guide called "back to emui from custom roms", which requires the openkirin twrp, though. Anyway, did you check that you have firmware access with IMEI?
Days Tech said:
You can try to reinstall EMUI on it. There is a guide called "back to emui from custom roms", which requires the openkirin twrp, though. Anyway, did you check that you have firmware access with IMEI?
Click to expand...
Click to collapse
Yes, I checked it before start the update
EDIT: Can I use the restore option into Hisuite?
When using either option, in System Update press the 3dot menu and select full package. This will download one large update rather than the multiple OTA files.
linkazoid said:
When using either option, in System Update press the 3dot menu and select full package. This will download one large update rather than the multiple OTA files.
Click to expand...
Click to collapse
I will do that, thanks!!
There is no way to fix this problem?
EDIT: I was able to resolve the problem with the rollback guide of huawei, flashing MM via dload!!
xxfraxx said:
Hello to everyone!!
I have a problem with my Honor 8, it is the FRD-L09 model firmware B394.
I installed Firmware Finder from Playstore and tried to downloaded the B402 version, it downloaded a lot of packages ota and then tried to install the update without success.
After that, when I turn on the phone, there is this message. If I push the power button the phone starts.
I don't know if it can be useful but if I go into fastboot mode the phone says: phone unlocked and frp locked, but I haven't unlock the bootloader. The phone is new, purchase from the honor site.
Thank you in advance!!
Click to expand...
Click to collapse
Typically you get this problem when you install an update without locking the bootloader.. This happened with me couple of weeks back.. I think happens, cos during the process of the update the bootloader gets locked, but it doesnt come up on the fastboot (donno why)
I just unlocked the bootloader using the OEM code and voila it worked... I was able to get ride of this message as well as root the phone.. Do try and let me know!
@kishorev
have you asked OEM code from huawei site?
Hnktc said:
@kishorev
have you asked OEM code from huawei site?
Click to expand...
Click to collapse
Yes the bootloader unlock code..
Hi mates
I updated my S8+ to Multi-CSC OXM G955FXXU1CRB7 , no root all oficial other that I lost volte (CSC related) everything is working just fine.......but i notice i do not have the OEM Unlock option under Developer Options, did anyone notice that? is somewhere else??......
MAX 404 said:
Hi mates
I updated my S8+ to Multi-CSC OXM G955FXXU1CRB7 , no root all oficial other that I lost volte (CSC related) everything is working just fine.......but i notice i do not have the OEM Unlock option under Developer Options, did anyone notice that? is somewhere else??......
Click to expand...
Click to collapse
This is a known issue I dont know the exacts as i dont own exy but it has to do with leaving the devie on for so many days
TheMadScientist said:
This is a known issue I dont know the exacts as i dont own exy but it has to do with leaving the devie on for so many days
Click to expand...
Click to collapse
Hi mate
I read that somewhere and it looked strange to me , it said something about 7 days on...... well i guess time will tell
Thanks for the info , let you know in a few days....
MAX 404 said:
Hi mate
I read that somewhere and it looked strange to me , it said something about 7 days on...... well i guess time will tell
Thanks for the info , let you know in a few days....
Click to expand...
Click to collapse
yea its not lying
latest version is CRC7
its been out about a couple of weeks I believe.
I downloaded it from Sammobile.
Flashed via latest Odin.
on my S8+ G955F developer options still has
option for
allow oem unlock
TheMadScientist said:
yea its not lying
Click to expand...
Click to collapse
paul_59 said:
latest version is CRC7
its been out about a couple of weeks I believe.
I downloaded it from Sammobile.
Flashed via latest Odin.
on my S8+ G955F developer options still has
option for
allow oem unlock
Click to expand...
Click to collapse
@TheMadScientist , you were right after 8 days of flashing OEM unlock is back
@paul_59 , I flashed CRC7 with odin also , I changed the CSC my original country CSC is not available yet so I used the unbranded version for my country
Hello, after 8 day powered on phone, "OEM unlock" still invisible.
My version: R16NW.G955FXUU2CRED. I can't downgrade ;(
Hello guys i just want to report some "bypass"
So i got my s8+ this morning and i cant find the OEM UNLOCK option so i search our beloved forum and find the answer but didnt work (the change date 7 days backward method)
So out of curiosity i change my date to 3 month ago and check update but still no oem unlock change 4 month check update still no oem unlock and then i change it to february and check update and VOILAA!! the oem unlock option appear and i changed the date without rebooting the device so just spam change date and check update im on latest CRF1 V2 bootloader
Sorry for double post but i cant edit in xda labs This is some pic from my phone
I have a seemingly stupid but still annoying problem. As many of you know Android 8 + EMUI 8 came out this summer and I have updated my Honor8. Everything works well, even better (especially with regard to the battery) apart from a problem, quite annoying. I have seen that everyone around complains about the same problem, so it is clear that both a build bug and not a local problem.
Basically ... the bluetooth link with the multimedia system of my car doesn't work as it should, while it worked well with the 7.0.
Tracknames, music infos disappears, sometimes it connects regularly, starting the music, sometimes nothing happens, sometimes the music passes from the car speakers to smartphone (!!)... in short, manage the music in the car It has become a big problem!
I tried all possible options; reset pairing, reset bluetooth, clear cache, activate the developer options to control some low-level aspects of bluetooth, and finally installed Bluetooth Auto Connect which also has several advanced options. Nothing works. In the meantime an update of 8.0 has been released (mine is the buiold 521). The update came out in September ... maybe (MAYBE) this update fixes all bluetooth issues (but i don't have any detailed info about). Until today I have not received any updates and normally I check new version regularly every day. At this point I decided to return to Nougat!
And here the adventure begins!
I CANNOT IN ANY WAY do the downgrade.
What I tried:
- through HiSuite. The "back to previous version" option appears random (rarely); normally the program tells me "the system is up to date". Once appeared I tried to run the procedure, but after the decompression it gives me an error "error updating".
- by standard Rollback procedure. Using a microSD and putting the full version of Nougate in the dload folder. The installation starts but stops almost immediately with the same "update cannot be applied" error.
At this point I am desperate. I cannot update Oreo, I can't go back to Nougat and meanwhile the bluetooth still doesn't work with my car. Remember that before Oreo, everything worked very well!
What can I do? Can you help me?
Thank you
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
m2relax said:
hi / i can help u / pls say me this:
your region(Ru/Eu/Cn.......)
your model( FRD-L09/L19/L04........)
Your Build number
and which build you upgrade to emui 8
Click to expand...
Click to collapse
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Thelothian said:
Region: EU
Model: FRD-L09
Build: 8.0.0.521 (C432)
Previous Build: don't remember. It was Nougat, and I've upgraded around the first week of September. From that day I haven't received/applied any patch, because nothing appears until now.
This morning I've tried again with HiSuite. As usual it says I'm running the latest version and it doesn't offer any downgrade option .
Click to expand...
Click to collapse
dont worry/ do u change region of your phone past?
m2relax said:
dont worry/ do u change region of your phone past?
Click to expand...
Click to collapse
Never. And never jailbroken or rooted...
Thelothian said:
Never. And never jailbroken or rooted...
Click to expand...
Click to collapse
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
m2relax said:
ok / pls do this work step by step :
1-Get Unlock Code for your Phone
2-Unlock your phone with Unlock Code
3-install TWRP recovery
4-after install TWRP notice me to send a file for u ( u must flash it from recovery TWRP )
5-after flashing u most install recovery stock
6-End and your problem is done! :fingers-crossed:
Click to expand...
Click to collapse
I Heard TWRP doesn't work well on Oreo...
CurlyApple said:
I Heard TWRP doesn't work well on Oreo...
Click to expand...
Click to collapse
no if you use multi tools 8 for install twrp its work perfectly on oero
m2relax said:
no if you use multi tools 8 for install twrp its work perfectly on oero
Click to expand...
Click to collapse
The more you know...
Finally I've decide to try updating to 8.0.0.562. After a month of tries, fails (damn Huawei and his stupid update system), errors and a lot of other stupid things, I was finally able to update my Honor hoping the latest version will fix all the problems. It was a enormous waste of time (searching around internet)... but in the end I found a method described here: https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-bricked-t3868085#4And if you go ahead you should find the correct firmware link (on a Russian site). Although, IMHO, failing with the classic method was due to the impossibility or some bugs in the update system, to unpack the update files on sdcard. So the solution seems to be to leave both the zip and the unpacked folder.The problems with bluetooth remain, but I hope that now there is not to be crazy applying next updates. ATTENTION: the method above is NOT valid for rollback! If you try, you'll brick your Honor.
And finally I've taken an important decision... for me this is the last Huawei/honor device. Next time I'll go to another brand, with a serious update system.
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
scseke said:
Hello,
I have the same problem whit my honor, bluetooth lost signal random times, and my battery is faster get low, on android 7 i dont feel thees problems. Anyone have an idea how can i downgrade to nougat or marshmallow? My phone infos:
-FRD-L09 8.0.0.521(C432), I bought it in Hungary (i think its an EU modell), the phone have an unlocked bootloader, and flashed whit TWRP recovery
Who know the solution, pls reply here or, write me an email. Big thanks
Click to expand...
Click to collapse
flash this file with twrp and install stock recovery and do reset factor / finally use hisuite to rollback
I have just installed December 2019 security patch via OTA and now I can't connect to any WiFi any more. It scans and detects networks, but it won't connect. It asks for the passphrase of networks which have already been stored, I enter it and then it says "could not save network" and "could not connect to network". Anyone with the same problem?
My idea to solve this was to boot into recovery and clear cache partition, but this option is simply missing in the recovery menu. Any idea how else cache partition can be cleared without root?
Maheshwara said:
I have a Moto Z4 XT1980-3 (Unlocked retail version with RETUS channel) with bootloader locked - no modifications from official state so far. When I got the December 2019 security patch upgrade, something network-related got corrupted - I have not been able to connect to any WiFi at all! This was the origin of all the desaster.
I read through the internet and found the information that it could happen that an OTA upgrade may not have been got on the device properly and if there are any hassles afterwards, it is required to do a full flash of the recent firmware. Okay, no problem, I thought. I am really familiar with ADB, fastboot and so on, and so I did. Took the recent firmware from here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/ (the one uploaded on 6th of December 2019).
The result was that I could flash all parts of the firmware, except of boot, vbmeta and dspso - for these parts I got a "(bootloader) Preflash validation failed" error. So now I am with an inconsistent firmware state and can only access fastboot mode (not even recovery). Plus sometimes when booting it, I get errors of unbootable A/B slots in the bootloader log. After having flashed gpt again, these errors disappear and I simply get the message that my device won't boot because of an invalid operating system.
What I have already tried to do:
- flash a full factory image (see above)
- use RSD lite (this tool detects my device as connected, but with no device information at all (only "?") and says it can not be switched to fastboot mode - but I am in fastboot mode already ???)
- use LSMA Smart Repair Assistant (this tool says my device is not compatible)
- Blankflash (I have not found out yet how to get my device in edl mode from fastboot)
As bricked devices are a more general Android issue and Moto Z4 is not very spread (the corresponding device forum is almost dead), I try to ask my question here in the general Android troubleshooting section. I hope, somebody can give me any advice how to reanimate my device. Maybe, anybody with special Motorola experience who can tell me why I can not flash the full factory image or explain how I can get boot, vbmeta and dspso back to the device. Any help appreciated.
Click to expand...
Click to collapse
Not being able to flash the boot.img likely means you are flashing the wrong firmware.
Either an older version or the wrong software channel.
sd_shadow said:
Not being able to flash the boot.img likely means you are flashing the wrong firmware.
Either an older version or the wrong software channel.
Click to expand...
Click to collapse
This is what I have been supposing, too, in the meantime. Channel is correct, but obviously, the image I have is too old.
Any idea where I can get a factory image of the most recent firmware version from?
Gesendet von meinem Moto Z3 Play mit Tapatalk
Maheshwara said:
This is what I have been supposing, too, in the meantime. Channel is correct, but obviously, the image I have is too old.
Any idea where I can get a factory image of the most recent firmware version from?
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
Unfortunately there is no official way to get Moto firmware.
There has always been people who have access, that reupload firmware.
https://mirrors.lolinet.com/firmware/moto
Is currently the best updated site.
Hopefully a newer version is uploaded soon.
Otherwise you could contact moto support.
Is it still under warranty?
Sent from my mata using XDA Labs
This XDA post contains links to unbricking tools for Moto devices.
RSDLite does not work on Windows 10. If you have a Windows 7 machine, you might want to try that.
Otherwise, go here for a video for converting RSDLite XML files to Windows batch files
The download link is hard to find, so here http://rootjunkysdl.com/files/Android Programs/RSD_Lite_Motorola_XML_To_Batch_Script.zip
Make sure you download the SDK platform-tools from Google, I had problems when using the one included. Replace adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and fastboot.exe from the firmware converter with the ones from the platform-tools package.
If you're not using Windows, make sure you have platform-tools installed and follow this guide to convert the XML file to a shell script yourself, of course adding #!/bin/bash to the first line of the script.
You may also need to edit the resulting batch/script file and replace the target "system" with "system_a" and fingers crossed it'll complete and you'll be golden.
@sd_shadow
I know nothing but the lolinet page for getting firmwares, too. That's where I got the too old image I already have from. I hope, that it will not last too long till a recent image appears there.
In the meantime, I contacted Moto support. My device is still under warranty. They will investigate further how to help me and then get in touch with me again. I hope, I will not need to send it in, because it is easy to solve the problem on my own - I need nothing but such a damn recent firmware.
@Lesking72
Good to know that RSD does not work with Windows 10... My desperation led me to try this. I prefer more platform independent ways of flashing, because my daily driver is Linux (with a Windows 10 VirtualBox which I only use if there is no way around). To transfer the support or flash file of the image to a linux flashing script is quite simple. Fastboot flashing commands are always the same - there is only a need to look which partition to assign which file to. All information about this can be found in the flash file. The main thing for me is, that now, I know where the problem is: I do not have a firmware which is new enough to flash it with bootloader locked. So no RSD, flashfile converters, Blankflash or what else will help me in my situation. I will have to wait for a factory image with a recent firmware. Damn! I can not do anything else! This is what is really annoying to me.
Even more annoying is that I can not even unlock the bootloader to solve the problem, because the "Allow OEM Unlock" flag in developer settings is inactive! At least I think so... Any idea how to find out if this flag is active or not via fastboot without voiding warranty? I can get the unlock data via fastboot and so request the unlock code, but what if when unlocking it says that it can not be unlocked because of this flag being inactive? Then I would have lost my warranty for nothing. Too risky...
I have also played around a bit with this Moto LSMA Tool. It does not even detect my intact Moto Z3 Play in fastboot mode!
@Maheshwara I was watching the rootjunky videos I linked in my previous post and for his device, it threw errors for some parts but still worked. It might be worth it to try flashing again, but replace the "system" target with "system_a"
I haven't tried to downgrade the firmware on my phone though, so I don't know if your issue is because of anti-downgrade features or it's just showing those errors.
@Lesking72
The Moto support has already confirmed me that my problems' reason is the anti-downgrade "feature". And I flashed the same partitions like in the image's flash file. I simply built fastboot commands of the information inside.
The only thing that could solve my problem is to get a recent factory image or find somebody with unlocked Z4 version with RETUS channel, bootloader still locked and recent software version, who could backup all the partitions for me.
I have just seen that there is at least a more recent image for Verizon version here: https://mirrors.lolinet.com/firmware/moto/foles/official/VZW/
That gives me a bit of hope that there will be soon one for the unlocked retail version, too. Or would it be a good idea to try if I can flash boot, vbmeta and dspso of the latest Verizon image to my device? If I am honest, I do not think so...
@Maheshwara If you tried flashing the newest version boot, vbmeta and dspso from the VZW image it would likely not work because your system partition etc. will be from the older unlocked version you tried to flash.
Even if that weren't the case I don't know if you'd be able to flash the VZW firmware without unlocking the bootloader (I figure it's signed differently to stop people from installing the retail firmware on a VZW phone which would make it not work on a retail phone with a locked bootloader)
The odd thing is that I have no OTA update available and when I connect to LMSA it says I'm on the latest version
Are you already with December 2019 security patch?
Gesendet von meinem Moto Z3 Play mit Tapatalk
I live in México, and i have the same moto z4 than you, 1980-3 US retail, and the ota has not arrived yet,
My last OTA is from october, do you know about other users with the same problem than you? MAHESHWARA
@airecomprimido
No, I don't know about other users who already received the December OTA for retail US version. I think, Moto has withdrawn it because of problems it may cause. I seem to be the only unlucky who already got it.
Gesendet von meinem Moto Z3 Play mit Tapatalk
Maheshwara said:
@airecomprimido
No, I don't know about other users who already received the December OTA for retail US version. I think, Moto has withdrawn it because of problems it may cause. I seem to be the only unlucky who already got it.
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
Maybe you will receive the new fixed december OTA, do you know something about android 10?
Maheshwara said:
Are you already with December 2019 security patch?
Gesendet von meinem Moto Z3 Play mit Tapatalk
Click to expand...
Click to collapse
@Maheshwara i get the OTA yesterday, my phone is with de december security patch, and working fine
https://ibb.co/mNHp69X
airecomprimido said:
Maybe you will receive the new fixed december OTA
Click to expand...
Click to collapse
Too late - my phone is already fully bricked! I will have to wait until a factory image with December patch version will appear somewhere. No other way to revive it... No boot, no OTA, but good to know that it seems to have been definitely rolled out now. So there's a bit of hope that the full factory image I need will be available soon.
Got the factory image version I needed this morning. After having flashed it my device got revived. So far so good, but WiFi connectivity was still broken. After having done a factory reset everything was fine.
But no good that a simple OTA security patch upgrade craps a device with necessity of a full reset.
Gesendet von meinem moto z4 mit Tapatalk
I own a Rog Phone 5s (ZS676KS) since one week and tried to install TWRP without success. The result was a bricked phone and stressful days with no prospect of a solution. In this forum I found the following tutorial and completed it successfully
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
The update via the settings does not work, no update is found. So I downloaded the latest firmware from Asus and saved it in the internal memory. After restarting the phone I get a message that a system update is available, but it ends in an error message. I have tried the same with the previous firmware versions, but without success.
I would be very happy if someone has a solution to this problem.
You need to update the phone incrementally. You cant just go from the oldest version to the newest version through OTA updates....
Baby steps.
So i have to Update the next Version after the one i have and so on ?
RT3K said:
So i have to Update the next Version after the one i have and so on ?
Click to expand...
Click to collapse
Yes. One by one.
It takes about.....30 to 40 minutes total.
I've done it.
You saved my day. Its working. Thank you !
RT3K said:
You saved my day. Its working. Thank you !
Click to expand...
Click to collapse
You're most welcome
Now i cant Install any Update past the Version WW-18.1220.2109.149. All before that worked fine.
edit: after a few tries i got it to work.