Database Develop

[TOOLKIT][FLASHER]Desire C Toolk!t v1.5(25/04/13)[Recovery/Kernel/Root/Bootloader]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Presenting to You
HTC DESIRE C TOOLK!T by TeKnoGin
DISCLAIMER
Code:
[FONT="Century Gothic"]* TheRedHunter has not only tested the tool but has confirmed that it is working. (POST 2)
So first of all a big thanks to him for taking the risk and testing the toolkit.
* I am not responsible if your device gets bricked or something
happens so I recommend that you get a stock rom ready.
* You will need an Unlocked Bootloader which means you have
already void your warranty. [URL="http://forum.xda-developers.com/showthread.php?p=40690862"]If you haven't unlocked it yet then here is a guide[/URL][/FONT]
Code:
[FONT="Century Gothic"]The toolkit provides the user (basically new users) to flash Recoveries and
Kernels (even ROMs which will be updated soon) to your DESIRE C.
# The update v1.5 will also provide users with two new features that is ***unlocking bootloader***
(giving you the oem unlock code) and ***rooting your device***
[SIZE="5"][COLOR="DarkGreen"]Desire C Toolk!t v1.0[/COLOR][/SIZE]
# Flashing Custom Recoveries:-
> ClockWorkMod Recovery 6.0.3.0 (TOUCH) by mehmehmen [URL="http://forum.xda-developers.com/showthread.php?t=2231101"]LINK HERE[/URL]
> ClockWorkMod Recovery Stable by mmmcfc [URL="http://forum.xda-developers.com/showthread.php?t=1785010"]LINK HERE[/URL]
> ClockWorkMod Recovery 5.5.0.4 (TOUCH) by munjeni [URL="http://forum.xda-developers.com/showthread.php?t=1829649"]LINK HERE[/URL]
> TWRP Recovery 2.5.0.0 by nikhil16242 [URL="http://forum.xda-developers.com/showthread.php?t=2148015"]LINK HERE[/URL]
> Your Own Recovery Whichever You Want (if you have any new one please
tell me too)
# Flashing Custom Kernels
> Prometheus Kernel by nikhil16242 [URL="http://forum.xda-developers.com/showthread.php?t=2192750"]LINK HERE[/URL]
> Your Own Desired Kernel[/FONT]
[SIZE="5"][COLOR="DarkGreen"]Desire C Toolk!t v1.5[/COLOR][/SIZE]
# Rooting your phone
> Root your Desire C with just a click. Rooting process uses [URL="http://www.modaco.com/topic/355158-r1-superboot-how-to-root-the-htc-desire-c/"]Superboot[/URL]
to get root access and then provide permanent root to the users.
> Unlock Bootloader [OPENS THE LINK] (BY THE WAY HERE IS A GUIDE TOO:-
[URL="http://forum.xda-developers.com/showthread.php?p=40690862"]http://forum.xda-developers.com/showthread.php?p=40690862[/URL])
Code:
[FONT="Century Gothic"]
# * Extract the "toolkit_desire_c.zip" to somewhere like Desktop.
* Connect your Desire C with USB Debugging Enabled.
* Run "recovery.bat".
* Select your Desired Option.
* Just wait.......
# *To Flash Your Own Desired RECOVERY or KERNEL [COLOR="Red"]
+ Make sure you rename your recovery to ****recovery.img**** (without starsigns)
and place it in the "own" folder and then select option 7.
+ Make sure you rename your kernel (img file) to ****boot.img**** (without starsigns)
and place it in the "own folder " and then select option 6.[/COLOR][/FONT]
Code:
[FONT="Century Gothic"] Mirrors will be coming soon till then no mirrors please....
[SIZE="4"][COLOR="DarkGreen"]Desire C ToolK!t v 1.0[/COLOR][/SIZE]
# Skydrive:- [URL="http://sdrv.ms/13swfZ6"]http://sdrv.ms/13swfZ6[/URL][COLOR="Red"]{COMPATIBLE with all COMPRESSION SOFTWARE
thnx to [URL="http://forum.xda-developers.com/member.php?u=5091745"]noahvt[/URL]}[/COLOR]
# Dev-Host:- [URL="http://d-h.st/cuR"]http://d-h.st/cuR[/URL]
[SIZE="4"][COLOR="DarkGreen"]Desire C ToolK!t v 1.5[/COLOR][/SIZE]
# Skydrive:- [URL="http://sdrv.ms/17Z1nTE"]http://sdrv.ms/17Z1nTE[/URL]
# Dev-Host:- [URL="http://d-h.st/N92"]http://d-h.st/N92[/URL]
[/FONT]
​

