Question soft bricked oneplus 10 pro that worked great with lineage os

Search This thread
By:
Advanced…
Y

yedashare

Member
Dec 7, 2022
11
6
ectoplasma22 said:
Did you managed to get fingerprint working on gsi ?
Click to expand...
Click to collapse
When I started lineageos it ran the wizard for fingerprint but I didn't run it so I cannot tell you for sure that it would have worked.
Besides this I could call, receive call and use location, sound and camera worked just fine, and mostly for me GAPS was working 100 %.
First time I purchased a ONEPLUS phone and last time.
So far I've been working with Xiaomi and for me, they are the cheapest and the best phones. I still have my PocoF2 that I repaired.
My phone is my office, no more OnePlus ever in my office !!!
 
You must log in or register to reply here.

Similar threads

empty.cad
General Oneplus 10 Pro Global Rom India / eu
Replies
352
Views
60K
S
slapman
VovaHouse
How To Guide Root Oneplus 10 Pro (Color OS - Oxygen OS)
Replies
191
Views
39K
GuyInDogSuit
GuyInDogSuit
g96818
How To Guide OnePlus 10 Pro NE2215 ***ROOTED***
Replies
406
Views
50K
g96818
g96818
A
How To Guide Enable Native Call Recording + OP Stock Dialer on OnePlus 10 Pro
Replies
150
Views
40K
Ahmad Rady
Ahmad Rady
Khalid Ghouri
Question Help with Unbricking OnePlus 10 Pro (NE2213)
Replies
158
Views
27K
Ph0nysk1nk
Ph0nysk1nk

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    Y
    yedashare
    I SAVED MY PHONE 🎉🎉🎉
    BACK ONLINE
    THANKS TO THIS POST:

    [TOOL] Oppo/Realme Flash .OFP File on Bootloader

    A tool to flash .ofp files in bootloader mode...
    forum.xda-developers.com forum.xda-developers.com
    WHICH BROUGHT ME BACK TO FASTBOOTD
    AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
    AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
    YES!!!!!!!!!!!!!!!!!

    One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
    I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
    I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
    Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
    And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
    That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.

    A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
    BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
    I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
    View
    3
    beatbreakee
    beatbreakee
    yedashare said:
    and this is where I CRUSHED down by running this:

    The rooting​

    get you latest magisk here
    Install it on your phone
    transfer the boot.img you extracted to your phone
    open magisk and install it on the boot.img
    the patched boot img will be in the download folder move it to your pc
    open the fastboot tools folder and open a terminal
    adb reboot bootloader fastboot flash boot magisk_patched.img
    when your booted open magisk and direct install magisk.
    than just reboot
    Click to expand...
    Click to collapse
    This is where your fatal mistake was.... the red line above is incorrect !

    It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"

    you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.

    The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.

    Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.

    When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.

    hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.

    cheers
    View
    2
    TuLy2702
    TuLy2702
    yedashare said:
    THIS WAS TOO GOOD TO BE TRUE !
    After I thought everything was back, I noticed that the battery stopped charging.
    I flashed again Lineageos and it worked but yet the battery didn't charge.
    I re run the python script but this time using another OFP and it showed successful.
    And yet it successfully killed my phone. Completely dead for the second time.
    Hundreds of $ and of hours for a F^&& phone.
    Huge lesson to learn here about choices.
    EoS
    Click to expand...
    Click to collapse
    you make me laugh 😂
    View
    1
    metrixx02
    metrixx02
    u can try to fix sms mms problem using this thread

    xiaomi 12/moto edge x30(or any device with sm8450) sms＆ims error · Issue #2246 · phhusson/treble_experimentations

    Now gsi is able to boot on devices with...
    github.com github.com
    @yedashare

    @dladz maybe we can share it groups ?
    View
    1
    Y
    yedashare
    beatbreakee said:
    This is where your fatal mistake was.... the red line above is incorrect !

    It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"

    you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.

    The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.

    Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.

    When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.

    hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.

    cheers
    Click to expand...
    Click to collapse
    Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
    Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
    I thought that as long as I reach the recovery mode, I can still fix it.
    If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
    And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
    Many thanks for your efforts.
    View

New posts