Database Develop

[TUT][HOW-TO] How to root Xiaomi Redmi2 and install CWM

ARE YOU SEARCHING TO ROOT YOUR REDMI 2 ?​
DISCLAIMER:​DO THIS ON YOUR OWN. I'M NOT RESPONSIBLE FOR ANYTHING HAPPENS TO YOU AND YOUR DEVICE.​PLEASE DONOT MIRROR THE LINKS​
CLICK HERE FOR NATIVE ROOT​
IF YOU ARE GETTING STOCK RECOVERY EVEN AFTER FLASHIN CWM, SEE THIS POST​
STEP 1- FLASHING CWM ON YOUR PHONE
1.At first, you'll need the "adb" and "fastboot" tools. Get them HERE
2.Extract them into a folder, let's name it "Redmi2" (You can give your own name to the folder. That doesn't matter here.)
3.Now get the CWM .img file from HERE
You can use Philz Touch recovery also. Get HERE
4.Rename cwm.img or philz.img you downloaded above and as "recovery.img" and place it in the Redmi2 folder.
Now the folder will look like this-
{
"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"
}
5.Press and hold "shift" button and right click in the blank area of the folder and click on "open command promt window here". The command prompt will open.
6.Now turn off your Redmi2. Wait until it vibrates. After it's vibrated press and hold "Volume down and Power" keys together until it boots into "fastboot mode". Now connect the Redmi2 to your PC/Laptop through USB cable in fastboot mode itself.
7.Get to the command prompt now.
Now type: " fastboot devices " (without these- " " )
Like this-
8.Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command
9.Now enter the next command: " fastboot flash recovery recovery.img "
Like this-
10. Now this ends...
Type the last command: " fastboot reboot "
Like this-
11.Now your phone will reboot with ClockWorkMod(CWM) installed. CHEERS...
STEP 2- ROOTING YOUR PHONE
1. Firstly get the SuperSU.zip from HERE
2. Now copy the downloaded zip to your sdcard (not in any folder just in sdcard)
3. Boot into CWM recovery by turning off the phone and pressing "Volume UP and Power" button together after the phone vibrates.
4. Once CWM main menu is displayed, select "Install from zip" and browse to the zip that you downloaded earlier and select it.
5. Install the zip. If you get any warning, ignore and proceed.
6. After the installation is complete, reboot your device. (I think you can do that)
7. VOILA..!!! YOU ROOTED YOUR REDMI2
PLEASE HIT THANKS​
JOIN OUR FACEBOOK GROUP HERE​
CREDITS:
1. I don't claim any credit for "adb and fastboot tools" and the "recovery.img" and "SuperSu.zip"
2. Thanks to @subhrajiNath on Miui english forums who wrote the original guides.
Thread link is here and here​

I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here

postadelmaga said:
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
Click to expand...
Click to collapse
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull

? not flashing ?
noobpremium said:
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
Click to expand...
Click to collapse
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )

postadelmaga said:
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
Click to expand...
Click to collapse
get "Flashify" app from playstore and first take backup of stock recovery and then flash the cwm with it. Thats it..
Actually I didn't knew this method before i made this guide..
Anyway, fastboot gives us a different feel, doesn't it? :v

wait I don't know flashify but it looks it needs root to flash the recovery ... but I think I need cwm to root ... so I think this is not gonna work ...
Ok got it, this may be useful to anybody face the issue with recovery:
I discovered you can workaround the issue in this way:
Temporary boot into CWM:
HTML:
fastboot boot recovery.img
Root the device using CWM
Flash CWM using flashify
[ CWM when you log out ask you for root so maybe it is not necessary to use the zip file ( but I'm not very expert so maybe I'm wrong)]
You can install GAPPS with CWM `gapps-kk-20140606-signed .zip` but be careful, whenever you update MIUI you will look all software installed using CWM. ( superSu and GAPPS for example )

thanks
thanks!

eienkisu said:
thanks!
Click to expand...
Click to collapse
Pleasure

Okay bro :good:
I'll update the OP