Nice tool, I'll test it as soon as I'll be home.
Edit: Your toolkit works like a charm. This is the easiest way to flash kernels/recoveries I've ever used.

Doesn't work: unknown compression method in winrar,winzip and standard windows extraction program!

TheRedHunter said:
Nice tool, I'll test it as soon as I'll be home.
Click to expand...
Click to collapse
Thnx Man Report here asap whether it is working or not??
Just try and test each one.

noahvt said:
Doesn't work: unknown compression method in winrar,winzip and standard windows extraction program!
Click to expand...
Click to collapse
Try it with 7-zip.
I compressed it using 7-zip.....
btw i'll see to make it work with winzip, winrar and other compression software.

Update
I'll update a compressed version which will be compatible with all compression software soon.
Edit: UPDATED

Huston we've got a problem. It's something wrong with my port...but what is the connection between a port and a recovery flash ?4
Problem solved, thank you.

Solution
Here is a fix to that problem.
http://themikmik.com/showthread.php?15885-ADB-Server-didn-t-Ack-Error-SOLVED
Run the batch file ....TRY IT.....
Download it here:- http://sdrv.ms/14MRGJ8
there are two reasons for this error:-
1. when no device is connected
2. when HTCSyncManager.exe is already using adb servers

Worked like a charm, thank you very much! :good:

FusionX3 said:
Worked like a charm, thank you very much! :good:
Click to expand...
Click to collapse
Happy to Help

I tried to install the Prometheus kernel too now. It wrote Writing Successful but when the phone tries to boot it's stuck at the white HTC screen with the red text (This build is for development purposes only ...). What should I do?
EDIT: I tried to restore to a previous backup, I tried to install a custom ROM I had on my SD Card, none of that worked.

FusionX3 said:
I tried to install the Prometheus kernel too now. It wrote Writing Successful but when the phone tries to boot it's stuck at the white HTC screen with the red text (This build is for development purposes only ...). What should I do?
EDIT: I tried to restore to a previous backup, I tried to install a custom ROM I had on my SD Card, none of that worked.
Click to expand...
Click to collapse
But thats working with my phone......
I tried installing Prometheus Kernel and it was successful....
Try installing the kernel manually.
1. Switch Off your phone and then boot into fastboot mode.
2. Connect your phone to the computer.
3. Open a command prompt in the "tools" folder.
4. Run the following command
"fastboot flash boot boot.img" (without quotes)
5. restart your phone with this command
"fastboot restart"
Tell me whether that worked or not.
Taking the case of the backup or flashing the ROM which recovery did you flashed???
I would recommend you to flash the CWM 6.0.3.0 TOUCH recovery which doesn't till now has a bug.
For this repeat the steps in this post and instead of step 4 just run the following command:
"fastboot flash recovery recovery_touch_6_0_3_0.img"
Then try to flash the ROM.
If it says "Install from sdcard failed" or something like that then retry downloading the ROM.
If nothing works then try FLASHING STOCK ROM...
Edit: How can a restore fail ? What error does it show? Did you change the recovery? Are the recoveries different i.e. the one with which you backed up and the one which you are trying to restore????

TeKnoGin said:
But thats working with my phone......
I tried installing Prometheus Kernel and it was successful....
Try installing the kernel manually.
1. Switch Off your phone and then boot into fastboot mode.
2. Connect your phone to the computer.
3. Open a command prompt in the "tools" folder.
4. Run the following command
"fastboot flash boot boot.img" (without quotes)
5. restart your phone with this command
"fastboot restart"
Tell me whether that worked or not.
Taking the case of the backup or flashing the ROM which recovery did you flashed???
I would recommend you to flash the CWM 6.0.3.0 TOUCH recovery which doesn't till now has a bug.
For this repeat the steps in this post and instead of step 4 just run the following command:
"fastboot flash recovery recovery_touch_6_0_3_0.img"
Then try to flash the ROM.
If it says "Install from sdcard failed" or something like that then retry downloading the ROM.
If nothing works then try FLASHING STOCK ROM...
Edit: How can a restore fail ? What error does it show? Did you change the recovery? Are the recoveries different i.e. the one with which you backed up and the one which you are trying to restore????
Click to expand...
Click to collapse
I resolved the problem. I installed the smallest version (700) of the Prometheus kernel, and that worked.

