Note:- Credits To this guide goes to {Diablosss}
GUIDE FOR UNLOCKING BOOTLOADER OF MEIZU PRO 7
(Sorry for the inconvenience, but there are some issues in posting pictures. Therefore requesting you to please check the attached files for images)
This guide can also work with many other Meizu devices. Checked on 15, 16 all options (s, t, x) and on Pro7I post the archive and instructions in pictures.
Step 1: Download. Unpack. Run meizublunlocker.exe
meizublunlocker:-https://drive.google.com/open?id=1yEm_vZo4rsqEtii279AU6l1mBajiSPQ2
See Image 1 in Attachments.
Step 2:-We connect the phone to the computer in fastboot mode (hold down the Vol. Down and power buttons), click refresh. The program must identify the device.
See Image 2 in Attachments.
Step 3ress CheckBL to check bootloader status.
See Image 3 in Attachments.
Step 4:-Click the Create Request button. This will create a file with the end of req.dat in the folder with this program
We send it to the e-mail [email protected] and wait for the response file to unlock the bootloader.
(This takes usually 1 week to receive the unlocked file, but you can donate to get the file within 3 hours)
See Image 4 in Attachments.
Step 5:- After we received the unlock file with the end of res.dat, click UnlockBL and select the resulting file.
See Image 5 in Attachments.
If the file is correct then get this answer
See Image 6 in Attachments.
That's It. We successfully Unlocked the Bootloader.
Now the next thing is to install the TWRP in our Device. ( Further credits goes to{ sergpolov} )
Step 1: Download and install "adb_run"
adb run:-https://drive.google.com/open?id=1y4wdL53-P7mybKsj5XeimHRoMSpokMkQ
Step 2:- Download the required Files.
Stock Recovery Pro 7:-https://drive.google.com/open?id=1e2tRdqLi5jsT8J854RMcIA-jvZyR7xhT
Twrp Pro 7:-https://drive.google.com/open?id=1uYOT9HGractYuoJvRidgAgh8IBLhzFtu
Step 3:-We load the phone into fastboot mode, flash through the fastboot the recovery you need.
Launch the application shortcut
Step 4:-Click "3" - go to fastboot mode
See Image 7 in Attachments.
Step 5:-Click "3" - recovery
See Image 8 in Attachments.
Step 6:-Here we select the recovery file: - in the window that opens, we throw the file itself and close the window with the file and press any button.
See Image 9 in Attachments.
The process has begun.
See Image 10 in Attachments.
Step 7:- Choose "Y" and "Enter"
See Image 11 in Attachments.
The recovery firmware process is over!
Next Few Steps are Extremely Important , so follow with caution!Step 8:-Reboot into Recovery Mode(hold down "Power" and hold, as soon as the screen goes blank, hold down the second button "Volume +" - hold it until vibration and release "Power", and after it release the button "Volume +")
Step 9:-To disable encryption of the "Data" section (who installs TWRP), we immediately flash the zip archive - tool-root_unlock-Testing-Pro7.zip
(disables encryption of the "Data" section, disables Boot and Recovery checks, installs Magisk and disables system root) and reboot into the system.)
tool-root_unlock-Testing-Pro7.zip:-https://drive.google.com/open?id=1a3Gyyuoo2Jv3EN7EWPwj389tXorSwkxT
Attention ! When installing custom recovery (TWRP) on your device, for the full TWRP functionality, you should format the internal memory (Data section) of the device using TWRP itself, since the "Data" section on Meizu smartphones is encrypted, I highly recommend it before installing custom recovery , on creating backups using the internal Flyme firmware (after creating the backup, it is located in the "backup" folder of the internal drive), as well as copying all the necessary data from the phone’s internal memory to the computer!
NOTE:-No One shall be responsible to any damage ocurring to your device
Doubts and queries are welcomed .
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
XRed_CubeX said:
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
Click to expand...
Click to collapse
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
adityadhage said:
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
Click to expand...
Click to collapse
But then for other MTKs like M5C it will never work?
XRed_CubeX said:
But then for other MTKs like M5C it will never work?
Click to expand...
Click to collapse
i know you have already tried this method with your device and it didnt worked. I am not sure that m5c will get another method in future or not. Bcoz we also got lucky with pro 7 that it got successful by the help of guide ported from Meizu 16TH a Qualcomm device.
its now per donation only.
spiramedia said:
its now per donation only.
Click to expand...
Click to collapse
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
cris2d2 said:
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
Click to expand...
Click to collapse
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
adityadhage said:
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
Click to expand...
Click to collapse
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
cris2d2 said:
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
Click to expand...
Click to collapse
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
adityadhage said:
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
Click to expand...
Click to collapse
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
cris2d2 said:
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
Click to expand...
Click to collapse
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
adityadhage said:
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
Click to expand...
Click to collapse
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
cris2d2 said:
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
Click to expand...
Click to collapse
basically you are right
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
deathbreath2010 said:
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
Click to expand...
Click to collapse
this guide is now updated and guranteed to work with x30 also
follow this
https://www.youtube.com/watch?v=Rnuf-uNBnYA&t=319s
adityadhage said:
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
Click to expand...
Click to collapse
its not 5$ its now 15$ its too mutch
sajib_ngage said:
its not 5$ its now 15$ its too mutch
Click to expand...
Click to collapse
try asking them for lower price, they will help u i think. Tell them its for pro 7 bcoz pro 7 requires less work. try ur luck
Related
Introduction
This is aimed to be a complete but simple guide for users which want to know what works in the Treble-World on the Mate 10 Pro and 'how to get there', based on other guides and my own findings
Disclaimer: I am not responsible for what you do with your device, you are free, probably old enough to know what you are doing and intelligent enough to read this through.
For the moment I will only speak about my own tests on a BLA L29 as I don't have the possibility to test everything.
Feel free to share your own discoveries via PM (just reuse the same formatting to make things easy)
Requirement
1. PC/Laptop running Windows 10 with adb and fastboot drivers installed
2. Original Huawei USB Type-C Cable
3. Being able to read and use search when a question arises
Summary
0. General Information
I. Unlock the Bootloader
II. Choose your ROM (a.k.a "What works on what")
III. Install your ROM
IV. Miscellaneous / Secondary stuff
V. Bonus : What to do if I am stuck / Bootlooping
0. General Information
To make things easier for everybody, here are some basic informations about your device and some common knowledge :
How do I get in Download / Bootloader / Fastboot Mode ?
Shut down your device, insert your USB cable. Keep the Volume DOWN button pressed and press the Power button, wait.
PRO TIPP : You may also get there from within android, first enable ADB debugging in developer options, then, on your PC open a command prompt and type "adb reboot-bootloader"
How do I get in Recovery Mode ?
While in Download / Bootloader / Fastboot Mode, take the USB cable out, keep the Volume UP button pressed and press the Power button until the phone reboots.
I. Unlock the Bootloader
We allready have a thread by @otonieru perfectly discussing this point, don't forget the Windows 10 fix :
https://forum.xda-developers.com/mate-10/how-to/how-to-huawei-mate-10-pro-standard-t3709535
II. Choose your ROM (a.k.a "What works on what")
This section isn't complete and should be detailed with time. None of these ROMs is specific for the Mate 10 Pro, but thanks to Treble, most images will work. Device-specific modifications are still needed in future, ask your local dev
1. Generic AOSP (Android 8.0 and 8.1) by Phhusson
Link : https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Description : Really basic ROM (basically pure AOSP) which serves as a basis for most of the other ROMs.
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk, Signal strength is reported incorrectly, error message at each start, Play Store tends to hang (solution : wipe the Play Store from recents or force close it)
Actual status : Barebones, can be customized in some ways with overlays.
2. LineageOS 15.1 (Android 8.1) by LuK1337
Link : https://forum.xda-developers.com/honor-view-10/development/rom-lineageos-15-1-t3753000
Description : If you don't know LineageOS, you should have heard about CyanogenMod (CM). This is a super clean, customizable version of Android, based on AOSP
What's working : Everything basic
What's not working : VoLTE, SuperSU and Magisk (system crashes), Signal strength is reported incorrectly,
root works thanks to addon-su (see Miscellaneous)
Actual status : Working as a daily driver (at least in my case) if you can live with some very small drawbacks.
III. Install your ROM
Once you have unlocked your Bootloader and chosen the ROM your heart desires follow these steps :
1. BACK UP YOUR DATA ! -> You will certainly have to do a factory reset and backing up data should be something natural when flashing something on your phone, even before updates.
2. Download the ROM (latest is probably best, but it's best to read what is said in the respective threads before jumping in the hole.
3. Reboot to the Download / Bootloader / Fastboot Mode (see above)
4. Flash the ROM by opening a command prompt and typing :
Code:
fastboot flash system system.img
where "system.img" is the filename of the ROM you downloaded
5. Reboot the phone by typing :
Code:
fastboot reboot
6. The phone will probably get in a bootloop. Don't panic. This should be normal.
After 4-5 reboot the phone will go in Recovery mode. Make a Factory Reset
7. Reboot
8. Profit
IV. Miscellaneous / Device-Specific stuff
This is probably the more interesting part as it is quite hard to find the correct information for our device concerning these points.
Root
ROMs as Lineage don't come prerooted. To root your phone the only viable solution seems to be addon-su for the moment.
To install you will need to install TWRP (follow the instructions in this link by @Dees_Troy : https://forum.xda-developers.com/mate-10/development/recovery-twrp-3-2-1-0-touch-recovery-t3752399 ), boot to TWRP (same as booting to Recovery, as TWRP is the new Recovery). go to advanced -> adb sideload. Connect your phone to your PC and flash the file using
Code:
adb sideload addonsu-15.1-arm64.zip
finally reboot, go to 'developer options' and chose the desired option under 'root options'. Done.
Camera
When flashing a ROM it will probably come with the stock AOSP or Lineage camera which, just say it, sucks on our device form a quality point of view. Here are the answers found to this problem for the moment. Sadly, there isn't one solution which works for everything and everyone.
Google Camera - GCam
Photos work - Gallery works - Videos don't work
Right now his is probably the best compromise if you want something that works, easy to install, while not wanting every little gimmick (in that case you should probably stay on EMUI - The definition of gimmick). Simply install the apk.
Note : there are probably other versions of GCam that work or will work in future, feel free to inform me / us about better working versions.
Link : https://drive.google.com/file/d/1Rw2lXtSHvOUalpA8YKg_kW2Xj_Gu746M/view
More information / discussion :
https://forum.xda-developers.com/mate-10/help/gcam-mod-mate-10-t3729078
Camera Port from the Mate 9 - needs root
Photos work - Videos don't work - Gallery doesn't work - Most filters and gimmicks work
A bit more complicated to install. The easiest way found for now is to root first using addon-su and then copy the system folder inside this zip into the respective folders using a root enables explorer like solid explorer
Link : https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI
More information / discussion : https://forum.xda-developers.com/pr...huawei-stock-camera-app-treble-roms-t3735169/
V. Bonus : What to do if I am stuck / Bootlooping
Remember when I said to back up ? Well I hope you did, because if you are really bootlooped and a reflash of the system image hasn't helped. you will have to reflash the whole device, which isn't quick.
Gladly @mankindtv has got you covered with his great guide : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I hope I could help a bit. Feel free to add your own findings, simply PM me.
Credits -
@otonieru for the great Bootloader unlocking thread
@phhusson for his many efforts to make Treble awesome
@LuK1337 for his many efforts to get things working on the Lineage side as well as for addon-su
@Dees_Troy for his awesome work on TWRP
@mankindtw for his great guide on recovering from the loops of boots
reserved
It's gonna be one of the most helpful threads for the novices.
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
If possible, please add how to go back to stock rom in simplified form.
mdjishadk said:
It's gonna be one of the most helpful threads for the novices.
Click to expand...
Click to collapse
I have lost three days to get out of bootloops and gather the info... I hope nobody else will have to live the same thing (and maybe this can become a dedicated thread to fix the last missing blocks to have a complete experience)
good job
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
good job on this one OP btw, video on mate 9 camera port is only broken on 8.1, on 8.0 all camera features work fine except opening of the picture from the camera app itself
Good job man!
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It might be android 8.1. It worked fine for me when using 20180225 version, didn't test later ones.
What version are you on?
Gryphie said:
You can also root Lineageos with magisk. I did it and it works.
https://forum.xda-developers.com/mate-10/how-to/root-huawei-mate-10-pro-magisk-twrp-t3753956
Click to expand...
Click to collapse
It crashed everything on my 8.1 build (and the developer himself recommended me addon-su) maybe a tad harder to use, but at least you learn something at the same time
You should add that the stereo speakers don't work.
Timate5 said:
You should add that the stereo speakers don't work.
Click to expand...
Click to collapse
"Stereo"... When coming from a Nexus 6P this Sally doesn't sound stereo at all... But you're right !
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
timo.helfer said:
Android Auto doesn't work also on these ROMs. Phone says its incompatible because of some OMX codec issues
Click to expand...
Click to collapse
That's too bad, android auto uses h264 streaming codec I think. I think this issue will have something to do with hardware acceleration. Have you tried messing around with the acceleration option found in the developer options to see if it might work?
Nice guide! Thank you @ChriKn!
Can you add to the "Generic AOSP (Android 8.0 and 8.1) by Phhusson"'s part that we need to use A-ONLY version of this rom?
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
ChriKn said:
I will try as soon as I have my PC.
Sad news, I got a good opportunity on a Pixel 2 XL and sold my Mate 10 Pro (I need my Pure Android AND Quality Camera)
Does someone want to take the thread over ?
Click to expand...
Click to collapse
Sure i can write some impressions. I just installed Carbon ROM.
I did flash but is not booting at all.
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
triconix555 said:
Hello, I did everything as mentioned. And phone is not booting it just bootloops.
i can't do a reset is sends me directly back to recovery and just ask to reboot or shutdown phone...
What do I have to do ?
Can i go to stock rom again ?
Thanks
Click to expand...
Click to collapse
Let it Bootloop until it goes to erecovery and than factory reset it
Timate5 said:
Let it Bootloop until it goes to erecovery and than factory reset it
Click to expand...
Click to collapse
I did that but it is just boolooping again, I did all tge steos over and over and it just bootloops every tipe even after factory resete, it actualy asked le once to resete since then after a couole of reboots it goes straight to te erecovery, wherz it ask to login on a wifi to download latest bootloader and rom or reboot or shutdown device...
Hi,
I just happened to google how to unlock Nokia 7 Plus' bootloader again and stumbled upon this site:
[Guide] How to unlock the bootloader on Nokia Android Phones for free
Detailed guide to help you unlock the bootloader of your Nokia Android device. You can unlock bootloader on many Nokia smartphones, including Nokia 7 Plus, Nokia 8, Nokia 8 Sirocco, Nokia 8.1, Nokia 7, Nokia 6, Nokia 6.1, Nokia 5, Nokia 2, Nokia 2.1. etc.
www.techmesto.com
It was updated today with a free way to generate bootloader unlock keys for Nokia 7 Plus apparently. Now I can't test this myself at the moment (in a week at earliest), but do you think this is legit?
At least I can generate a code apparently, so this part is actually free.
Hello,
has anyone tried this unlocker, because I'd like to use it, but since I use my nokia 7 plus as my primary phone I'd like to have some confirmations before using it
I use my Nokia 7 Plus as primary phone as well, but I guess I'll just risk it
However, I can't promise anything here. Hopefully I will get around to it within the coming week.
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Thanks for the useful infos.
I suppose I will unlock my phone in the upcomming months but right now I just factory resetted it and it's working almost nicely.
I really want to unlock and flash a custom rom on my phone, because the stock rom it's buggy and tends to have some performance issues, but right now if I mess with it I can't afford to change the phone so I guess I'll have to wait.
Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Do you have any tips on flashing TWRP? Thanks!
I have unlocked bootloader, tried to install TWRP from https://twrp.me/nokia/nokia7plus.html
fastboot flash recovery twrp.img
Output:
target reported max download size of 402653184 bytes
sending 'recovery' (42644 KB)...
OKAY [ 1.274s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.298s
GenericAsianGuy said:
Do you have any tips on flashing TWRP? Thanks!
Click to expand...
Click to collapse
Yeah, the tutorials seem to be a little outdated...
In general, follow this guide here (its from the same person that created the official twrp.me site I believe):
[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx |
Note - Iam Not Responsible for bricked devices About Team win recovery project TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who...
forum.xda-developers.com
I wasn't sure if I have a OOB or POB device, but I haven't had any issues using both (currently using OOB since I'm pretty sure my Nokia 7 Plus is that old )
Secondly, what the instruction somehow failed to mention is how to get the install.zip. It is on their sourceforge page in a subfolder:
B2N_sprout - Browse /TWRP-TEN/OOB at SourceForge.net
sourceforge.net
This is for the OOB variant, you can replace OOB at the end with POB to get the other files
You can verify, that I'm sending you the right link by following the links from the forum post to download the image to boot from. For example:
https://sourceforge.net/projects/b2n-sprout/files/TWRP-TEN/POB/twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download
Now you can just remove the "twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download" part of the URL and you get to the folder where all the other images are located. Download the latest "twrp-installer-*.zip" for your device and install it.
Znert said:
Yeah, the tutorials seem to be a little outdated...
In general, follow this guide here (its from the same person that created the official twrp.me site I believe):
[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx |
Note - Iam Not Responsible for bricked devices About Team win recovery project TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who...
forum.xda-developers.com
I wasn't sure if I have a OOB or POB device, but I haven't had any issues using both (currently using OOB since I'm pretty sure my Nokia 7 Plus is that old )
Secondly, what the instruction somehow failed to mention is how to get the install.zip. It is on their sourceforge page in a subfolder:
B2N_sprout - Browse /TWRP-TEN/OOB at SourceForge.net
sourceforge.net
This is for the OOB variant, you can replace OOB at the end with POB to get the other files
You can verify, that I'm sending you the right link by following the links from the forum post to download the image to boot from. For example:
https://sourceforge.net/projects/b2n-sprout/files/TWRP-TEN/POB/twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download
Now you can just remove the "twrp-3.4.0-0-B2N_sprout-POB-10.0-20200829.img/download" part of the URL and you get to the folder where all the other images are located. Download the latest "twrp-installer-*.zip" for your device and install it.
Click to expand...
Click to collapse
This is great, thank you so much! I can also boot from both OOB and POB, will try this out later today
EDIT: worked like a charm. Thanks again!
Great! Glad I could help!
Hi @Znert, did you use TWRP for Android 10 or Android 11?
Another question: can I unlock the bootloader of a Nokia 7+ on Android 10?
Thank you again.
Radder124 said:
Hi @Znert, did you use TWRP for Android 10 or Android 11?
Another question: can I unlock the bootloader of a Nokia 7+ on Android 10?
Thank you again.
Click to expand...
Click to collapse
I use the Android 10 version, but I'm not sure what the difference is anyways (it's a bootloader, shouldn't that be OS independent?)
Regarding your second question, yes, I unlocked my bootloader with the latest official stock ROM (so Android 10).
Yes that's what I thought also... Maybe we need to use the Android 11 version to install a Android 11 ROM.
Now I see there is a new version of TWRP 3.5.2 on the official website.
Znert said:
I tried it yesterday and it work flawlessly.
Just follow the steps on the page, I had no issues unlocking the bootloader.
That being said, I nearly bricked my device when trying to flash Lineage OS onto it (because all TWRP and Lineage OS step by step guides seem to be out of date?), but this guide helped me get back to stock: https://forum.xda-developers.com/t/...m-flash-tool-nokia-7-plus-b2n_sprout.4023961/
Might keep it handy if you are like me
Click to expand...
Click to collapse
Can you tell me, has unlocking bootloader deleted your apps and data?
In my experience with every older fone, it does format it, but i wanna make sure.
Thanks in advance!
ghost baby said:
Can you tell me, has unlocking bootloader deleted your apps and data?
In my experience with every older fone, it does format it, but i wanna make sure.
Thanks in advance!
Click to expand...
Click to collapse
Yes, unlocking the bootloader will wipe your phone. As far as I know, this is true for all Android phones.
Deleted
Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Download
Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Download
Click to expand...
Click to collapse
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.
Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors
coffeemakerexpress said:
Thank you for the reply.
However I believe that this is what I did do when I set up the phone with the ROMs.
I still tried to do it exactly as you explained, however this did not work.
I got into a bootloop after flashing firmware through fastboot, even if I cleaned the data using recovery. I tried the Recovery version of the firmware and this worked fine so after that I followed your tutorial just as you described.
This still didn't work, when booted into the Custom ROM the touch screen was still not working at all.
In the meanwhile I found this blog-post:
lemon – Encik Kunci
Posts about lemon written by Encik Kunci
encikkunci.wordpress.com
Where he states and I quote: "Phones with nt36672d display isn’t supported yet." this was posted August 11, 2021.
I don't know who he is or how he knows that.
I am pretty sure it's a kernel problem or firmware or something, regarding the screen being NVT-ts and probably the "nt36672d" variant.
This makes me very sad.
Click to expand...
Click to collapse
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.
superdragonpt said:
Its indeed an kernel issue, there's ( at least) two screen revisions from two different vendors
Click to expand...
Click to collapse
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
Atanassoww said:
I found this in 4pda:
Quote a reply: Yes, I had the same thing. By the way, if we are talking about OrangeFox recovery, which did not start at all, then it was necessary to use a newer version, I found a link to a google drive on the xda forum, it did not start there.
And on the touch, I also tried 2 custom firmware on them, everything started, but the touch did not work in principle. Only on off or lightweight everyone and on xiaomi.eu worked. I suppose the same case, but I can refine it when the phone is sent back.
ps: Due to freezes and rebots - in the service they changed the motherboard in the end, I'm waiting for the parcel now.
Click to expand...
Click to collapse
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.
coffeemakerexpress said:
I see, so my assumption was correct. Thank you for clarifying.
Do you know how often Xiaomi (or if they will at all) release firmware/kernel source codes, and do you know if custom kernel makers/Custom ROM makers, will actually update their kernels/ROMs to use this in the future?
And is there a way/place for me to keep updated on if Xiaomi releases the needed firmware/sourcecode for this display, so that I can ask ROM makers/Kernel makers nicely to add the firmware, assuming they don't know about this issue?
So you have the same problem? I'm not sure I understand what you mean here, aside from the touchscreen not working for you either due to this weird display model.
Click to expand...
Click to collapse
Yes or is not Supported right now..
This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
coffeemakerexpress said:
This is just a small update with a possible fix that I haven't tried yet because I'm tired of flashing ROMs all day, I will try it later if I get the motivation to do so. I post this because someone else might have the energy to test this themselves. If I test this I will update this post with an edit or bump this thread.
I Found on a forum called 4PDA where a user by the name "Void_dp" talks about a Xiaomi Redmi 9T with a nt36672d display. The forum is in Russian, but use a translator if you are interested. It is the post this url links to:
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки - 4PDA
Xiaomi Redmi 9T / Redmi Note 9 4G - Неофициальные прошивки
4pda.to
I do not know if the website itself or this user is trustworthy or correct, so try this with caution and I am not responsible for anything you decide to do or happens to you or your computer, or phone.
In short he explains that crDroid 7.9 (7.10 is the current version, and is the one I tried) use a different kernel than the Stormbreaker kernel than crDroid 7.10 uses.
He says if you have crDroid 7.10 installed you have to format data before trying this.
1. Download crDroid 7.9 and crDroid 7.10
2. Get the "boot.img" from the crDroid 7.9 rom and extract it
3. Open the zip file for crDroid 7.10 (do not extract anything) and replace the "boot.img" (7.10 version) with the one you just extracted (7.9 version)
4. Do a clean flash with this modified ROM you just made.
That is all he said, but if it doesn't work my first thought is to try the original crDroid 7.9 rom, if you don't care about running the latest update. This is probably not smart in relation to security patches and stuff like that. I take no responsibility for whatever happens.
Additional information:
I checked the Changelog for the crDroid roms, and they changed the kernel from "Optimus Drunk kernel 11.0" to "Stormbreaker" when they upgraded their ROMs version from 7.9 to 7.10.
I tried using the "Optimus Drunk kernel 11.1" kernel in my trial and error with the ROMs without luck, so I will try to flash some roms together with the "Optimus Drunk kernel 11.0" if I can find it.
Link to crDroid ROM for Redmi 9t:
crDroid.net - Download crDroid for supported devices
official crDroid ROM website
crdroid.net
Click to expand...
Click to collapse
I DIDN't work for me, I got a bootloop, maybe it will work for u
hamid_dabouz said:
I DIDN't work for me, I got a bootloop, maybe it will work for u
Click to expand...
Click to collapse
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?
coffeemakerexpress said:
Thats sad to hear, this phone is a nightmare. I haven't tried this yet, maybe I will try this weekend.
I'm wondering though, did you FORMAT data after flashing?
By bootloop, which of these do you mean:
That it never enters the "loading phase" of the OS (Android/rom splash screen)
That it gets stuck and restarts in the "loading phase" of the OS (Android/rom splash screen)
That it just kicks you to recovery/fastboot over and over again, without showing the OS loading screen
Or something else?
Click to expand...
Click to collapse
Ohh Jeesus...
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)
hamid_dabouz said:
Thank you for respond, But i already flashed Two versions of " stormbreaker"kernel one of them worked but the touch is going insane, if you clicked on somewhere on the screen it will respond in other place of the screen ( i hope you understand what i'm saying)
Click to expand...
Click to collapse
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Atanassoww said:
Ohh Jeesus...
Click to expand...
Click to collapse
Why that reaction? I am here to learn and try to solve my problem, if you have any advice please elaborate on why what I said was wrong or dumb so I won't make the same mistake again.
superdragonpt said:
OK I just got my t9, and started the BL unlock, unfortunately I still need to wait ~ 1 week.
So I can't do testing at the moment
My unit has this very same touch screen, so seems I will likely have this same issue in the future.
I took a look at the kernel source provided by Xiaomi ( android 10 only)
And this touch variant isn't there in the defconfig
since the same kernel is used by 4 devices ( including t9, poco m3,etc )
I took the opportunity to check the few custom kernels that already exist for poco M3, and you guys should definitely try the poco m3 " stormbreaker" kernel, since it includes more TP drivers and the correct loading of both Novatek's TP drivers firmware
Cheers
Click to expand...
Click to collapse
I will maybe try the Stormbreaker kernel for Poco M3 this weekend as well then to check it out.
superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Thank you for this informative answer, do I take it as this is something you will look into? If I can help by using adb or something, to get information from my phone just tell me what to do.
superdragonpt said:
Oh i see...
Well since the weekly MIUI EU a11 ROMs seems to work alright ( as per the users feedback) , perhaps this can be easily fixed.
Just a matter of extracting from those android 11 kernel the DTB, and convert dtb to dts and the touch firmware loading binary and fix the kernel entries.
Assuming that the tp driver is the same or similar, and the issue is just the firmware blob and DTS
Let's see
Cheers
Click to expand...
Click to collapse
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.
I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....
coffeemakerexpress said:
Is this the extract you were talking about? It has the firmware for the touchscreens and everything for android 11. but it is for the Chinese version, so I don't know if that matters.
redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
qssi-user 11 RKQ1.201004.002 V12.0.3.0.RJQCNXM release-keys - redmi_lime_dump/vendor/firmware at qssi-user-11-RKQ1.201004.002-V12.0.3.0.RJQCNXM-release-keys · PythonDevelopers/redmi_lime_dump
github.com
I don't know if this is relevant but I thought I would share it since I found it. Someone smarter than me can maybe use it to make the touchscreen work.
Click to expand...
Click to collapse
coffeemakerexpress said:
Hello.
I have been trying to get a custom rom flashed on my Redmi 9T the past two days.
The problem I am facing is that the touch screen is not responsive with the flashed ROMs that I have tried.
ROMs I have tried:
PixelPlusUI_3.9_juice-11.0-20210912-1736-OFFICIAL
LegionOS-v3.13-juice-20210922-OFFICIAL-GAPPS
Arrow-v11.0-juice-COMMUNITY-20210809-GAPPS
crDroidAndroid-11.0-20210927-juice-v7.10
What did make the touch screen work was to flash "boot.img" from one of the android 11 builds of MIUI such as "xiaomi.eu_multi_HMNote94G_HM9T_POCOM3_21.9.8_v12-11" or "xiaomi.eu_multi_HMNote94G_HM9T_POCO_M3_21.5.27_v12-11" after flashing the custom ROM, but this resulted in "Sytem UI" crashing and wifi not working. There were probably other things that didn't work but I can't have a phone without WiFi so this was not a solution for me.
After looking into what "boot.img" contains, it seems like it contains the kernel and other important system related components.I then tried to flash the following kernels over a new install of the custom ROMs "crDroid" and "PixelPlusUI 3.9":
StormBreaker-lime-r3-0909-0545
CartelProject-lime-BETA-20210915-07
Optimus_Drunk_Citrus_v11.1
But they did not help with getting the touch screen to work.
I also tried a combination of a "boot.img" from an offical android 11 EU MIUI ROM and these three kernels in the hope that I would keep the touch screen fix from "boot.img" and get wifi from the kernels, however every time the kernel was flashed the touch screen stopped working.
This leads me to believe the kernel itself makes the touch screen not work, and other things from the "boot.img" make the WiFi stop working.
So I have a few questions I hope someone can answer:
When do you think Xiaomi will release the source-code for the android 11 kernels that they use in their new MIUI ROMs? As I don't know their release cycles.
When will the firmware for the NVT-ts touchscreen version of Redmi 9T be added to custom kernels?
Is there a way for me to extract the Android 11 MIUI kernel from "boot.img" and flash ONLY that, if that fixes my touchscreen and does not break my WiFi? (If this is legal/allowed/possible)
I don't know anything about android development so if I am wrong please correct me.
Thank you in advance.
Click to expand...
Click to collapse
Atanassoww said:
1.Download an official firmware, boot your device into your Fastboot Mode with Power+Volume Down Button connect your device to your pc and launch the flash_all.bat
When the flash is completed go to the Stock Recovery with Power Button+Volume Up Button, clean the data and wait your device to boot. When your device booted setting it up and enable USB Debugging from the Developer Tools.
2. Now boot your device to Fastboot Mode using Power Button+Volume Down and try to Flash TWRP or OrangeFOX.
3. Boot your device into Recovery using Power Button+Volume Up
4. Now make a CLEAN FLASH:
Format Data
Flash latest MIUI Weekly
Flash ROM zip
Flash Gapps (for Vanilla build)
Format Data
Reboot System,
Enjoy!
MIUI Weekly Firmware (Lime):Download
Fastboot Firmware tgz:Downl
Click to expand...
Click to collapse
bogteo said:
I fix dt2w on Xtended custom rom. Replace kernel and flash Magisk extension. I don.t try others roms....
Click to expand...
Click to collapse
Please can you explain more ?
I tried with crdroid 7.9 without success. still cannot use the touchscreen
m210j19sy I began with global miui rom
I've collected all files necessary to root and recover (if necessary) the OnePlus 10 Pro with Android 13 Update - NE2211_11_C.21
( Firmware pulled from Oxygen Updater App)
Please note: Root at your own risk.
I'm not liable for any bricked device or issues possibly created from this process.
Stock Boot.zip
magisk_patched-NE2215_11_C.21.zip
Magisk-25.2.apk
stock.recovery.zip
NE2215_11_C.21 Stable (full).zip
Feel free to follow along using this guide:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!
If flashing/rooting errors out, and you end up in Qualcomm Crash Dump Mode, please perform the following:
Restart into Fastboot Mode by holding Volume Down + Power buttons until the device vibrates, then release only the power button
Once in Fastboot mode, try flashing a clean boot and recovery to BOTH slots like this :
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Follow the steps on this site to Flash the stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
If you have trouble rebooting to FastbootD (Recovery)
Try swapping Active slots from the application (typically slot A worked for me)
Choose reboot to FastbootD
Sorry if this is a stupid question, but is this to be used when the OP 10 Pro is ALREADY on OS 13, or is this to be used when the unit is on OS 12 (not yet rooted) and you want to take it to OS 13?
Thanks for your help.
Either or would be fine.
It's an upgrade using a full OTA update.
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
eren15935 said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Not yet, but once I find one I'll upload it ASAP for the community.
Savio Dantes said:
Not yet, but once I find one I'll upload it ASAP for the community.
Click to expand...
Click to collapse
thanks. It would be nice. good work.
Hi there, do you have for C.22?
Savio Dantes said:
Not yet, but once I find one I'll upload it ASAP for the community.
Click to expand...
Click to collapse
There is...check this out
(Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
Please note, the TWRP image used IS NOT the official TWRP image. I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me. Warning As stated by @beatbreakee , do not flash...
forum.xda-developers.com
(Guide) Install TWRP + Root + Install Magisk + Bypass Safetynet
Please note, the TWRP image used IS NOT the official TWRP image. I am not responsible for any any harm, such as bricking, or bootloops, which may happen to your device. This is what worked for me. Warning As stated by @beatbreakee , do not flash...
forum.xda-developers.com
eren15935 said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
linhdanstore said:
Hi. Is there any oneplus 10 pro compatible twrp? I could not find.
Click to expand...
Click to collapse
Literally look above.
Savio Dantes said:
I've collected all files necessary to root and recover (if necessary) the OnePlus 10 Pro with Android 13 Update - NE2211_11_C.21
( Firmware pulled from Oxygen Updater App)
Please note: Root at your own risk.
I'm not liable for any bricked device or issues possibly created from this process.
Stock Boot.zip
magisk_patched-NE2215_11_C.21.zip
Magisk-25.2.apk
stock.recovery.zip
NE2215_11_C.21 Stable (full).zip
Feel free to follow along using this guide:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and others too!
Click to expand...
Click to collapse
Can you use ADB tools to restore stock rom if the device was soft bricked?
No. There are a few unbricking tools I've had to use in the past such as MSM tool, Fastboot Enhance Tool, and payload Dumper. (Google them, they're easy to find)
Note, that MSM tools are (nowadays) typically created and coded with a specific device and may also require authentication to unlock.
I've since moved on to the Google Pixel Pro series after seeing the terrible "Franekstien Project" that Oppo applied to Oneplus in their Color OS "make files"... It's literally a "lucky" mash-up of OnePlus Legacy OS and Oppo.
When companies sell out like that, do lazy transitions, etc. and the core reason we supported them in the first place becomes both forgotten and obsolete, that's when I typically stop supporting them.
Savio Dantes said:
No. There are a few unbricking tools I've had to use in the past such as MSM tool, Fastboot Enhance Tool, and payload Dumper. (Google them, they're easy to find)
Note, that MSM tools are (nowadays) typically created and coded with a specific device and may also require authentication to unlock.
I've since moved on to the Google Pixel Pro series after seeing the terrible "Franekstien Project" that Oppo applied to Oneplus in their Color OS "make files"... It's literally a "lucky" mash-up of OnePlus Legacy OS and Oppo.
When companies sell out like that, do lazy transitions, etc. and the core reason we supported them becomes forgotten, an obsolete, after which I typically stop supporting them.
Click to expand...
Click to collapse
Just to clarify does fastboot enhance tool and/or payload dumper works with restoring stock rom?
SKNIZZY said:
Just to clarify does fastboot enhance tool and/or payload dumper works with restoring stock rom?
Click to expand...
Click to collapse
Yes it does.
Fastboot enhance works fine, you need to remove the cow files first and have a valid payload.bin but that's it
Install LineageOS 20 on SM-T290 and SM-T295 with Google Apps (MindTheGapps)
* Your warranty is now void. (It might already been)
* I am not responsible for any damage that it may do to your device. I WARNED YOU
* It's your choice to do it. Not mine. I just made it as I wanted to do it, but you have the choice to do so. If you choose to do it, you know that it may have consequences.
Click to expand...
Click to collapse
WARNING! This won't work on a bootloader with version U4! Flashing won't work and so you will not be able to use this guide. Unfortunately, you can also currently not downgrade the bootloader, making it impossible to get any custom stuff (custom recovery, custom ROM, etc.) on your device...
Hello there! This is another guide from me here on XDA Developers! Today, I will show you how to install LineageOS 20 on an SM-T290 and SM-T295, and yes, it works on both! Let's get started:
PrerequisitesBut first, make sure you have all of this:
An SM-T290 or SM-T295 tablet
TWRP (v3.7.0 recommended for SM-T290 and v3.5.2 for SM-T295)
Unlocked bootloader
1. Download LineageOS 20 ZIP from here (There stands it is for gtowifi, but it also works on the LTE model).
2. Choose the nightly build for the ZIP, it is very stable even though it is nightly.
3. OPTIONAL BUT I DO NOT RECOMMEND: You could also choose the recovery, but that's more like the stock recovery and I recommend you to keep TWRP as it has better features.
4. Download the ZIP that has the format 'lineage-20.0-YYYYMMDD-nightly-gtowifi-signed.zip'
- OPTIONAL: Download the recovery image for LineageOS 20 with the format 'lineage-20.0-YYYYMMDD-recovery-gtowifi.img'.
5. Download MindTheGapps from here.
6. Choose the one with the format 'MindTheGapps-13.0.0-arm64-YYYYMMDD_BBBBBB.zip'
7. Follow the links to download the ZIP file.
8. Place the LineageOS and MindTheGapps ZIP to an SD card or USB drive. If you choose to also take LineageOS recovery, you will also need to place the .IMG to an SD card or USB drive.
9. Insert the SD card or USB drive into your tablet.
10. Boot the device into TWRP.
11. Go to 'Wipe' > 'Swipe to Wipe'.
12. Then go once again to 'Wipe' > 'Format data' > 'Swipe to format'.
13. Go to install, make sure that it is not install image but as flash ZIP!
14. Use the select storage button to choose the storage where the ZIPs are saved.
15. Choose the LineageOS 20 ZIP and swipe to install.
16. Wait until it is done and now install MindTheGapps.
17. Optional step (depending on whether you have the following things):
- Install Magisk (root) ZIP if you have it. You could also do this later on.
- Install LineageOS recovery ZIP if you have chosen to use it. This can also be done later.
17. Click on 'Reboot system' or go to 'Reboot' > 'System'.
18. Wait until the boot is done.
19. Go through the setup, but WAIT! First read the step below.
20. Depending on whether you have LineageOS recovery or TWRP, you need to enable the option 'Auto-update LineageOS Recovery/LOS Recovery' in the setup if you have LineageOS/LOS Recovery and disable that if you have TWRP.
21. Once the setup completed, you are done!
That was easy to follow. Thank you.
Heeni said:
That was easy to follow. Thank you.
Click to expand...
Click to collapse
No problem!
Heeni said:
That was easy to follow. Thank you.
Click to expand...
Click to collapse
Nice. Guess you have LineageOS 20 right now.
Minionguyjpro said:
Nice. Guess you have LineageOS 20 right now.
Click to expand...
Click to collapse
Yes. I was previously running a GSI, but I like this better.
I'm not using Gapps, so I just skipped para. 16. I did install Magisk.
Does OTA update work with TWRP, or only with Lineage recovery?
Heeni said:
Yes. I was previously running a GSI, but I like this better.
I'm not using Gapps, so I just skipped para. 16. I did install Magisk.
Does OTA update work with TWRP, or only with Lineage recovery?
Click to expand...
Click to collapse
It does work with TWRP. It uses an OpenRecoveryScript. If you have Gapps (which you don't have), you need to reflash them afterwards. Also Magisk needs to be reflashed, but it is much easier to do than the stock!
How does this tablet with LineageOS work now?
Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
dequadim said:
How does this tablet with LineageOS work now? Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
Click to expand...
Click to collapse
I'm not sure, but it has some good features though. Some parts are a bit buggy, but most are not. It's also much faster.
Hello, thank you for the installation guide. Used my T290 and everything was working perfectly fine... I then decided to use LineageOS for MicroG and also everything ist working...
LineageOS 20 for MicroG:
gtowifi
My other SM-T295 is now on Bootloader5 (T295XXS5CWA1) so I think there is no way anymore to get LineageOS 20 on it. I now ordered a "new" SM-T295, which is supposed to be on Android 9. When I use the Guide above, is the cellular modul and LTE working with the CustomRom? Or should I use the GSI? Why is it such a different between those two devices?
SGX22 said:
Hello, thank you for the installation guide. Used my T290 and everything was working perfectly fine... I then decided to use LineageOS for MicroG and also everything ist working...
LineageOS 20 for MicroG:
gtowifi
My other SM-T295 is now on Bootloader5 (T295XXS5CWA1) so I think there is no way anymore to get LineageOS 20 on it. I now ordered a "new" SM-T295, which is supposed to be on Android 9. When I use the Guide above, is the cellular modul and LTE working with the CustomRom? Or should I use the GSI? Why is it such a different between those two devices?
Click to expand...
Click to collapse
Hello there! LTE will not be included, but you have 2 workarounds:
Make a hotspot over Wi-Fi with your phone or any other SIM device
Use the GSI ROM, which may have support
Well, LTE doesn't work, because of this: LineageOS is made on base of the drivers and packages of the device. And, they are almost the same I think, that's why the other stuff will or should work. But, the SM-T295 also has a driver and/or package for the SIM, LTE and so. And because it was originally made for the SM-T290, instead of an SM-T295, it will not include those drivers and so the support for it. You could try a GSI, although I had issues with it. But I may have done it wrong or so.., I always say: if there is an official custom ROM, use that over GSI, because it was really made for the device and includes the drivers and packages for the device. Although I don't really know whether GSI is bad, it may also work correctly..., if you try GSI, and it doesn't work, you could take a look at this: https://forum.xda-developers.com/t/gsi-lte-fix.3925151/
dequadim said:
How does this tablet with LineageOS work now?
Has it become more responsive than the original Samsung ROM or does it continue to suffer from the same exasperating slowness that characterized it?
Click to expand...
Click to collapse
In my opinion it is much faster and very responsive. It is really an improvement!
SGX22 said:
In my opinion it is much faster and very responsive. It is really an improvement!
Click to expand...
Click to collapse
Well, I will install it as soon as I can.
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
nima2005com said:
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
Click to expand...
Click to collapse
That's I think because your bootloader version is 4 or higher, instead of 3..., this updates after an update, and it can also not be downgraded for now. Bootloader version 3 has not got this protection that disallows flashing custom things like TWRP. Bootloader version 4 and higher do have...
Minionguyjpro said:
That's I think because your bootloader version is 4 or higher, instead of 3..., this updates after an update, and it can also not be downgraded for now. Bootloader version 3 has not got this protection that disallows flashing custom things like TWRP. Bootloader version 4 and higher do have...
Click to expand...
Click to collapse
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
nima2005com said:
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
Click to expand...
Click to collapse
Note: as i experienced you cant install Twrp on android 10 bootloader 3
nima2005com said:
I flashed TWRP on my T295 But unfortunately i got this eroor SECURE CHECK FAIL : recovery.img)
Click to expand...
Click to collapse
You can repair it quickly. Please search on youtube.
Deleted, need to search some further to make sure it is correct...
nima2005com said:
ok i haved installed this rom on T295 Android 9 Bootloader 3 And everything works .Thanks for making this awesome rom . the only bug i noticed is low brightness . i think oneui max brightness was higher than this rom
Click to expand...
Click to collapse
Hello, I ordered a "new" T295 with Android 10, but it is T295XXU4BUD3 as well, like my old T295. Is there still no way to get LineageOS on it.
I must say I am very disappointed now. I tried so many things bought 3!!! Devices.. It is just to much work to get LineageOS on a tablet. Is there any (small Tablet) that I can put LineageOS on with LTE which is working. Man, I am trying this for 2 years now..... What about Sony Tablets?
SGX22 said:
Hello, I ordered a "new" T295 with Android 10, but it is T295XXU4BUD3 as well, like my old T295. Is there still no way to get LineageOS on it.
I must say I am very disappointed now. I tried so many things bought 3!!! Devices.. It is just to much work to get LineageOS on a tablet. Is there any (small Tablet) that I can put LineageOS on with LTE which is working. Man, I am trying this for 2 years now..... What about Sony Tablets?
Click to expand...
Click to collapse
Well, an old Samsung Galaxy Tab 4 with LineageOS 18.1 (Android 11). I helped someone today to get it on his device! It was very easy to do, so.