yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] eKeith:
Ok Bob I gave it a go and successfully rooted my A2020U running stock A10 v2.09. This is my experience...

Firstly, my A2020U could not connect so I used the [MENTION=4911249]Unjustified Dev[/MENTION] Tool ("original tool") to easily determine my com port (i.e. 3). I edited the your scripts accordingly (using Notepad++) and got connected.

I'd rather not fiddle with the hardware buttons to change modes so I used the CLI to "adb reboot edl" to get into EDL mode.

I executed the backup_all.ps1 script.

It echoed several "warnings" indicating that it could not find files. However, the created backup folders did in fact include those files.

I noted that none of the "A" slot files include the "_a" postfix; the "B" slot files did include "_b".

Now I needed to transfer those boot files to my device by first rebooting my device and connecting via MTP.

I noted that the original tool offered a reboot menu option (but sadly only after executing a successful operation). So, not wanting to fiddle, I used the original tool to backup my boot files, then used the menu option to reboot; On my device I then manually selected it to connect via MTP.

After transferring the "boot.img" and "boot_b.img" files to my device, and installing Magisk Manager. I patched them and transferred them back to my PC.

To "flash" (restore) the patched files I decided to cut 'n' paste the two lines regarding them from your Reference.xml file into your rawprogram-specific-files.xml file, replacing your example lines.

I executed your run_write-files.ps1 script and it completed successfully.

Not wanting to fiddle again with the hardware buttons (just so that I can get the reboot option), I backed up the patched files using the original tool and rebooted. Now my device is successfully rooted.

Thank you!

Additional notes and suggestions:

1. Can you please investigate the "false" warnings? See my (redacted) log file attached;

2. It would be great if you could create/duplicate a script within your expanded tool set (or main program) to determine and set the appropriate COMPort (and teach us non-coders the actual commands);

3. Would you also consider investigating and including a reboot device script? (It looks like the original tool calls reset.xml);

4. Note that, at the time of reporting this, the latest versions for the Manager and Magsk are 8.02 (307) and 21.0 (21000) respectively, and that I had to switch the update channel to "beta" for the patched files to pass SafetyNet;

5. Because rooting is a likely use of your tool I am attaching my modified rawprogram-specific-files.xml file which targets the boot files for convenience.
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] eKeith:
If this can help me get my A10 device to a state where I can install a custom recovery and cutom ROMs, I would appreciate it!
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] bobthenormal:
Nice! :good:

For the questions..

0. Thanks for the heads up on filenames! I completely missed that the _a files don't have the labels... As you probably noticed all the files are backed up correctly still (no missing/overwritten files), but I removed the _a from all the A slot files. That was my original "fix", so I guess I started building this package before I got annoyed by not having the _a/_b consistency. I'll update the correct XML file and upload it as a new version.

1. Don't worry about those! They're part of using the fh_loader interface. Warnings are usually just fine, ERRORS are bad. I'll add a note to the post when I get a chance so people don't get scared by that.

It's only when you do a backup the program is really only designed in the "writing" sense, for backups you literally run an identical XML to writing but you send a flag that reverses the process. So it weirdly checks if the files it is going to copy (which of course don't exist) exist, and it throws the standard warning, but then it just creates them (of course).

I can't turn those off without lowering the verbosity setting for that tool. I decided to leave it set to high because if someone has a problem and they post their log file (like so!) it's very useful to troubleshoot.

2. I'll think about it / try. Not very hard to program but a little time consuming.

I'll throw a copy of lsusb.exe in the next version. Windows port of the linux command. People can simply run that on a command prompt and it will list all the active COM ports/devices. If you're not familiar with it - you can also find out by clicking on the windows start bar or pressing the windows key and typing in "Device Manager". In the hardware list there is a category for COM ports where it lists them.

3. Yeah that's very easy I'll put one in the next version as well.

4. Helpful to know. Interesting that you needed beta to pass... I didn't think to mention I use the canary builds (not really recommended... the current one crashes when I try to hide Magisk Manager lol)

5. Thanks! Maybe I should make a directory specific to boot backup/write... but I do think anyone not comfortable doing the change you did might not want to be flashing their boot files anyway haha.. things to consider I guess.