[GUIDE] Gain Root Access v3 (3 Methods!)

Hello people,
This is for Mi Note Pro (leo)
Disclaimer:
I'm not responsible for any devices being bricked, your device blowing up or world war 3 starting! You are doing this at your own risk.
Click to expand...
Click to collapse
A lot of people ask how to gain root on the Mi Note Pro without actually searching the posts so I decided to make a quick tutorial on how to do it. This is the way I have done it and I have found it to be the easiest way!
1st Method (THE EASIEST AND SAFEST!)
1. Go to http://en.miui.com/download-273.html and download the Developer ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. If you have downloaded the file through your phone it will be in the Download folder, if not plug your phone into the PC and move the .zip file over to your device.
3. Open Updater app, tap on 3 dots to open the menu and tap on Choose update package
4. Navigate to where you have put in the zip file and click on it and let the phone update. (This will wipe all your data apart from pictures etc.)
5. Once it has loaded go through the setup. Open Security app > Permissions > Root Access.. There you are all done
Make sure you open an app that requires root access first before going to Security app as it will not show up on there.
2nd Method (Advanced Users!)(Temporary TWRP Recovery)
Requirements:
fastboot driver (Link attached)
twrp.img - https://mega.nz/#!nR0jHZqL!2cksl ... 5H76ut8UVtnu97HHAEo
supersu - https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
common sense
mi note pro!
1. First of all download all the things you need. Which are fastboot driver, twrp and supersu. All links are above ^ Copy SuperSu over to your device and keep other files on your PC
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3. Woohoo great now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Extract the TWRP zip so you have just the .img file. Place it inside same folder as fastboot. I tend to rename it to twrp.img (makes lifes easier)
7. Type fastboot boot twrp.img
8. Now your phone should boot into TWRP!! Go to install and flash the SuperSU zip.
9. Reboot and you are all rooted with Stock Recovery and Stable ROM!
3rd Method (Advanced Users!)(Permanent TWRP Recovery)
Requirements:
fastboot driver
twrp.img - https://mega.nz/#!nR0jHZqL!2ckslQxV-ODWnswRYpfDCp2M5H76ut8UVtnu97HHAEo
supersu - https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
common sense
mi note pro!
1. First of all download all the things you need. Which are fastboot driver, twrp and supersu. All links are above ^ Copy SuperSu over to your device and keep other files on your PC
2. Power off your device and turn it back on by holding Power button and Volume Down at the same time. This will get you into fastboot menu.
3.Woohoo great now what you will have to do is plug your phone to your PC using a usb cable.
4. Open up the Command Promt and navigate to the location of your fastboot driver. Mine is C:/adb so I would type cd C:/adb in the command promt
5. Now type in fastboot devices just to make sure that your device is listed correctly.
6. Extract the TWRP zip so you have just the .img file. Place it inside same folder as fastboot. I tend to rename it to twrp.img (makes lifes easier)
7. Type fastboot flash recovery twrp.img
8. Now your phone should boot into TWRP!! Go to install and flash the SuperSU zip.
9. Reboot and you are all rooted with TWRP recovery, the only problem is that your OTA updates will break. You can flash them manually, when Updater downloads an update go into TWRP>Install and navigate to downloaded_rom folder
In case you need to go back to stock Recovery because you have flashed TWRP Permanently please follow instructions on this thread.http://en.miui.com/thread-124319-1-1.html

GREAT! EASY!
Need to wipe cache or data?

Nope no need to do that

nice thanks for the advice

I followed ur step but no show root access...
Did I miss anything?

Absent6775 said:
I followed ur step but no show root access...
Did I miss anything?
Click to expand...
Click to collapse
Yea step 5

Absent6775 said:
I followed ur step but no show root access...
Did I miss anything?
Click to expand...
Click to collapse
Well their Root Access works a bit different to SuperSU instead of popping up with a box promting you to give root access what you have to do is open the app the requires root access, do an action that needs root access then you go to Security > Premissions > Root Access and you have to grant it then.

