Jump to content

Hook

Keymaster
 View Profile  See their activity

  • Content Count

    2,071

  • Joined

  • Last visited

  • Days Won

    353

 Content Type 

Posts posted by Hook

    LineageOS 23.x Official Release for Pro1-X (QX1050)

    in General Discussion

    Posted

    Phew! That was close. Didn't get a chance to update until Tuesday night and discovered my Pro1x had been knocked loose from it's magnetic charging cable. It was rebooting and came up with 7% power. Was it in a boot loop because power was so low? Did I need my rubber bands. Apparently not. Don't entirely know why it was spontaneously rebooting, but it didn't start shutting down again. I connected the charging cable  and turned off the screen and a couple of hours later it was full (Have it set to not charge over 85%. I think I was lucky.  Lol.

    All's well that ends well. 😄

    Lineage-23.2-20260601-NIGHTLY-pro1x with May 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. 

    Changelog:

    https://download.lineageos.org/devices/pro1x/changes

     

    • Like 1
    • Haha 1

    Searching for QX1000 Firehose

    in Support

    Posted

    9 hours ago, dattel said:

    Love you, man. That's great.

     

    Now, the problem is to understand how Method 1 (via PBL) for getting into EDL mode is used.

    If anyone knows which two pads need to be shorted and how it needs to be done, I would be very thankful. Also writing a mail to the user "tdm". Maybe, with a little bit of luck he'll respond.

    You might want to try asking in the unofficial Discord sever. It is much more active than here and some of the old timers who don't come here much hang out there from time to time.  tdm is on Discord, but I have no idea if he will respond to DMs... he doesn't participate in the FxTec server although he is listed there.

    https://discord.gg/D5QkVZuc

    • Like 1

    LineageOS 22.x Official Release for Pro1 (QX1000)

    in General Discussion

    Posted

    3 minutes ago, EskeRahn said:

    Just checked the official download page, and currently it only contains ONE build. I wonder if that is a sign that it is soon dropped completely?

    That sort of happened with the Pro1x as well.  When the first 23.2  build appeared, they did leave 1 23.0 build up but didn't wait for the other older builds to drop off the page as new 23.2 builds were added.  They were chopped.  

    I would guess that as long as one of the devs has a Pro 1 and Pro1x, builds will continue, but have no doubt that means support could end any time and probably be a sudden drop.

    • Like 1

    LineageOS 23.x Official Release for Pro1-X (QX1050)

    in General Discussion

    Posted

    Yes, I am updated to 30.7 as well.  It's easy to do (two taps and reboot) and can be done any time. It doesn't need to be done immediately during OTA to retain root. Obviously, I do need to check more often than I was before,  but it's not a big deal.

    I am curious why I couldn't get the prescribed method to work, meaning not the OTA method @Name_not_avail describes, which is easy enough if I could get to that point, but the initial patching of the boot image to install Magisk initially.  But I'm not that curious. The method I use for initial installation is so much easier and simpler and, as log as it works, I'll keep using it.

     

    • Like 1

    LineageOS 23.x Official Release for Pro1-X (QX1050)

    in General Discussion

    Posted

    well, here's a new wrinkle.  I had been trying all week to install Magisk the way they say to in the official instructions here: https://topjohnwu.github.io/Magisk/install.html#patching-images  This was really just obsession, I don't have a huge need for root anymore.  But no matter what I did, root didn't take and every time I went back to the app it didn't indicate I had root.  I was honestly about to give up, but I hate to be defeated by computers. Lol.

    So I tried on last hail mary. I rebooted into recovery and without reinstalling anything else, I retried my old method of flashing Magisk changing the apk extension on the Magisk file to zip and using ADB sideload. I made 2 changes. One, I eliminated the "-d" option in the sideload command which had crept in because Lineage had used it. I don't even knnow what the option does, but I never used to do it. Second, I used the file for Madisk 30.6 when before I had been using some version of Magisk 29 (I'm sloppy about keeping up with the updates with my method).  I rebooted, opened the Magisk app, let it reinstall using their recommended automatic reinstall, not the find a file and patch it option and, boom, I'm rooted.  The fun will be that I will now be curious to see if, on Monday, I retain root again with OTA.  

    So what happened? Still  don't know. Maybe it was a simple as updaing Magisk. I don't know why that didn't occur to me before, but it had never created a problem in the past that I was slow to update. Right now I'm thinking that may be the most likely explanation. Whatever the explanation, I'm rooted again. 😄

    I think I may be  back to me lovely, boring, repetitive posts every Monday. 😉

    • Like 1

    LineageOS 23.x Official Release for Pro1-X (QX1050)

    in General Discussion

    Posted

    So, I tried doing LOS 23.2 (the Feb 9th update) as if it were a new install with were a new install, doing a factory reset and all.  It just made things worse,,, I got the same symptom of it only booting to bootloader, but worse because I finally could not get back to LOS 23.0 and, of course, I couldn't reinstall 23.0 because that was viewed but the system as a downgrade.  

    So on a whim, I decided to try something. I did the whole thing over again (including factory reset-- nothing to lose at this point), but this time I didn't flash Magisk. Boom, Everything worked.  I was also able to update to the Feb 16th update with the February security patch OTA.

    So what was the problem? Don't really know for sure. My best guess is that, given @Name_not_avail's success, is that LOS 23.2 no longer tolerates the way I used to install Magisk, even though it worked flawlessly up through 23.0. It was, I knew, a no longer fully supported and depreciated install method.  For now I'll rebuild the device and worry about root when I'm done.  I will probably have to, for now, install it from the app and try Name's method to preserve root after that.  A shame.  The old method was so simple. We will see how it all goes next Monday.  🙂 

    Whatever the case, I consider the problem solved for now.

    • Thanks 3

    LineageOS 23.x Official Release for Pro1-X (QX1050)

    in General Discussion

    Posted

    12 hours ago, Name_not_avail said:

    According to the principle of, "Never ask someone to do something that you wouldn't do yourself", by which I lead my life, I just updated my second 1x, the one without any Gapps.

    It worked flawlessly.

    Don't know what to tell you Hook, but this is definitely not a universal problem for the 1x.

    Oh, I agree. I don't think it's specific to any device, and it is clearly not universal, but there have been a couple reports out there of either the same thing or something similar happening on different devices.  No good clues provided by any of the reports. The ones on the bug report Gitlab are being looked into. 

    I tried treating it as a full upgrade and that didn't work either.  At least it still gave me back 23.0. Unless some information pops up about what the problem might be, I will wait until Monday and try the new update. If that doesn't work, I will have no choice but to wipe and do a whole install from scratch. Have no idea what could be creating this problem, but it isn't my rooting method.  😉

    So, upshot, People may do fine with this update. I have no clue why I am getting this. Maybe my Pro1x is mad at me for paying so much attention to Writer Decks.

    LineageOS 23.x Official Release for Pro1-X (QX1050)

    in General Discussion

    Posted

    10 hours ago, Name_not_avail said:

    I would suggest trying the OTA again, stop at the "reboot now" toast, open Magisk and select install to vacant slot, and THEN reboot. Can't be worse than where you are now, and it may well work.

    Sadly, it didn't work.  Had to do the dance to get it to boot back to 23.0. Still have root. The result was the same as previous attempts to upgrade to 23.2.

    I may wait for the next  update and see if things go any better.  Otherwise, I will try installing it as if it were an upgrade even though it is still Android 16.

     

    • Sad 2
×
×
  • Create New...

Important Information

Terms

  I accept