I confirm #postadelmaga the CWM recovery does not stay, the only way to do access it is the fastboot boot recovery.img Here's how I succeeded with two phones now.
power on, start wifi, do Miui updates
install ADB or the files above on PC
reboot to fastboot with voldown+pwr
now comes fastboot boot recovery.img
in CWM, sideload SuperSu and Gapps
connect you preferred VPN (if in China)
install and update all Google apps needed
delete most Chinese apps

hey i m unable to flash recovery plzz help
Device version 2014818
Sent from my 2014818

Hi buddy could you plz port touchwiz from galaxy prime?

The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.

not working.
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.

godwintgn said:
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
Click to expand...
Click to collapse
Are you on win7? I got this same issue on my win7... try on win8 it works flawlessly
Please hit thanks if done

Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.

Shrihari007 said:
Hi buddy could you plz port touchwiz from galaxy prime?
Click to expand...
Click to collapse
TW sucks man.. why do you want it :/ anyways I'll try

leuk_he said:
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
Click to expand...
Click to collapse
Thanks to you bro.. I'll update the OP for those who are facing some issues with my guide's precedure..

OP Updated
I've updated the OP with the other guide's link.. please check it out if you're having some issues with this one

godwintgn said:
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Click to expand...
Click to collapse
Try on some friend's PC or something

[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro

Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64

Nice, that is what we need .. Thanks Liam

How can i load twrp? Fastboot boot command, didnt work

DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread

Not working for me get a error file is to large to download when try to flash

dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools

liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same

Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?

Not working for me. Both sims dissapear and phone keeps FC.

pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"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"
}

I see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app

error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash

pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared

liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app

NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc

Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it

mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?

liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1

Great thanks!
But can we update OTA to B2 with this?

@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?