As for getting you back from A10, definitely. I'll figure out how to upload them to one of those file sharing sites in a week or two.

In the mean time, with a backup from this tool you're safe (as far as bricking goes, you'll have to system wipe) to try rafy's EDL backup to revert to A9. I'll find the actual post... I should have been less lazy and linked it in my post lol... HERE - rafyvitto's EDL.

If flashing his backup doesn't boot right away try the tool I included to fix the bootable partition. If it still doesn't work after that (maybe mention here what happened) then just restore your backup.

Do you have the 128gb phone by chance?
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] eKeith:
Thanks much, especially for your detailed clarifications and convenient link!

I have the 8/256GB (P855A03_NA) model.

PS

I want to spend more time on ensuring I have a complete device backup before nuking with another EDL; will dedicate some time this week...
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] bobthenormal:
Oh nice, with the 256gb model you're good to use the userdata backup program too. Sounds ideal for you since, like me, you want a really bulletproof backup. If you run a full backup and then run the userdata backup you literally have a "phone state" so you can return your phone back to exactly where it was, not have to wipe system or anything.

Of course I'd hate to be wrong so as usual, do at your own risk! Lol. But I am using that method and it has worked great. The downside being over an hour of waiting for the userdata to download or upload... and having to store 256gb (for long term storage you can compress it down to literally a few gb).

I've been kinda busy, but working on getting some of those things from my last post done hopefully this week.
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] eKeith:
That's great to know! Your user data backup option has simplified my life.

I will wait for your next revision to do a full backup plus user data before nuking.

I am looking forward to moving on from ZTE's A10 to one of Ray's ROMs...
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] bobthenormal:
Updated to 1.1a - kind of had to rush on some things so keep an eye out for mistakes, especially in the XML files, and let me know if you find any.

Should have an 1.09 (A9) firmware package up "Soon(TM)", just have to make the xml files then upload the file somewhere.

EDIT: Already needed to update to 1.1b - I found that the GPT_Tools had a big error that probably was there since 1.0 and no one noticed! Backups of the GPT should now actually work...
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] eKeith:
Thank you [MENTION=5408979]bobthenormal[/MENTION] !

Looking forward to your A9 EDL backup...
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] bobthenormal:
It's up -- see the new thread.

I didn't have time to test it so make sure you backup but I'm 99,99% sure it will work. I tested it several times in the past, but to make the firmware package I took out all the (I hope) unnecessary files.

There's one thing I'm not sure of - whether you'll need to use the Fix Bootable tool after installing it. IF you need to, then I believe you will have to install it to partition B and then run fix bootable B. (The 1.10 backup was taken originally from the B partition).

If you find that it works without having to do that, let me know... it may not be necessary if wherever that bootable flag is stored didn't get included in the firmware package.
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] eKeith:
Thank you [MENTION=5408979]bobthenormal[/MENTION] !

I should be able to give it a go this weekend and inform...
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] GrayFox1950:
@bobthenormal , first of all: THANK YOU SO MUCH for your hard work. I mean it.

Back in June i tried to flash LOS16 on my A2020G (6GB/128GB) (at first i thought it was an A2020U, but i was wrong). Unfortunately i was stuck in EDL-mode after it.

After that I managed to flash A2020G_PRO_V1.6_FULL_EDL.zip with MiFlash. Im still on this version.

Luckily, a lot has happened in this forum since June regarding the Axon 10 Pro. Now i have more time to spend on it, so I would like to give it another try. I want to flash LOS16 to try out rafyvittos sGSI.

First of all i want to make a "complete backup" (backup_all) of my device.

Which brings me to my question: Can I use your backup_all for my A2020G Pro 6/128?

I want to have at least a full backup of my actual state (without Userdata Backup of course) before I dare to flash again.