Is only way to root to do a full wipe?
Can we still do normal updates after installing this developer rom?

Yup you get newest weekly updates and they work perfectly fine! I'm on 5.7.2 currently

Updated.

Is it equally safe to flash the latest 1.0.0 supersu from chainfire? Is there any compatibility constraints? or are all version compatible with all devices? thanks for shedding some light into this

Can you use Flashify and install twrp and supersu or is supersu not needed using method 1? ?
sent from mobile thingy

Super su is not needed using method 1 as they use their own root manager.

Kahun said:
Super su is not needed using method 1 as they use their own root manager.
Click to expand...
Click to collapse
How to unroot in method 2 ?
Incase I want to sell this phone so the warranty still valid to the new owner.

deddo86 said:
How to unroot in method 2 ?
Incase I want to sell this phone so the warranty still valid to the new owner.
Click to expand...
Click to collapse
Just flash stable ROM.

Added a permanent recovery method but "might" break OTA

Problem with Method 1
Hi People /Mr. Kahun ,
I'm absolutely new but i would like to root my :
Mi Note Pro
Android 5.0.2.
MIUI 66.55.44.00
because some original programs make me creasy . I tried method 1. I followed your steps, i downloaded different DEVELOPER Rom (5.9.10 and 5.9.17) , but i had always with the step 4 the message GETTING INFO ..... and this is the end of the process .....
PLEASE PLEASE tell ma what can i do to root the device .
Thank you in advance

Try installing HappyMIUI rom from the android development section.

i don't know how to install .....i will try method 2.
thank you Kahun!

where can i find the fastboot driver (Link is NOT attached)

[Android 11] Unofficial Lineage OS 18.1 for A21s

