3
donuts
29d

HELP!!! I fucked up my OP6 again trying to install Lineage 17.1.

I was running Oxygen Pie and folloqed steps .. Flashed Lineage Recovery 20200609

And then the rom but just boots into Fastboot now.

I'm guessing it's bc I didn't first install Oxygen 10 and upgrade the firmware?

Not though I'm trying to sideload the zip but it keeps stopping at Signature Verification failed.... Even though I said override...

Comments
  • 1
    Did you do the factory reset prior to flashing?

    Also, do you have any custom recovery currently flashed (as in - TWRP or Clockworkmod... basically, could you flash a zip)?
  • 2
    @theKarlisK I can adb sideload, only recovery is there LineageOne but it's refusing to install Oxygen... bc of some signature verification failing.. even though I told it I don't care...
  • 1
    @billgates did you check that the downloaded files aren't corrupt? One thing I don't miss from flashing custom ROMs is their respective authors uploading to absolute shite filesharing sites filled with all kinds of garbage embedded into ads and throttled snail speeds as well as a notice 'DON'T MIRROR' on the description / install notes. I'd often get incomplete or corrupt files because the server decided to time out because I've had enough data with my single download and should come back another day.
  • 2
    @theKarlisK Well I'm trying to flash the stock rom now but the Recovery won't let me.

    And not sure which OS now. I tried Fastboot boot twrp.img but just freezes.

    Not sure if that's the right and though. Not sure if I should use flash boot ... That just makes it permanent installed in boot partition? I don't want to brick it any further?
  • 1
    @billgates I believe you can't "fastboot boot twrp.img" - what you probably want is "fastboot flash recovery twrp.img" then "fastboot reboot recovery".
  • 2
    @Haxk20 mind if I summon you? Haven't flashed ROMs for quite a while, so the usual flashing steps from memory are a bit foggy to me.
  • 2
    I dont have much experience with OnePlus tho from general things. Signature verification is vbmeta shit. Basically meaning it checks the partition data for checksum. If it doesnt match one of predefined keys it wont boot and show you verification error. One way to disable that is flash vbmeta image that has this verification disabled. Tho im not sure if thats correct for OnePlus.

    Tho lets get to debugging. Have you unlocked the bootloader ?(I guess yes as you can flash stuff but you never know). Have you flashed only TWRP image ? Were you supposed to flash it or just boot it. Which partition were you supposed to flash it to ?

    There is really so many questions i have so please paste here EXACTLY what you did. Step by step. Dont skip even the slightest thing. EVERYTHING.
  • 2
  • 2
    @Haxk20 So continuing from my original post, I try to restore OOS by ADB sideload Oxygen22 OTA 45 zip using the LineageRecovery 17.1 20200609.

    Even thought Lineage didn't work, there's Fastboot and can go into Lineage Recovery.

    But when I do the sideload of OOS, it says signature, I say fine, continue. Then it says this is a downgrade. Again Ok.

    But then it stops with error: signature verification failed.

    In this recovery there is no glibal option to disable it like TWRP
  • 2
    @billgates does the OTA file have fastboot at the end of it ? Even if not open the zip file and look if there is flash-all file. If yes. Extract the zip and launch that file with the phone connected in fastboot mode.
  • 2
    You might see invalid source file at header magic or something like that. Don't cancel it. Just wait. It should finish just fine.
  • 3
    Either way. Here is a link that should help you get your phone working once again. https://forum.xda-developers.com/on...
  • 2
    Also in case of flashing ROMs. Please don't assume things and follow the guide unless you are absolutely sure you know wtf you are doing. There are guards put in place by OEM and Google that if you do not follow the guide could render your phone bricked. People forget that this isn't just oh just flash that and that. One slip and you can really fucj up your phone. It's usually recovereble. Tho most people don't know how to recover from the state where even kernel doesn't start which can easily happen if you are not careful.
  • 2
    @Haxk20 Yea I did flash Lineage 17.1 before but went back to OOS for other reasons so thought it would be easy but last time I was still using TWRP.

    And I think I did a dirty install, so didn't do a full wipe.

    This time I followed Lineage all the way and well now their recovery is being a b*****
  • 2
    @billgates flash stock. Then go to lineage again if needed.
  • 3
    @Haxk20 that's what I've been trying but via recovery but I see I can flash directly...

    But yes will read over this
  • 3
    @billgates yes you can flash it directly. The recovery method is not very recommend unless you are just upgrading or something small.
  • 2
    @theKarlisK You can actually do fastboot boot recovery.img!
  • 2
    @linuxxx not dinner Android 10... All images just fail our freeze on boot .... Seems need to be installed on recovery but I don't wanna screw up recovery.

    Though since fastboot can flash not an issue not... But I didn't know it remember that
  • 2
    Ok I got Lineage 16 installed... seems LOS Recovery had no problem with that..

    But it really hates me trying to overwrite it with OOS....
  • 2
    @billgates How does it hate you? Also, make sure to do a full wipe in recovery before flashing!
  • 2
    @linuxxx this whole rant describes that? The official rom fails LOS Recovery's signature verification but telling it to install anyway still fails... because signature verification
  • 2
    @Haxk20 where do you get the flash all bats?
  • 2
    @billgates you should have it in the OTA zip.
  • 2
    @Haxk20 ah ok, so need to download from that site not there one from OPO, it just has payload.

    But now I just tried fastboot flash and it works!

    So let's see... Do I really installing Lineage 17.1 now? At least now I'm explored all possible way it fails?
  • 3
    @billgates you are not even close to all ways to fail. Even I haven't seen them all yet. And I have seen a lot of ways to fail.
  • 2
    Also just stay on oos if it works. I mean lineage doesn't provide that much stuff that's not in oos.
  • 2
    @Haxk20 I want to update would having to reroot every time
  • 2
    Originally this morning is was thinking...I would upgrade to 10 now so let's switch to Lineage so don't have to keep losing root Everytime there an OTA...

    But yes harder done than said...
  • 1
    After a whole day... I'm back to where I started mostly...
  • 1
    @billgates last time i had a device that was flashable i had to update the bootloader to go from gingerbread to ics... why can't it just be simple anymore? I don't wanna have to pay $50 or more to get a code for the cheapest phone I can manage to get to work just so i can have it on-hand but *nooo* i have to go through 18 extra steps and a third-party or three to get a code to allow me to do anything.
  • 2
    @Parzi don't buy shitty devices. Sony and most oems allow you to unlock bootloader for free. It's just shitty oems that don't.
    Sony even provides device trees and mostly working AOSP ROM that we are as community working on. Well community mostly 12 guys working on it in their free time.
  • 1
    @Haxk20 My absolute best-case phone constraints:

    AT&T under $100 total with no monthly pay, no new plan discount.
  • 1
    @Parzi Dont expect an normal unlockable flashable phone then. As i can say. You want too much for your money.
  • 1
    @Haxk20 i'd just prefer something that i can digitally duct tape together a little better is all
  • 2
    @Parzi You know you can always sue the company if they dont give you kernel source. After you have that you can start the 3 months minimum journey of porting device trees and making everything on the phone working with stock android. Yeah dont expect someone to spend that much time on a phone that is under 100$ and breaks in a year or so. Its just not worth it. I mean you can do it. Nobody will stop you. Heck the people who have the phone will be happy even. But yeah no normal dev would spend time on it. Its not worth it. Get realistic with your money. You can get cheap ass phones. That doesnt mean you should tho.
  • 1
    @Haxk20 "just buy a better phone lmao" With what money?
  • 2
    @Parzi idk. Save up as most people do to buy phones. Because realistically even if the cheap phone lasts 1 year you have to buy one each year. 3 years and you could get the exact same phone I have. Xperia 10 Plus. Full ROM support. Just everything you will ever need. Heck the phone will most likely get even cheaper once 10 MK2 is released. So yeah.
  • 1
    @Haxk20 they either break or fail 1-2 years in average, even the only expensive phone i've ever had has done that, and i dunno if you noticed but there's both a pandemic and major unrest in my country.

    So, again.

    Save what money?
  • 1
    @Parzi oh you are from USA. Didn't know that. But when you can try to save up. Try Sony phone or some older OnePlus. Great OEMs that support the ROM community and even send devices to the people to work on them.
    Tho in Sony the cheap low end phones don't get support. The support starts at middle end.
  • 1
    And what was the expensive phone ? Because phone should last good 4 years before needing replacement. At least I never needed to buy phone sooner then 4 years after the one I just bought.
  • 0
    @Haxk20 LG G4, y'know, that one model of LG phone where the QA and solder jobs were so shit that almost every single one ever made was defective?

    The only expensive phone I've ever had, and i got it new too...
  • 1
    @Parzi oh LG. Yeah I do not recommend their phones even in the slightest. Complete garbage usually.

    But as I said. I know it's hard with the current situation. Try to save up somehow and buy Sony or oneplus. Tho with Sony go for mid range. Otherwise nearly no support.
Add Comment