I look forward to your answer. You also asked in post #13 for a 128GB Phone. I have one. If I can help you with it in any way - please let me know.
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] bobthenormal:
It *should* work for everything except the userdata as-is, BUT I can't be 100% as I don't have that phone - to be certain I need the files from backup_GPT (in the tools) from your phone. They're very small files so you can attach or PM them. I'll also make a userdata version to work with your phone.
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] bobthenormal:
Hopefully you haven't tried that backup_GPT yet, I went to use it today and realized it won't run as-is due to a small typo , I'll upload a tools version 1.1c with it corrected tomorrow. Once it's up I do suggest running that and uploading those GPT files, it will probably take me some time to get around to making changes to the tools (if necessary) once I have them.. I would expect the partitions addresses to be the same except for userdata, but won't know until I see those.
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] zapata13:
hi guys

i have problem after wrong flash

any with testpoint picture force EDL ,axon 10 pro bricked not detect pc with combinations keys,need force edl by testpoint

not power, not fastboot not qualcomm mode
[ZTE Axon 10 Pro ROMs, Kernels, Recoveries, & Other] MarcelWhy:
I'm trying to go back to A9 using the instructions here

https://xdaforums.com/t/rom-stock-stock-firmware-packages-for-expanded-edl-tools.4194045/

and getting stuck at an error [see attached image]. The phone is in EDL mode but I may well be missing something obvious. Any help would be GREATLY appreciated. Cheers!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Menduksay:
Good day, I would like to ask in this community a question, I recently bought the Kindle HD 10 (2019) and I am very happy with it but obviously the Amazon customization layer seems terrible to me, after investigating I found in this community a tool to remove everything from Amazon and I thought it was great, a great job, very grateful, but the only thing that I couldn't remove was the launcher, that's why I've come to ask you if you can recommend launchers for this tablet, I can't find one that convinces me, thanks in advance .

Any other applications for the tablet that you can suggest will be well received :)
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Noter2017:
The answer will be Nova Launcher. I guess we all tried all sorts of launchers but always end up using Nova Launcher. The premium/paid version is sometimes for sales for 99 cents
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Menduksay:
After download the new version of the Amazon Fire Tools v9 It comes configured with 3 launchers to install, among them is the Nova which I tried but I was bothered by the advertising in its free version so I tried the Microsoft one and the truth seems very good, I liked it, I will continue testing it a few days but I'm very happy at the moment, thank you for your suggestion.
[Tilt, TyTN II, MDA Vario III General] kingofall00:
on my moto Q i can listen to my music on my bluetooth headset, is there any way to get the music play out my bluetooth headset on my tilt? im using romos rom.

thank you
[Tilt, TyTN II, MDA Vario III General] PGenneken:
Try doing a search for BTAudio.. I think that might be what you are looking for.
[Tilt, TyTN II, MDA Vario III General] mech_supernova:
BlueMusic 2.0 works like that the demo only works for 2 min at a time though.

http://www.teksoftbluemusic.com/index.php?section=faq
[OnePlus 2 Original Android Development] _undead:
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

What's working

• Boots

• RIL

• VoLTE

• Wi-Fi

• GPS

• Hotspot

• Bluetooth

• Video Playback

• Camera/Video Recording

• Audio

• Sensors

• LED

• Alert Slider

• Screen-off Gestures

• WFD

• ADB Debugging

• SELinux Enforced

• Safetynet

Known issues

• You tell me

Installation Instructions

• Download the build and reboot to recovery

• Wipe system, data and cache

• Install the ROM

• Reboot

Notes:

• For Gapps, flash Nikgapps, Omni or Macro recommended.

• No support will be provided for above mentioned packages.

• Stock LOS is the default kernel.

Reporting Bugs

• You can grab logs via adb, any logcat reader app (matlog recommeded, now available on Play Store).

• DO NOT report bugs if you are not running stock kernel/have any magisk modules or flashing any addon zip.

Downloads

Click Here

Special Mentions

• Akash Shetty

• Wmbruckner

• Schrodinger's cat

• Sarthak

• Pierre

• rBen

These guys helped by testing multiple builds and reporting with useful logs when needed.

• rBen for donating his OnePlus 2.

• SGCMarkus for the help.

• Abhishek Tiwari for the VoLTE fix.

• Abhishek Tiwari and Gagan Malvi for the mm-pp-daemon fix.

XDA:DevDB Information