[CLOSED][UNOFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 8.1 | Phoenix |

{
"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"
}
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 are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
Note - As per the users request I tried my best to bring twrp support for Nokia SDM710 Community and I really don't own this phone
1 . Download twrp-3.4.0-0-PNX_sprout-10.0.img copy in one folder
2. boot in to download mode ( Volume down & power button )
3. open cmd type fastboot -w
4. type fastboot flash boot twrp-3.4.0-0-PNX_sprout-10.0.img
5. type fastboot reboot & immediately press volume up & power button for 8 seconds to boot in to twrp
9. Flash magisk or whatever you want either rom,gsi or kernel but fastboot -w command must and should until I fix decryption
Credits
* A big massive thank you for the one who tested my builds around 20+ images in a single day may be without him it's impossible to find another tester. thanks man TechnoStone
bugs- decryption & more..!!
Download Android 10 Twrp-3.4.0-0 From Here
​
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 8.1
Contributors
Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Source Code: https://github.com/omnirom/android_bootable_recovery
Device Source Code: https://github.com/Nokia-SDM660/android_device_nokia_PNX_sprout-TWRP
Version Information
Status: Experimental
Created 2020-04-29
Last Updated 2020-06-25

reserved

hello, I entered fastboot, but I cannot run command on my PC although I have installed ADB tool on my Pc. What can I do to flash your custom recovery on my nokia 8.1?
Big thanks to your for supporting Nokia 8.1 fan

nhthiencp said:
hello, I entered fastboot, but I cannot run command on my PC although I have installed ADB tool on my Pc. What can I do to flash your custom recovery on my nokia 8.1?
Big thanks to your for supporting Nokia 8.1 fan
Click to expand...
Click to collapse
1. Download latest adb platform tools
2. Extract to one folder
3. Name that folder as adb
4. Now copy that folder and paste in c: drive
5. Now copy path
6. Go to this pc give right click and click on environmental variables and click on path add your adb path and save it
7. Now adb & fastboot will work on all locations in your pc
Method 2
Download latest adb platform tools
Extract to one folder and name that as adb
Open adb folder
Open cmd in to that folder
Type fastboot devices
Now you will get your device ID
But before doing all these make sure your bootloader is unlocked
Regards
Raghu Varma

I understood what you explained. I can connect my phone to adn, it showed my device, however, i cannot run "fastboot -w", i think because my phone is still lock bootloader! How to unlock my bootloader, besides Hikari Calyx 's method???
Thanks!

nhthiencp said:
I understood what you explained. I can connect my phone to adn, it showed my device, however, i cannot run "fastboot -w", i think because my phone is still lock bootloader! How to unlock my bootloader, besides Hikari Calyx 's method???
Thanks!
Click to expand...
Click to collapse
.
Open this link and download hmd bootloader unlocker. Remember it will completely void your warranty and not possible to lock bootloader .

Does this really work on N8.1 ?
Or any Nokia ?

issues faced
Its not working sir...TWRP recovery stuck on logo...also the phone keeps restarting and freezing system ui, loss of wifi and hotspot creation facilities after flashing TWRP..I somehow managed to relock bootloader that saved my device or I was sure it was rendered useless... please check it thoroughly b4 uploading...I was on June security patch when flashed the recovery
N b4 u ask yes I followed all steps...

Can u please upload a working twrp please

Changelog - Thu Jun 25 12:41:03 UTC 2020
================================
* https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html

Please help me!
Raghu varma said:
Changelog - Thu Jun 25 12:41:03 UTC 2020
================================
* https://twrp.me/site/update/2020/06/24/twrp-3.4.0-0-released.html
Click to expand...
Click to collapse
i downloaded unlock key from Nokia, but when I flash unlock key, it notifies me Failed, so what should I do??? Thanks

Thank you for uploading this version. Install worked but touch screen seems non-responsive.
Installed latest build as of today twrp-3.4.0-PNX_sprout-10.0-20200821.img
Cannot find anything in /tmp/recovery.log
Edit: Tried both 3.3.1-0 and 3.4.0 with same result.
For others: dont hold the power button for 8 sec (but shorter) because it will make the device reboot

iljawashere said:
Thank you for uploading this version. Install worked but touch screen seems non-responsive.
Installed latest build as of today twrp-3.4.0-PNX_sprout-10.0-20200821.img
Cannot find anything in /tmp/recovery.log
Edit: Tried both 3.3.1-0 and 3.4.0 with same result.
For others: dont hold the power button for 8 sec (but shorter) because it will make the device reboot
Click to expand...
Click to collapse
it looks like the phone doesn't want to boot into android at all anymore. Only working thing is TWRP wihout touch enabled and fastboot.
Tryed to restore it via OST but it hangs on "getting variable 'productid'". :/ Does anyone want to share a proper boot.img?

iljawashere said:
it looks like the phone doesn't want to boot into android at all anymore. Only working thing is TWRP wihout touch enabled and fastboot.
Tryed to restore it via OST but it hangs on "getting variable 'productid'". :/ Does anyone want to share a proper boot.img?
Click to expand...
Click to collapse
There are stock boot.img collection. 430B is March, C is April, D is May, E is June, F is July, G is August

Doesn't work
After flashing twrp-3.4.0-0-PNX_sprout-10.0-20200829.img, I entered TWRP successfully. Then it stuck at unlock warning message and didn't get in system after rebooting phone.
This TWRP with big problem !!
After flashing back stock boot image and my phone can be booted into system.

after install twrp system not load

Hey guys, anyone can say if it works properly or not?
All those posts saying it half-bricked their phone doesn't seem very reassuring...
It'd be nice to finally have a working TWRP on this phone...

Is it fixed or still not working?

Thread closed on request of OP @Raghu varma

[RECOVERY][UNOFFICIAL][TWRP] Samsung M51 TWRP 3.4.0 (Stable)

UNOFFİCİAL TWRP RECOVERY 3.4.0
**ATTENTİON**
I'm not responsible for any bricked device.
Bugs
- Data encryption doesn't working. But I found a way to mount data. Follow my steps to mount data permanently.
- I couldn't find any other bugs. You'll tell me.
How to unlock your Bootloader?
**THİS WILL FORMAT YOUR DATA**
1- Go to Settings --> About Phone --> Software Information and click 7 times build number.
2- Now turn back to settings and pull down. You will see the Developer Options. Enable OEM Unlock and Usb Debbuging.
3- Now turn off your phone.
4- Hold [Vol Up + Vol Down] buttons and connect your phone to your pc while you are holding the buttons.
5- You will see a green screen. Hold the Vol Up button until an confirmation screen comes up and then only press Vol Up (Don't hold it again).
Now your phone will format itself and your bootloader will be unlocked !!!
INSTALLATION
(Before the installation you must unlock your bootloader)
1- Download the attached files.(Extract Odin,TWRP and USB Driver from the zip and install the samsung usb drivers)
2- Download your stock rom from the download button for a clean install.
(Extract the files too)
DOWNLOAD STOCK
(If you don't want to make a clean install you can skip to step 7 and format internal storage and data over twrp before installing the zips.)
3- Reboot your phone into bootloader (Press Vol Up + Vol Down Connect your phone and after it booted press again Vol Up)
4- Go to odin and click on the AP button and select your extracted AP (example: AP_M515FXXU1BTK4........_.tar.md5)
The verification will take a while be patient.
5- Now match the other files with BL CP and CSC
Leave Userdata blank.
Don't select HOME_CSC and delete this file otherwise twrps data mount won't work.
6- Press start and wait. NOW YOU MUST BE QUICK. After "Super" HOLD ONLY [Vol Up + Vol Down] until your phone reboots. It will take a while wait please. After it boots again into bootloader press Vol Up.
7- Now go to odin click AP, select Twrp.tar and press start . You must be quick again. Enter recovery after install before your phone reboots normal. Otherwise mount data on twrp won't work.
8- Now copy the files (Disable_Dm_verity.zip,Magisk.zip,multidisabler.zip) onto your sdcard or over mtp to your device. Install first Disable_Dm_Verity.zip and multidisabler.zip. Then install Magisk.zip. At last Install Disable_Dm_verity.zip again.
9- Reboot your phone and format data over settings to fix the 32GB storage bug.
10- After the format progress install MagiskManager.apk for root.
11- Enjoy it.
Backup your data before installing.
If you have any problems tell it me I'll help you.
If you want you can donate ​
Paypal(EUR): Donate
{
"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"
}
Paypal(US): Donate
BITCOIN KEY:
xpub661MyMwAqRbcFh8eA5BSesBNmKMAtFPpvP1wSrK53JmpPsKhQ5MwMwD64EyCjHEcCTiXmb3tD4TPUz2VpbfXDptc6QVew9H2x8ddQNdsiS4
​
After weeks I succeed fixing mount the dynamic partition and data. Now I'll work more on my miui project stay on.
Change Log:
Multidisabler 3.1 update
-Stable and compatible
Stable 2 -30th December 2020
-Fix mount Odm
-Fix backup Super Partition
Stable 1 - 26th December 2020
-Fix dynamic super partition mounting
-Fix File Manager
-Find a way to mount data partition correctly
-Fix MTP
-Other stuff
Beta 1 - 14th December 2020
- Fix mount external sdcard
- Fix screen overlay
Alpha 1 - 9th December 2020
- Inital Release
Thanks to
- @Zackptg5 for Disable_Dm_Verity_Forceencrypt
- @firemax13 for his source
- @LahKeda for his source
- @geiti94 for his source

Don't root your Samsung device as it will be void of warranty and many other troubles

k1n9n0th1n9 said:
Don't root your Samsung device as it will be void of warranty and many other troubles
Click to expand...
Click to collapse
I know what i do dont trouble.

I rooted it on the first day, but there's no rom nor kernel to flash. Poor for m51

dxxdxx said:
I rooted it on the first day, but there's no rom nor kernel to flash. Poor for m51
Click to expand...
Click to collapse
I made it .

Your recovery won't work, I managed to solve your vbmeta issue but it reboots to bootloader.
I built one from source and it still doesn't boot, even though I'm trying to fix that.
Maybe we will get a working recovery soon

It works now.

dxxdxx said:
I rooted it on the first day, but there's no rom nor kernel to flash. Poor for m51
Click to expand...
Click to collapse
What guide did you use?

grinna said:
What guide did you use?
Click to expand...
Click to collapse
ulnlock your device. then extract and install the file below over odin than download magisk zip and flash it (unlocking bootloader formatts your data)

hummm ... good things starting to happen for M51. Keep it up and thanks ...

Data Decryption is working?

LahKeda said:
Data Decryption is working?
Click to expand...
Click to collapse
I couldn't encrypt but i found a way to mount data permanently. You must disable forceencryption on your phone. I wrote on my steps how to disable. It works on me. I've tested it on my m51.

bekirakil said:
I couldn't encrypt but i found a way to mount data permanently. You must disable forceencryption on your phone. I wrote on my steps how to disable. It works on me. I've tested it on my m51.
Click to expand...
Click to collapse
so it's not much different from my build.
btw, did you build from source or ported it?

LahKeda said:
so it's not much different from my build.
btw, did you build from source or ported it?
Click to expand...
Click to collapse
I mixed it from s20 and a80 twrp and we don't need to type any command to mount system. Vendor and other partitions can mounted. These are de differences.

bekirakil said:
I mixed it from s20 and a80 twrp and we don't need to type any command to mount system. Vendor and other partitions can mounted. These are de differences.
Click to expand...
Click to collapse
That's already fixed in stable 1 and it works without any problem plus I don't use any hacks to mount the data or don't need to flash other files to mount data.
Just flash twrp files and it works out of the box

LahKeda said:
That's already fixed in stable 1 and it works without any problem plus I don't use any hacks to mount the data or don't need to flash other files to mount data.
Just flash twrp files and it works out of the box
Click to expand...
Click to collapse
No, you haven't fixed it we must type commands into terminal on twrp to mount. On my twrp it mounts automatically. But on yours vendor and other dynamic partitions haven't complete mount support.

In step 6, I don't see the super status, do you mean the pass status?

swiftez said:
In step 6, I don't see the super status, do you mean the pass status?
Click to expand...
Click to collapse
I mean a little bit earlier to don't miss the first boot. You must boot it again in bootloader before it boots normal.

bekirakil said:
I mean a little bit earlier to don't miss the first boot. You must boot it again in bootloader before it boots normal.
Click to expand...
Click to collapse
After following all the steps and have root, do I need to press power and volume up button every time I restart the phone to have Magisk root or can I boot it normally without pressing anything?

swiftez said:
After following all the steps and have root, do I need to press power and volume up button every time I restart the phone to have Magisk root or can I boot it normally without pressing anything?
Click to expand...
Click to collapse
After these steps you can boot your phone normally. Only at first install you need to go to magisk manager and install libraries.

[ROM][UNOFFICIAL][kebab][13.0_r16] LineageOS 20 [12/14/2022]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
LineageOS 20.0 source code Github repo
Kernel source code Github repo
Full Changelog
Instructions :
https://wiki.lineageos.org/devices/kebab
First Time Install / Clean Flash
1. Be on the OOS12 (C.36) (I didn't tested on OOS13)
2. Download copy_partitions, vbmeta, recovery, and rom for your device from here
3. Reboot to bootloader
4.fastboot flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery
5. While in recovery, navigate to Apply update -> Apply from ADB
6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
7. Repeat step 5 and adb sideload rom.zip (replace "rom" with actual filename)
8. Format data, reboot to recovery
9.While in recovery, navigate to Apply update -> Apply from ADB
10.adb sideload NikGapps-core-arm64-13-20220908-signed.zip
11.adb sideload NikGapps-Addon-13-SetupWizard-20220908-signed.zip
12.Format data, reboot to system
Update / Dirty Flash
1. Reboot to recovery
2. While in recovery, navigate to Apply update -> Apply from ADB
3. adb sideload rom.zip (replace "rom" with actual filename)
4. Reboot to system
Update from LineageOs19.1 to LineageOs20.0/ Dirty Flash (No data loss!)
1. Reboot to recovery
2. While in recovery, navigate to Apply update -> Apply from ADB
3. adb sideload rom.zip (replace "rom" with actual filename)
4.Reboot to recovery
5.adb sideload NikGapps-core-arm64-13-20220908-signed.zip
6.adb sideload NikGapps-Addon-13-SetupWizard-20220908-signed.zip
7. Reboot to system
Downloads :
https://sourceforge.net/projects/android-kernel-oneplus-sm8250/files/
I will make two build per month, and all build first i will test for 7 days on my device (KB2003) then I will release to public.
When LienageOs 20.0 is official out for kebab I will try to bring Crdroid 13 for our device.
Credits: @AnierinB, @LuK1337 and all LineageOs team!!

No touch if firmware Oos13,
Flash in progress firmware 12,
Thx.

CDI-78 said:
No touch if firmware Oos13,
Flash in progress firmware 12,
Thx.
Click to expand...
Click to collapse
I clearly sad in instruction that firmware is from OOS12 C.36
Thanks for try and happy flashing

It was to test, i was on 13
Flash using the good old method of fastboot rom installer.
NikGapps-core-arm64-13 and Magisk via adb,
everything works perfectly.

thanks, I'll compare it with pixel experience, although I'm undecided on which PE to download...

Happy Holidays all!
Is the rom working with TWRP as recovery, can anyone confirm?
Also, can I upgrade from 19 to 20 without data loss?
Screenshots of rom would be nice, if anyone can upload some that be great!

Happy holydays!
Here some screenshot.
I will test upgrade from LineageOs19 to 20, but I think you will loose data.

the rom is impressively stable, everything works perfectly,

...

CDI-78 said:
It was to test, i was on 13
Flash using the good old method of fastboot rom installer.
NikGapps-core-arm64-13 and Magisk via adb,
everything works perfectly.
Click to expand...
Click to collapse
Can you describe how you done that mate??Flash via FASTBOOT??Thanks and cheers.

hello,
I use fastboot_installer
you unzip the rom in "payload_input".
you run payload_dumper
when it's finished you go to payload_output, you copy the content of the folder to fastboot_installer.
you start the 8T in recovery,
factory reset (you lose your data)
advanced , enter fastboot
in the fastboot_installer folder you run ROMinstaller
if you want to install gapps you go through Apply update in recovery
Idem for Magisk, the zip in Apply update it will be necessary for you to install the apk of Magisk once the telephone restarted
Which firmware are you on? If 12 no worries, if not reflash the 12.
Merry Christmas XDA

Im on 13 damn..Thank for the head up mate..

Just flash this in recovery, apply update, adb sideload
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

CDI-78 said:
Just flash this in recovery, apply update, adb sideload
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
when exactly? before flashing Lineageos

exthomeboy said:
when exactly? before flashing Lineageos
Click to expand...
Click to collapse
First check ddr type of kebab is it DDr4 or DDr5 with this method:
1: Boot into recovery
2: Go to "Advanced" and press "Enable ADB"
3: Connect phone to PC
4: Run "adb shell getprop ro.boot.ddr_type"
A value of "0" means you have DDR4. A value of "1" means you have DDR5.
If this returns blank, continue to Step 5.
5: If that didn't work, try "adb shell cat /proc/devinfo/ddr_type"
Output should say "Device version: DDR4" or "Device version: DDR5"
Then install androd12C-36 firmware.
If you install firmware for a wrong ddr type then you will brick your device for good!!!
And after that install Lineageos.
Or wait next build will be on OOs13-F13 firmware.

bojantanasic said:
First check ddr type of kebab is it DDr4 or DDr5 with this method:
1: Boot into recovery
2: Go to "Advanced" and press "Enable ADB"
3: Connect phone to PC
4: Run "adb shell getprop ro.boot.ddr_type"
A value of "0" means you have DDR4. A value of "1" means you have DDR5.
If this returns blank, continue to Step 5.
5: If that didn't work, try "adb shell cat /proc/devinfo/ddr_type"
Output should say "Device version: DDR4" or "Device version: DDR5"
Then install androd12C-36 firmware.
If you install firmware for a wrong ddr type then you will brick your device for good!!!
And after that install Lineageos.
Or wait next build will be on OOs13-F13 firmware.
Click to expand...
Click to collapse
many thanks for your response. I'd rather wait for the next build then.

Update from Lineage19.1 to this rom is without data lost and everything works just fine.
I'm on new build with OSs13 firmware, if test go well I will release.
Happy holiday

bojantanasic said:
Update from Lineage19.1 to this rom is without data lost and everything works just fine.
I'm on new build with OSs13 firmware, if test go well I will release.
Happy holiday
Click to expand...
Click to collapse
Do you think those gapps will recommend it?

northernitaly said:
Do you think those gapps will recommend it?
Click to expand...
Click to collapse
Use same GAPPS that you use in LineageOs19.1 but for android 13!!

bojantanasic said:
Use same GAPPS that you use in LineageOs19.1 but for android 13!!
Click to expand...
Click to collapse
I imagine its lightness, battery, simplicity and support.