WARNING + DISCLAIMER:
By installing this custom ROM, you are VOIDING your warranty. Also, installation of this ROM WILL TRIP KNOX PERMANENTLY, and render apps such as Samsung Health, Private Folder, (+ any apps that depend on KNOX) useless until you get the phone's motherboard replaced at the Samsung C/S center.
Although this software is released in the hope that it will be useful, there is NO GUARANTEE that installing this will not cause any harm to your device. I TAKE NO RESPONSIBILITY FOR ANY BRICKED DEVICES, DAMAGED HARDWARE, OR ANY OTHER PROBLEMS CAUSED BY THIS ROM. You are using this ROM at YOUR OWN RISK. I strongly recommend that you DO NOT continue to the steps below UNLESS YOU FULLY UNDERSTAND WHAT YOU ARE DOING.
While this ROM has been tested with South Korean variant of Galaxy A21s (SM-A217N, CSC changed from LUC->SKC), please keep in mind that it hasn't been tested on any other variant (such as A217F, A217M.)
Click to expand...
Click to collapse
I would like to express special thanks to all the developers who contributed to the LineageOS port for Galaxy Tab S6 Lite + all the other developers who contributed to sepolicy & hardware parts for Samsung SLSI (Exynos) devices. Porting LineageOS to A21s would have been much harder without them.
Click to expand...
Click to collapse
After doing some research on this device, I was able to port LineageOS. The original sources are based on Galaxy Tab S6 Lite Wi-Fi version (gta4xlwifi), with some heavy modifications made for the A21s. In the process, I was able to fix some of the problems that were found on GSI (MTP, Fingerprint removal issues, NFC, Wi-Fi hotspot and direct), and added in some enhancements to the kernel.
Unfortunately, installation of this ROM requires Lineage Recovery, and since FBE (File-based-encryption) is enabled by default, it is incompatible with the TWRP.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOT WORKING:
- Cell Broadcast (Emergency Messages) is broken in South Korea. The phone shows notifications, but the messages appear broken. Not sure about other countries. FIXED in South Korea as of 2021/9/2. However, its functionality in other countries hasn't been tested.
- Samsung's Proprietary Apps
- In order to use Wi-Fi Direct, you need to install a Wi-Fi direct sharing app from Google Play, as LineageOS doesn't have a sharing app installed by default
- Auto Brightness (The phone doesn't have the sensors for it anyway)
- On very rare occasions(probably once in more than 20 boots), the device's RIL (Phone calls, Data) might start up late when booting. If you see "No service" after booting, please wait for 30-60 seconds.
- VoLTE & VoWifi(not tested) - Unfortunately, this is located deep within Samsung's framework. AOSP-based roms for other Samsung devices don't support it either. Someday, this might be fixed.....
WORKING:
- Everything Else
GITHUB:
Device Source Tree: android_device_samsung_a21s, android_device_samsung_universal3830-common
Kernel: android_kernel_samsung_universal3830-common
Instructions for Installation:
1. BEFORE INSTALLING, make sure that you have UNLOCKED the bootloader of your device. This is a great guide that show how to do it. Also, the phone must be on the Stock ANDROID 11. If you are on binary U6, please use the recovery tar for U6.
2. Download the Lineage Recovery, ROM, Google Apps, ADB, and Odin. Unzip ADB and Odin to somewhere appropriate.
- ROM
- Recovery / Recovery(for U6)
- Google Apps
- ADB
- Odin
3. Enable USB Debugging on the device. Go to settings->About phone->Software information, and tap the build number several times until you see the notification that the devloper settings have been enabled. After enabling developer settings, go to settings->developer settings and check USB debugging.
4. Open Command Prompt, and type "cd <the path where you saved ADB to>".
4-1. As a test, type "adb devices". After typing it, the phone should show a screen that asks you to grant permissions for USB debugging. Select Yes.
5. On the phone, start holding down the Volume Up and Down keys. KEEP THE KEYS PRESSED UNTIL THE PHONE REBOOTS AFTER YOU TYPE THE COMMAND IN THE NEXT STEP.
6. While holding the keys down. type in the command "adb reboot recovery" on the command line.
11. After the phone reboots into download mode, press volume up to continue. Make sure that you see the "OEM LOCK: OFF" before continuing.
12. Open Odin. After opening Odin, click on AP, and select the Lineage Recovery Tar file that you downloaded in the step 2. After that, click on Start.
13. After a few seconds, if everything goes well, Odin should show "PASS" and the device should reboot into Lineage Recovery. After the device enters recovery, tap on Apply update->Apply from ADB. In some cases, touchscreen may be unresponsive or slow. If that happens, use Volume Keys to navigate and Power key to select. KEEP THE DEVICE CONNECTED TO THE COMPUTER.
14. After choosing Apply from ADB, type "adb sideload <the path where you saved the ROM file>" on the command prompt and press enter.
<CONTINUED ON THE NEXT POST>

15. If everything goes right, the device should show "script succeeded: result was [1.000000]" While ADB may show errors such as "Failed to read command" at 47%, this is no problem as long as the device says that the script succeeded.
16. Now it is time to install Google apps. On the phone, tap on Apply from ADB again, and on the computer, type "adb sideload <the path where you saved Google apps to>" and press enter.
17. After about 1-2 minutes, installation should be complete. Again, ADB might show "Failed to read command" errors. As long as the phone says that it was success, this is no problem. After installing, click on the "back" icon shown below.
18. Choose Wipe data/factory reset, and reboot the device.
19. If everything went well, the phone should reboot into LineageOS. Set up the device and Enjoy!

ADDITIONAL TIP: HOW TO ROOT THE PHONE ON LINEAGE 18
On Lineage 18, I patched the kernel so that it would have no problem with the official Magisk app.
Therefore, you DON'T need to use a version that has been modified for A21s.
If you want to have root, you can get the Official Magisk App.
1. Download & Install Magisk from the official source.
2. Select Install. When it asks you to select the boot image, choose the boot image from the Lineage OS ROM file that you downloaded from the step above. After patching the boot image, move & rename it to something you can type easily (ex. /sdcard/rooting.img)
3. Enable developer settings (Settings->About phone->Tap on build number)
4. Go to developer settings and enable USB debugging & root permissions for usb debugging.
5. Connect the phone to the PC.
6. Open the command prompt, and type "cd <the folder where you installed adb>. After that, type "adb root". If the phone asks you for permissions for USB debugging, allow it.
7. After the adb shows "Restarting adbd as root", type "adb shell dd if=/sdcard/<the path to saved boot image>" of=/dev/block/by-name/boot". The output should be something like
" *** records in
*** records out
*** bytes (** M) copied, *** s, **M/s"
8. After seeing the output above, reboot the phone. After rebooting, it should be rooted.

Good news. Thank you very much

Then, my friends, write here how it works and thank you for your observations

Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc

Pharcanal40 said:
Thanks for your work buddy.....
I got Magisk installed an easier way...
Download Magisk Canary .apk
Change .apk to .zip then install the same way as the Rom and Gapps, by ADB sideload.
Factory reset/Format data and reboot.
Done
All we need is a working TWRP.... I've got one working but it shows no files and won't mount anything..... e.g. system, data etc
Click to expand...
Click to collapse
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..

Gxzllen said:
What is your device model ...is it SM A217F/DS android 11 U6? Pls reply..
Click to expand...
Click to collapse
A217F on U5

Pharcanal40 said:
A217F on U5
Click to expand...
Click to collapse
Can i download it on u6?i'm afraid my phone brick if i do it

Gxzllen said:
Can i download it on u6?i'm afraid my phone brick if i do it
Click to expand...
Click to collapse
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.

grccorps said:
If you're on U6, there's a chance that Odin might fail on vbmeta.
A possible solution is:
1. Download Magisk (version doesn't matter)
2. Download the U6 firmware that you're on
3. Using Magisk, patch the AP tar of U6 firmware
4. In the Lineage recovery tar file that you downloaded from above, replace the vbmeta.img with the one from Magisk-patched AP tar file
5. Proceed with the installation as written above
A more fail-safe method would be:
1. Root the phone using a patched Magisk app
2. unpack the recovery.img in the Lineage recovery tar file and copy it into your device's SD card
3. Enable USB debugging on the phone, and connect the phone to adb
4. Using command prompt, type
"cd <path to adb>"
"adb shell"
"su"
"dd if=/sdcard/<path to lineage recovery image> of=/dev/block/by-name/recovery"
"reboot recovery"
After typing these, your device will reboot into Lineage Recovery. After entering recovery, select apply update->apply from adb, and proceed with the installatiom above from Step 14.
Click to expand...
Click to collapse
nice thankyou bro

Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin

Pharcanal40 said:
Or you can extract just the boot.img from the AP.tar. Patch it in Magisk then repack in the AP and flash with Odin
Click to expand...
Click to collapse
Ohh okay its easy this way

Can I use adb fastboot instead of Odin?

Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Thank you for your review. It's such a great news that it's working on U6.
Yes, PUBG is a hell of a game, Krafton has done such a great job with it The kernel has newer mali graphics driver (R26P0 -> R31P0), maybe that could've done the trick (or it may just be due to LineageOS being much, much lighter than One UI)
How is the battery? While I wasn't able to find any abnormal battery drains (both in standby and stress conditions), I'm concered about how it would perform in other devices.

NuzzaimStark said:
Successfully Flashed! Everything work fine.
Model- A217f /DS
U6 binary ,Android 11 latest.
Note: Encountered some problems when I flash (vbmeta) ie, its because of its only for u5.
Odin showed failed at last ,
Phone was unable to boot but
By using hijacking software , bootloader was again running . but when auto reboot lineage recovery was automatically loaded, and tryed your above steps and everything working fine,
Note: pubg is very very better in this ROM.
Close range is also better.
Thankyou grccorps .
Click to expand...
Click to collapse
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exchange?

Phuc230204 said:
Can you be a little more specific? my phone U6 but idk how to flash recovery can or you give me email so i can exc(hange?
Click to expand...
Click to collapse
First look on A21s LineageOS 18.1

hi,so i get this message "only official released binaries are allowed''in download mode,after the vbmeta failed...
SM-A217F/DSN
and in frp hijacker i get ''check device connection or com ports''

Update:so i succeded to hijack my phone after the error but it wouldn't boot into recovery,and i got everytime a screen with a warning that my phone is not using samsung's official software,and when i press the power button to continue,like it shows,it boots automatically into android.
So what should i do?
And do i need root to do this?

[12] PixelExperience [OFFICIAL] [OnePlus8Pro] [ROM]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to @LuK1337,@chandra1.jd ,@hasaber8 for all OnePlus 8 Pro trees
Team PixelExperience
Device Supported
Oneplus 8 Pro only
Whats is working?
Everything
What's not working?
let me know
Installation Process:
-You need ADB and Fastboot
1. Sideload rom.zip from recovery
2. restart to system (no need of factory reset)
Flashing for 1st time
In some cases slot b can be unpopulated or contain much older firmware than slot a, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of slot a to slot b. This step is NOT optional. To do this, sideload the copy-partitions-20210323_1922.zip package by doing the following:
-Download the copy-partitions-20210323_1922.zip file.
-Sideload the copy-partitions-20210323_1922.zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload copy-partitions-20210323_1922.zip
Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”.
1. Download recovery provided here
2. Reboot to bootloader and flash recovery
Code:
fastboot flash recovery <recovery_filename>.img
fastboot reboot fastboot
fastboot flash --slot=all recovery recovery.img
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Down + Power.
Or
Code:
fastboot reboot recovery
3. Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
4. Sideload the PixelExperience .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
DOWNLOADS​DOWNLOAD LINKS BELOW:
ROM - Click here (Latest Build)
RECOVERY - click here
ROM (plus edition) - Click here (Latest Build)
RECOVERY - click here
SOURCE
Android version:
Security patch level: April 2022
Build author: jef00
Kernel Source: https://github.com/PixelExperience-Devices/kernel_oneplus_sm8250
ROM Source: https://github.com/PixelExperience

Welcome.

Great.
Will definitely give it a try.

Ijaz Farooq said:
Great.
Will definitely give it a try.
Click to expand...
Click to collapse
Nicee!

Running PE11 right now and waited for this ROM! Thank you!

This one have a working Face unlock feature?

lieblingsbesuch said:
Running PE11 right now and waited for this ROM! Thank you!
Click to expand...
Click to collapse
No problem!

vpclabs said:
This one have a working Face unlock feature?
Click to expand...
Click to collapse
yes it has it

Sorry a couple of questions, does this ROM have OOS camera (if not is there any way to add it ?) and is Google Photos Unlimited activated ??
aparently "https://github.com/Evolution-X/fram.../internal/util/evolution/PixelPropsUtils.java" is needed to get Unlimited working ( I honestly dont know anything about how to impliment it :-( )
Thanks

pantha007 said:
Sorry a couple of questions, does this ROM have OOS camera (if not is there any way to add it ?) and is Google Photos Unlimited activated ??
Thanks
Click to expand...
Click to collapse
Afaik gphotos unlimited is no more available.

lieblingsbesuch said:
Afaik gphotos unlimited is no more available.
Click to expand...
Click to collapse
It does work im on A11 with Pixelify Module and its sweet ( but Pixelify seems to not work nice with 12 for some reason the camera goes away lol), I hope this ROM has OOS Cam and Unlimited photos

pantha007 said:
Sorry a couple of questions, does this ROM have OOS camera (if not is there any way to add it ?) and is Google Photos Unlimited activated ??
aparently "https://github.com/Evolution-X/fram.../internal/util/evolution/PixelPropsUtils.java" is needed to get Unlimited working ( I honestly dont know anything about how to impliment it :-( )
Thanks
Click to expand...
Click to collapse
Google Photos is Unlimited yes, because Google Photos is mask to Pixel XL. No OOS camera because i wanted to stay close to the Oneplus 8T official release and it is a pain in the ass to port it.

jef_00 said:
Google Photos is Unlimited yes, because Google Photos is mask to Pixel XL. No OOS camera because i wanted to stay close to the Oneplus 8T official release and it is a pain in the ass to port it.
Click to expand...
Click to collapse
Thanks for your work

pantha007 said:
Thanks for your work
Click to expand...
Click to collapse
No thanks mate! :d

All good rom but very tiny and annoying issue that the display is not well cut. Like shown in pic. Not a hardware issue because it changes when goes to landscape.

jef_00 said:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
Click to expand...
Click to collapse
Hey @jef_00 I don't seem to find the option "Apply Update" on device. How do I get it to work? Or should I simply sideload using ADB command and that should suffice?

yzlnew said:
All good rom but very tiny and annoying issue that the display is not well cut. Like shown in pic. Not a hardware issue because it changes when goes to landscape.
Click to expand...
Click to collapse
Hi thans for letting me know i will fix it in the next build!

tahiriqbal said:
Hey @jef_00 I don't seem to find the option "Apply Update" on device. How do I get it to work? Or should I simply sideload using ADB command and that should suffice?
Click to expand...
Click to collapse
Hey mate dd you flash the recovery file? the option "Apply Update" is in the recovery and it is to sideload

jef_00 said:
Hey mate dd you flash the recovery file? the option "Apply Update" is in the recovery and it is to sideload
Click to expand...
Click to collapse
yes, i was eventually able to figure out. now i am stuck at phone setup screen. i am using the Last Pin but it says it is invalid, and I cannot receive 2-Step Verification code because I don't have career coverage. How do I now get past that?

tahiriqbal said:
yes, i was eventually able to figure out. now i am stuck at phone setup screen. i am using the Last Pin but it says it is invalid, and I cannot receive 2-Step Verification code because I don't have career coverage. How do I now get past that?
Click to expand...
Click to collapse
Did you a clean install?

How To Guide [GUIDE] XIAOMI.EU ROMs Flashing Guide All Devices [Linux-Only]

XIAOMI.EU ROMs Flashing Guide:
MIUI 13 (Stable)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
Your device's bootloader must be unlocked.
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Click to expand...
Click to collapse
Then go to your custom rom download thread and check the date of rom file.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of home directory and connect your device to fastboot mode and open terminal in stock rom folder and type command:
./flash_all.sh
The terminal will close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Follow flashing guide of twrp from here.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the .eu rom zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select eu rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to system.
Done.
Updating via Updater app: (ROM Type: Recovery)
(A Xiaomi.eu ROM must already be installed on your device)
Download Xiaomi.eu ROM zip file
Copy the ROM zip file to the internal storage
Updater -> Menu (...) -> Select update package
Select the ROM zip file
Confirm any dialogs
Done!
Installing with Fastboot: (ROM Type: Fastboot)
Download Xiaomi.eu ROM zip file
Extract the .eu ROM zip to root of home directory.
Connect device in fastboot to PC via USB cable
Open a terminal in the .eu rom folder.
Run the command:
./first_install_with_data_format.sh - with data wipe, if you're flashing Xiaomi.eu ROM for the first time or downgrading
./update_rom.sh - without data wipe, if you're updating from an older Xiaomi.eu ROM.
Done!
Remember:
If you are going from MIUI 13 (or later) Weekly ROM to MIUI 13 Stable ROM, you are doing a downgrade, so format data is mandatory!
MIUI 13 (Weekly)
Go to the sourceforge link of the rom and see the date of your rom. In this case it's alioth.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of home directory and connect your device to fastboot mode and open a terminal in the rom folder and run the command:
./flash_all.sh
A terminal window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Follow flashing guide of twrp from here.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the .eu rom zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select rom eu zip and flash.
Once flashing done , wipe dalvik.
Reboot to recovery.
Reboot to system.
Done.
Fastboot:
Unzip .eu rom file to root of home directory.
Go into folder.
Open terminal window in the folder
Run command:
./linux_fastboot_update_rom.sh(Data will be lost)
Done.
CHECK THE XIAOMI.EU THREAD FOR KNOWING IF YOUR ROM IS FASTBOOT OR RECOVERY.
NOTE FOR ALL:
Make sure to always extract and move the stock rom folder in root of home directory (this helps avoid flashing errors)The path should look something like this:
home\spes_global_images_YourVersionhere
Also make sure the same to unzip xiaomi.eu rom folder in the root of home directory:
home\xiaomi.eu_multi_HMNote11_YourVersionHere
Then flash Xiaomi.EU according to instructions above.
Alternatively If you want you can flash india , eea , turkey , etc variants of stock rom instead of global , then flash xiaomi.eu according to the instructions above. But keep in mind that the release date of stock rom that you are flashing should be closest to the release date of xiaomi.eu weekly rom.
Must do all the process again if flashing a new rom
If you get a error like this: assert failed _dynamic partitions package_extract_file(dynamic_partitions_op_list) ERROR 1
Then go to the guide here and re do all the steps in the guide and when it comes to flashing twrp, then use twrp 3.6.1 to flash rom then flash twrp 3.7.0 according to the process in guide (if the rom you flashed is a12) or use shrp 3.1 instead of using twrp after re doing all the steps and then flash rom.
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can cause problems such as reboots, apps crashing,etc as recovery is integrated into boot partition in which kernel is also integrated.

Thanks for not forgetting us linux folks.

pulsar said:
Thanks for not forgetting us linux folks.
Click to expand...
Click to collapse
long live linux ! windows is bs.