[ROM][UNOFFICIAL][R]LineageOS 18.1 for OnePlus 2 | Android 11, ROM for the OnePlus 2

Contributors

_undead

Source Code

Device Tree: https://github.com/mukul2259/device_oneplus_oneplus2/

Common Tree: https://github.com/mukul2259/device_oppo_common

Kernel: https://github.com/mukul2259/kernel_oneplus_msm8994

Vendor: https://github.com/mukul2259/proprietary_vendor_oneplus

ROM OS Version: Android 11

ROM Kernel: Linux 3.10.x

Based On: LineageOS

Version Information

Status: Stable
[OnePlus 2 Original Android Development] _undead:
Reserved

RIL Control App (Data Workaround)

https://sourceforge.net/projects/mukul2259/files/oneplus2/R/Ril_Control.apk/download
[OnePlus 2 Original Android Development] _undead:
Reserved
[OnePlus 2 Original Android Development] Vishal Gharat1:
Nice work undead👍👍👍
[OnePlus 2 Original Android Development] nelson pansare:
Keeping the Phone alive.... Respect bro..
[OnePlus 2 Original Android Development] aggtanishq1:
@_undeed in some places in OP you have mentioned android 10 instead of android 11

BTW really happy to see your efforts
[OnePlus 2 Original Android Development] _undead:
:highfive:

It's because XDA doesn't have Android 11 option yet. :fingers-crossed:

It is a hair-pulling yet a good experience to work with a legacy device and push it to the limits.
[OnePlus 2 Original Android Development] aggtanishq1:
Still nice efforts and waiting for the ROM to become a stable one and will surely switch
[OnePlus 2 Original Android Development] Oswald Boelcke:
That's affirmative - and there won't obviously be one in future as all DevDB threads will be reverted to "normal" threads eventually. Please refer to Big Changes To XDA Forums are Coming Soon:

However, you can manually edit to Android 11. Just don't use the option "Edit project" but edit the OP (only available in Style XDA 2015); please refer to attached screenshot.
[OnePlus 2 Original Android Development] _undead:
Thanks for the info Oswald.
[OnePlus 2 Original Android Development] tarkzim:
Hey [MENTION=4867044]_undead[/MENTION] , If you don't mind you can check my Z5 R builds and sources.

Since the hardware is pretty similar to OP2, for lagging issues check this one.

I hope it will help you and your work here, Cheers!
[OnePlus 2 Original Android Development] _undead:
Hello there!

Glad to see your response. I have already set that in the build I posted, not sure why it is happening.

The response is much appreciated! If you want, you can join our OnePlus 2 Discord server, bringing the best for both devices together because of the hardware.

Cheers!
[OnePlus 2 Original Android Development] toscha42:
Just installed LoS 18.0. Yes, a bit laggy here and there some force closes as well. But that was known so no complaints. :) But apart from that it works quite nice. Btw, I used FlameGapps and they work fine as well.

Not rooted yet, first need to find the Magisk Canary builds.

All in all a great work!

Cheers

Toscha
[OnePlus 2 Original Android Development] aggtanishq1:
Please include some screenshots
[OnePlus 2 Original Android Development] anirajkumar:
Thank you for your efforts bros. There are bugs as you mentioned, and it keeps crashing, Hope to get a stable version soon. Cheers!
[OnePlus 2 Original Android Development] rihan_shawn:
That's a very good news for oneplus 2 users. I'm so happy to have Android 11 on my oneplus 2 phone. as you said there's bug and restart issues. but that's a very good project for Us. keep going and make Oneplus 2 Undead. Great work.
[OnePlus 2 Original Android Development] vinko1950:
Man, thank you for keeping our phone alive for so long.

My last flashed ROM is RR 7.0.2 (rolled out on 22.04.2019. haha), but I will flash this one when it becomes stable af.

