Hello, Today i wanted to install Lineage OS 16.0 on my Phone and it shows me an Error in TWRP Recovery what shows: "Error applying update: 18 (ErrorCode::kDownloadPayloadPubKeyVerificationError)
Updater process ended with ERROR: 1
Now i have no OS and dont know what to do...
I have no idea what i should do now...
Thx for Everyone who is trying to Help!
xArekkusu said:
Hello, Today i wanted to install Lineage OS 16.0 on my Phone and it shows me an Error in TWRP Recovery what shows: "Error applying update: 18 (ErrorCode::kDownloadPayloadPubKeyVerificationError)
Updater process ended with ERROR: 1
Now i have no OS and dont know what to do...
I have no idea what i should do now...
Thx for Everyone who is trying to Help!
Click to expand...
Click to collapse
Hi
I don't have unlocked bootloader, so I can't help you more in that side.
However, I can help you in the "no OS" problem, because after 3 days I think that lineage isn't your main idea anymore
To flash stock firmware, even with unlocked bootloader, you have to use in your PC or "EMMA" tool by Sony, or newflasher.
You need stock ftf firmware to do that, easily downloadable in the link https://xpericheck.com/ .
If what abovementioned doesn't work, simply relock bootloader and perform a clean install via Xperia Companion (with your PC).
Hope this helps :highfive:
If you need more help, just ask
Related
On 551 Z00A or AD the official downgrade version of LP WW-52.20.40.196 firmware from any M stock firmware - via sd card
https://www.youtube.com/watch?v=_1T6SMJiUSg&feature=youtu.be
Success -- Downgrade of MM to LP works with the downgrade firmware above , works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , it detected .134 and ..144 and .184 MM update packages and now also should detect .223 latest firmware if on ext SD if written like mentioned and shown in the video !
The above LP downgrade version is detected in .223 latest M firmware after a reboot.
Some pics
Seeing a lot of people bricking their devices downgrading to LP from M .
There is now no need for all these bricks when we can downgrade via M recovery to LP via ext sd card .
If you are on a stock rom MM bl and rooted TWRP ..you just need to flash stock boot.img and recovery for the MM build you are on . Reboot to stock M recovery. Follow above procedure.
If you are on M bl custom Rom and rooted TWRP but have no stock M back-up , flash back boot.img and recovery for.134 , sideload .134 stock. Then downgrade
That above applies to 551 Z00A .
Merry Xmas to all at XDA --Still seeing people looking to downgrade from M to LP even after posting this method above via ext SD card - WOW
So , my present to you is a video of the above process
Say NO to anymore bricks Say NO to ever having to use xFSTK downloader again
This makes our phones fully , changeable forwards and backwards via SD card (for good)
The process will go from .184 M to .196 LP on the 551 Z00AD or Z00A
If you Have MM bl custom rom - use giovix`s Modder tool to `return to stock option` flash boot.img - flash recovery option in Modder . Follow process.
Video Coming Soon ...........
Ps, i assume the process will be exactly the same for Z008 from the latest Stock M to LP but using the relevant downgrade version(whatever that is) from official ASUS site for Z008
I dont have a Z008 so if anyone wishes to attempt it and give me your results here , that would be great for others
pps, i decided to do the video due to either people dont trust this method or people are extremely shy about hitting the thanks button . Whichever -- help others
Yup, using the Asus files to downgrade from MM to LP bricked my brother's phone. I've tried a few methods with xFSTK to fix it but nothing has worked so far. Looks like the phone will be recycled Oh well, he seems pretty happy with his Samsung Note 3 for now
audit13 said:
Yup, using the Asus files to downgrade from MM to LP bricked my brother's phone. I've tried a few methods with xFSTK to fix it but nothing has worked so far. Looks like the phone will be recycled Oh well, he seems pretty happy with his Samsung Note 3 for now
Click to expand...
Click to collapse
Yup , even tho i can unbrick in xFSTK in less time it takes to downgrade (everytime success btw) -- pay attention to the video... on the edited files i show in file manager
timbernot said:
Yup , even tho i can unbrick in xFSTK in less time it takes to downgrade (everytime success btw) -- pay attention to the video... on the edited files i show in file manager
Click to expand...
Click to collapse
Thanks, I'll give it another go when I have a chance.
audit13 said:
Thanks, I'll give it another go when I have a chance.
Click to expand...
Click to collapse
You need to have a working device to downgrade via SD :good:
Okay, I was able to restore stock MM to the phone which is what it has before it bricked. Problem now is that I can't verify the Google account I tried both of my google accounts without success. I'll have to find some other method.
audit13 said:
Okay, I was able to restore stock MM to the phone which is what it has before it bricked. Problem now is that I can't verify the Google account I tried both of my google accounts without success. I'll have to find some other method.
Click to expand...
Click to collapse
But you was bricked a moment ago - no comprehendi ?:laugh:
If you used xFSTK you wouldnt need to downgrade , you would be in LP already.
If done on another device try later , maybe a reboot :good:
I was bricked and was able to iFSTK to get into the bootloader. I then used the Asus Flash tool to flash an MM raw file to at least get the phone booted. I was happy until I was stuck at the set up screen with no way to verify the google account.
Now its time to party vid coming soon .
All the very best wishes to each and all
audit13 said:
I was bricked and was able to iFSTK to get into the bootloader. I then used the Asus Flash tool to flash an MM raw file to at least get the phone booted. I was happy until I was stuck at the set up screen with no way to verify the google account.
Click to expand...
Click to collapse
MM raw file Hey , please share here ?
If there even is a MM raw file that is
Flash 5.0 raw for 5.0 then you wont need to downgrade btw
And this is nothing to do with downgrading via SD card btw - off topic
I believe I used the MM ww raw file from here: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
audit13 said:
I believe I used the MM ww raw file from here: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Do you know what you are doing ?
Saying , posting ?
Do you have a zenfone ?
Let me know which one of my posts is confusing and I'll try to clarify.
On 551 Z00A or AD the official downgrade version of LP WW-52.20.40.196 firmware from any M stock firmware - via sd card
https://www.youtube.com/watch?v=_1T6SMJiUSg&feature=youtu.be
OP updated
Merry Xmas to all at XDA --Still seeing people looking to downgrade from M to LP even after posting this method above via ext SD card - WOW
So , my present to you is a video of the above process
Say NO to anymore bricks Say NO to ever having to use xFSTK downloader again
This makes our phones fully , changeable forwards and backwards via SD card (for good)
The process will go from .184 M to .196 LP on the 551 Z00AD or Z00A
If you Have MM bl custom rom - use giovix`s Modder tool to `return to stock option` flash boot.img - flash recovery option in Modder . Follow process.
Video Coming Soon ...........
Ps, i assume the process will be exactly the same for Z008 from the latest Stock M to LP but using the relevant downgrade version(whatever that is) from official ASUS site for Z008
I dont have a Z008 so if anyone wishes to attempt it and give me your results here , that would be great for others
pps, i decided to do the video due to either people dont trust this method or people are extremely shy about hitting the thanks button . Whichever -- help others
audit13 said:
Let me know which one of my posts is confusing and I'll try to clarify.
Click to expand...
Click to collapse
Hi , I understand where you went wrong , you flash raw again in boot loader ,where it stays on ' RESULT=OK ' a couple of mins into flash in on screen cmds , you close flash tools . Force close it...restart flash tools .put all stuff in again ...then press vol+ once.
Leave connected to PC from first part flash all the way through closing flash tools and restarting flash ..do not touch fone apart from vol + before second flash.
Serial will be corrected and you will boot into system.
There is a vid of this exact process in my unbrick thread.
Enjoy
Ps , I never let the first flash finish , due to knowing above process to correct serial..
So if you run into probs , you may need to re flash in xfstk again.
timbernot said:
Hi , I understand where you went wrong , you flash raw again in boot loader ,where it stays on ' RESULT=OK ' a couple of mins into flash in on screen cmds , you close flash tools . Force close it...restart flash tools .put all stuff in again ...then press vol+ once.
Leave connected to PC from first part flash all the way through closing flash tools and restarting flash ..do not touch fone apart from vol + before second flash.
Serial will be corrected and you will boot into system.
There is a vid of this exact process in my unbrick thread.
Enjoy
Ps , I never let the first flash finish , due to knowing above process to correct serial..
So if you run into probs , you may need to re flash in xfstk again.
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU! It worked.
This is what I did to cause the loss of serial #:
used the sd card method to downgrade from MM based on instructions from another forum (i.e. not XDA);
phone got stuck at the erasing portion of the process and stayed there for about 45 minutes so I powered off the phone;
used xFSTK to successfully flash the bootloader
successfully flashed MM raw file with Asus Flash Tool;
tried to downgrade to LP again and bricked again;
used SFSTK again but serial # was now abcde... in bootloader so I used Asus Flash Tool again. AFT never finished flashing a ROMand the phone was stuck on the bootloader screen with "Result: okay" so I just shut down the phone and left it off until I saw your post this morning.
Edit:
I set up the phone ran software update option from settings but the Android Version is 5.0? Also, when I boot into fastboot, I see the serial # as abcde... but I can get the proper serial # by pressing the volume up and down keys a few times. Lastly, my SD card is not seen in recovery but is seen in the ROM. When I boot to recovery from the bootloader, I see this:
Android system recovery <3e>
LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user
E:file path/tmp/last_install
E:file path /cache
E:file path /tmp
Finding update package
Opening update package
E: file path:/sdcard/MOFD_SDUPDATE.ZIP
E: failed to map file
SD installation aborted.
E: Installation failed with status 1
I'm not too worried as these things are cosmetic. The important thing is the phone now works
Just to clear things up.
You never bricked your device using the method in the OP regarding downgrading via sd card. So not to scare people off .
Mofd sdupdate method is for adb sideload using a cable.
In the video it shows how files must be written when downloaded for each stock firmware in file manager in the first few mins. To be recognised from ext sd
Lastly , 2.20 in firmware or raw = LP
4.21 = M which doesn't have a raw yet unless I missed it coming about
So I have been trying to install Cyanogenmod 14, but I am kind of new to this, so I will probably seem pretty stupid. I basically tried to install it but forgot to unlock my bootloader. It was messed up, but I got help to install 2.20.40.184, so it works again. Now, however, I still want to install cyanogenmod 14. Partly because I for some reason don't get the OTA updates (I live in Denmark, where the Zenfone 2 isn't sold, so that may be it), so I've been stuck on lollipop since I got the phone. I don't even get a software update section under settings. So after all this, I tried to unlock the bootloader with the official app that you can download from the Asus website, however, when I do that, I get an error message saying "This device model is not supported". So looking for manual ways to root, I only found one that works with marshmallow, and when I download a ROM for marshmallow, I don't get the notification about an available software update. I also cannot enter recovery mode.
Hope this made sense, and that I posted it in the right place. Thank you!
Asus Zenfone 2
ZE551ML
Z00AD
WW_2.20.40.184
Look for raw file .196 LP from RealYoti on here
Flash it in boot loader, with AFTool
You may have a china firmware converted to WW.
Once you flash try unlock ..or update from sd card to M ...Check my signature for flashing in AFT , also clues in downgrade link for how to write M to be recognised after a reboot for updating
If not got Chinese original serial you should be fine
Then when upgraded to M , Modder tool should be ok for unlocking bl in M
Then you can install 14.1
Hi, thank you very much for your reply.
Should I flash the raw file .196 even though I am using .184 right now? And which of the links in your signature is for flashing with AFtool (and where do I get AFTool?)
I have no idea if I have a chinese firmware converted to WW. Sorry, I am new to this xD
Yes, I am planning to use the modder tool once I have managed to update to Marshmallow.
Thank you very much
try to dowgrade from nougat to marshmallow, according method in detail, and at the end of the flash in the recovery "dm-verity verification failed to check drk first" any solution?
SOLUTION:
SOLUTION: ROOT AGAIN
So im not entirely sure what solution root again is all about. But my story starts here. I work in IT for a company that issues phones out to all employees, and we have 100s, I was recently contracted by IT to do some FRP Bypass, and have been successful until I tried to walk someone doing this to an S7 Active, and they failed repeatedly just in trying to restore the phone with ODIN. They mailed me the phone, and now I have the dm-verity error DRK not installed. I have tried everything I can think of (do not have access to any box or key) so I tried rooting the phone. I have tried both the 6.0.1 and 7.0 roots. Most recently the 7.0, i can flash the eng kernel but it does not boot. Occasionally I can get to the setup screen, but mostly it just sits on the ATT globe or restores to a black screen. I can't actually set the phone up. It is currently FRP locked but I'm not worred about that for now. Any help is appreciated, I would settle for a complete restore to stock, but all FW I have tried (BL2) fails to boot do to DRK.
what firmware was it on ? which have you tried ?..
are you using the princecomsy modified Odin ?
have you tried the qd4 from my thread ?
miniminus said:
what firmware was it on ? which have you tried ?..
are you using the princecomsy modified Odin ?
have you tried the qd4 from my thread ?
Click to expand...
Click to collapse
I have tried every fw I can find on bl2 including the qd4 from your thread. I have tried both official and prince Odin. All to the same results. Right now I believe the device is on pi2 with the 6.0.1 eng AP. That is the only way I can boot the os. The 7.0 eng AP bootloops.
I have successfully rooted my 930a multiple times and many other devices so I am experienced. Not that it matters but I was also able to turn the FRP lock off using the eng AP.
Edit... Obviously I am using 6.0.1 eng with matching fw and tried the 7.0eng with qd4. I can Odin any fw that is on BL2 successfully but without the eng AP nothing will fully boot. And doing 100% stock Odin reflashes does not fix drk
Any final thoughts?
Edit... I shipped the phone back to my company, (it wasn't a personal device). And told them it needed to stay on 6.0 eng to function. And advised they dia it.
I have some proplem with Samsung Galaxy S6 SM-G920VZMA , after flash rom DQD1 has loop boot error "dm-verity error …… failed code : 0x002" Please help.
Hello All!
I'm sorry if this has been asked before but I'm trying to install nougat on my phone and having some great difficulty.
So far my phone is flashed and I was running TWRP 3.0.2 however every time i try to flash a lineage 14.1 based rom it would never work. (tried straight lineage 14.1, nutOS, DOT) none of them worked (wiped the phone clean, then received error 7, removed the assert lines that let in install but just perpetually boot looped) . My many a google searches makes me believe that that particular version of TWRP does not work with nougat. but that's the only version I am able to get working. any newer version of TWRP gets stuck in a perpetual boot loop.
So with that said, if my suspicious are correct and i need a newer version is there anything I'm missing to install a newer version of TWRP? if 3.0.2 is a good enough version to install nougat based rom's what am I missing on that end?
Any help at all would be greatly appreciated! and Thanks in advance!
Ninja edit: I'm runnnig the Z00A (Z551ML) and i've been using using roms/images meant for Z00A
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Slent said:
I'm actually not yet used to these kind of stuffs but I guess your problem has something to do with either your twrp version or the bootloader version, this link might help you. http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
Click to expand...
Click to collapse
Yup that was it. My google-fu is off as i found my answer from a reddit post (5 seconds after asking this question in reddit...) My issue was that i was still on lolipop, the last OTA update and had no idea asus put out a manual update. worst part is, after unlocking the bootloader installing twrp, THEN installing that oem update, that might have cause my phone to crash mid update so it ended up bricking the phone...
I was able to Frankenstein it back together with old parts that I thought were no good, right now I'm on that last manual update and I gotta fight through a few issues preventing the boot loader from being unlocked.
Anyway you were correct, using the last OTA update updates the bootloader so I was stuck cause of that.
Please when i receved update OREO for my moto G5 Xt 1676 dual ? Thanks in advance ,,??
mednazim said:
Please when i receved update OREO for my moto G5 Xt 1676 dual ? Thanks in advance ,,
Click to expand...
Click to collapse
Most probably, you will receive it in this century.. I think. :laugh:
I'll be serious now. Nobody knows when you will receive an update. It depends on your region mostly, but there are also few other factors which can delay it. However, if you don't want to wait anymore and have knowledge of flashing fastboot firmwares, full fastboot Oreo firmware (step-by-step tutorial included) for Moto G5 is already available here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244. Of course, nobody is responsible for any damage you make by flashing it.
it is necessary to unlock bootloader and install recovery for install update OREO ?
mednazim said:
it is necessary to unlock bootloader and install recovery for install update OREO ?
Click to expand...
Click to collapse
No, it isn't. According to posts in the other threads, there are at least 2 requirements to successfully update to Oreo through OTA (https://forum.xda-developers.com/g5...ase-opp28-t3849273/post77771786)#post77771786).
The first one is that system, boot and recovery partitions must be 100% unmodified - restoring doesn't help. If it's once modified, only a full reflash of stock firmware (with equal or newer build) will revert it to completely unmodified state. If you decide to install an update with one of these partitions modified - in the better case, update will refuse to install. In the worse one, it will install, but you will end up with hardbrick.
The second one, your build number must be NPPS25.137-93-2-5 (install script do the checking of the build number in the beginning of the OTA install. If it finds different value, installation will be stopped with some error showing up, but nothing happens, because the whole process of updating didn't start at all).
Thanks bro i will try