Fk it, I was lazy with flashing new stuff.
[OnePlus 2 Original Android Development] Custom Romer:
Pls develop more Android 11 (R) Roms For The
[OnePlus 2 Original Android Development] mincaeuro:
Hi are there any news regarding this ?
[OnePlus 2 Original Android Development] gorenvebanac:
This would be super helpful. i'm using op2 as my main phone so i can't risk using the alpha :(
[OnePlus 2 Original Android Development] _undead:
Hopefully, soon!
[OnePlus 2 Original Android Development] _undead:
Thanks.

As stated, I tried to implement a different fix for camera in the latest test build but it didn't do anything apparently.

You can customize what hardware keys do in the settings. I will try to implement a "swap" button.

Yes, ignore those. OP2 is pretty old and I didn't sign using a private key yet.

Mobile data issue is gone, as confirmed by others.

The translation was pretty accurate btw.

All the test builds were enforcing.
[OnePlus 2 Original Android Development] _undead:
Hello everyone,

Uploaded a new build with re-added fix for camera and mobile data together. Check and let me know!

Filename: lineage-18.1-20211018-UNOFFICIAL-oneplus2.zip

Cheers!
[OnePlus 2 Original Android Development] Jaiwantn:
Thanks for your time in building for this device......

sorry to mention this: the camera issue is still not yet resolved

anyone who tried this, pls confirm whether camera issue and mobile data issue is working fine for u or not?

and btw @_undead.... u did not update the last updated date in that one...starting of this thread ( I don't know what to call that as...sorry)
[OnePlus 2 Original Android Development] Aequita:
I can second this.

Dirty-flashed the recommended build and the camera-issue persists.

(still can't test mobile data tho)
[OnePlus 2 Original Android Development] PhatUgly:
Hey @_undead, thank you so much for keeping our devices up to date! I am looking to change over from the official aviraxp build some time soon.

Would it be possible for you to enable signature spoofing to allow the use of microg in your builds?

You can find the patch here: https://github.com/lineageos4microg...ofing_patches/android_frameworks_base-R.patch
[OnePlus 2 Original Android Development] _undead:
Because it was a test build, not a release build

Will check it out

Will do, thanks
[OnePlus 2 Original Android Development] FastJack2:
Can confirm data toggle works in latest 18th) build, but camera gives instant black-screen. Not even takes a second as previous builds.

If you could fix that issue it would be absolutely the best daily driver! Amazing work so far!
[OnePlus 2 Original Android Development] I<Aow:
I can use my camera so far. Build 18_10_2021 Don't know how long but long enough to take one or two photos. I flashed this version today and will test around and see if the microphone bug (sometimes the microphone does not work, this disappears after a reboot) appears again.
[OnePlus 2 Original Android Development] _undead:
Just an update,

I've been trying to incorporate both the fixes into a single build, but it doesn't seem to be going well.

Our blobs in general are too old. There are two separate workarounds for the Data Issue and Camera issue, individually adding them make the respective thing work fine, while adding them into a single build just breaks the camera. Back to square zero.

I'll try to workaround the data issue (I have an idea). Let's see how that goes. Until then, please flash the build for whatsoever is more important for your daily needs.

Until then, you can use RIL Control app on the build with camera working, so that data fixes without having to reboot your phone everytime. Do note that this app needs root. Link: https://sourceforge.net/projects/mukul2259/files/oneplus2/R/Ril_Control.apk/download

Cheers!
[OnePlus 2 Original Android Development] Jaiwantn:
@_undead R u staying in India only know.(I am saying by seeing ur profile, it is mentioned that u r from Chandigarh)

At what time will u sleep and wake....u r posting a message at 3:47 am......very hard working man.....Good luck for ur upcoming builds and work....
[OnePlus 2 Original Android Development] _undead:
Yes, I am in India. It's just that my sleep schedule is off. Thanks.
[OnePlus 2 Original Android Development] I<Aow:
OK, I take this back. I experienced the camera bug several times. Especially if the phone is busy and if I wanna read a QR Code. But also sometimes without heavy load.
[OnePlus 2 Original Android Development] AACLSM:
Hi,

I confirm good working Camera for the "Camera Build" - though RIL App doesn't work reliable - at least

here in Switzerland. But with this it's to live for for me... :)

Stupid question: I can't find anymore the real Camera Pictures I can see it on the phone, but in DCIM/Camera is only a small/few KB jpg.datafile which can't be opened (-"corrupt") on my Computer :-(

Where to dig..?

Thanks in advance for any hint and help....