yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] darylzero:
:D

HOT 8 Magisk ROOTED

Boot.img Magisk patched

https://www.mediafire.com/file/0nzyd...tched.img/file

Original Boot.img

http://www.mediafire.com/file/32gtum.../boot.img/file

downloaded the uploaded firmware from google drive v236 i think

used techno tool to flash this to phone to VERIFY the firmwareis good and proper

once the firmware was verified and phone booted i uploaded the boot.img from that firmware v236 to magisk on phone and patched it

got this patched boot.img back to computer

now for the flashing part

install ADB drivers

on phone activate usb debug and oem unlock in developer mode in settings

check ADB is working and sees phone n computer via usb with command

"adb shell"

shouls show a valid response indicating phone is ADB ready

next get it into Fastboot mode with command

"adb reboot bootloader"

wait till phone reboots into fastboot mode check fastboot mode is active with this command

"fastboot devices"

now to unlock bootloader in fastboot else it will give error

use command

"fastboot flashing unlock "

this will also give a acknowledge on the phone that BOOTLOADER will now b unlocked and press volume up to agree

once bootloader is unlocked in fast boot next it to flash the magisk boot.img patched

i have uploaded this to medifire please download

place this file named

magisk_patched.img on desktop

use command boot

"fastboot flash boot (( need to drag and drop the file magisk_patched.img from desktop here ))"

wait till magic is done

after use to

"fastboot reboot "

after phone reboot it will b factory reset and rooted check root with magisk manager installed

root checked verified

https://www.mediafire.com/view/a2ivw...22733.png/fileif

any one needs anything message
[Android Q&A, Help & Troubleshooting] AshhRED:
Good job bro...

Plz POST

1. SCREENSHOTS

2. DEVICES STABILITY & PERFORMANCE REVIEW
[Android Q&A, Help & Troubleshooting] Munirathinam:
Bro my device bricked.

Sp flashtool not working.

Techno flash tool not working.(ongoing. 0% Completed.but 30 minites already finished.)What i do
[Android Q&A, Help & Troubleshooting] alecxs:
[MENTION=9248480]Munirathinam[/MENTION] for testing purposes do a read back of boot.img to make sure preloader drivers installed correctly and SP Flash Tool works. If you fail in readback, you don't have installed preloader drivers, or did not connect usb while power off AFTER clicking. You should focus on this until readback works for you.

Regarding MTK secure boot enabled devices with SP Flash Tool, just some common rules. Make sure you won't in any case:

1. DON'T flash preloader (always uncheck)

2. DO NOT "Format All + Download" or "Firmware upgrade" (this will hard brick your device)

3. DON'T use a wrong scatter file

If you can flash stock boot.img but don't allowed to flash magisk_patched.img you need to find another download agent. please note some DA only work with specific SP Flash Tool version, whenever you find DA+SPFT as bundle - use it
[Android Q&A, Help & Troubleshooting] Munirathinam:
Bro check this image.

I got more angry.

Help pls.

(Dead boot)I think.not power on.help pls
[Android Q&A, Help & Troubleshooting] alecxs:
this image says nothing to me. looks like phone is not connected in preloader mode. can you please check readback from SP Flash Tool?
[Android Q&A, Help & Troubleshooting] Munirathinam:
Readback ??how
[Android Q&A, Help & Troubleshooting] alecxs:
- install VCOM preloader drivers (this step is mandatory you should have done already)

- disconnect your phone usb

- power off phone completely

- find the read back section in SP Flash Tool

- create new entry for region emmc_user

- use start address and length from scatter file

- name it boot.img

- start the read back (for your entry)

- connect the phone usb and see readback is starting immediately, it takes just a couple of seconds

(just for the protocol readback does not harm your device it just dump a raw section of emmc - backup of boot.img in this case)

The following link is for creating your own scatter file (no root) and you don't need to follow the whole tutorial. it is for illustration only.

https://forum.hovatek.com/thread-21970.html
[Android Q&A, Help & Troubleshooting] Munirathinam:
Any Good news about TWRP??
[Android Q&A, Help & Troubleshooting] jameeldroid:
So finally someone came forward to try..

Does it retained phone encryption? How's the root experience :p

---------- Post added at 11:21 PM ---------- Previous post was at 11:20 PM ----------

Were you able to unbrick your phone?
[Android Q&A, Help & Troubleshooting] Munirathinam:
Infinix Service center.

My mobile not bricked.

They did only(something not connect.i think wire.) They did only that. No problem bro.
[Android Q&A, Help & Troubleshooting] Kuldip#:
Any custom rom for infinity hot 8 like miui 10 or 11 please help me

---------- Post added at 02:32 PM ---------- Previous post was at 02:18 PM ----------

Please if miui 10 available for infinix hot 8 then share please. .. all XDA developers please help me I don't like current rom
[Android Q&A, Help & Troubleshooting] Munirathinam:
You installed TWRP RECOVERY???

You can install gsi ROM.YES Possible.
[Android Q&A, Help & Troubleshooting] jameeldroid:
does mtk-su works on encrypted devices? i read somewhere it won't if device has dm-verity enabled.

---------- Post added at 10:59 PM ---------- Previous post was at 10:56 PM ----------

if i have scatter file for v236 and use that same scatter file to read boot image of v217 would it work? i mean the scatter file has memory address start and end for all the blocks so it should work right?

---------- Post added at 11:05 PM ---------- Previous post was at 10:59 PM ----------

Hi, i have been away for long because of exams. thank you for the try :D one quick question; is there a way to retain data when unlocking boot loader. ???i dont want to lose my apps and data.

---------- Post added at 11:17 PM ---------- Previous post was at 11:05 PM ----------

the first link you shared says there are two methods to flash. first is to flash the twrp via sp flash tool. does the sp flash tool allows flashing without bootloader unlock? if its possible then we dont need to unlock the bootloader and just flash the patched boot image directly via sp flash tool.. what you say?
[Android Q&A, Help & Troubleshooting] alecxs:
Yes readback will give you a copy of V217 boot.img (the scatter for boot usually won't change for roms) and yes it may possible to flash recovery with locked bootloader (i did this for MT6580) but maybe just oem signed images will pass secure boot. Try to dump userdata partition and it's assigned metadata partition (that's where the encryption key is stored). you should be able to restore it after unlocking. best is full rom dump.

edit: you can test scatter (at least for this partition) by unpacking boot.img with AIK - if it works the scatter was right
[Android Q&A, Help & Troubleshooting] AshhRED:
Don't flash it the .IMG is currupted, with potential to HARD-BRICK (DEAD/UNRESPONSIVE) your device.

Wait for the official port or compile with AIK-LINUX.
[Android Q&A, Help & Troubleshooting] AshhRED:
SUCCESSFULLY

*ROOTED
[Android Q&A, Help & Troubleshooting] AshhRED:
Juzz give me some time to Update the OP with complete GUIDE & THOROUGH Instructions for

*Rooting

*ADB-SideLoading

*UnBricking HARD-BRICK (Dead/UnResponsive)

*Flashing STOCK-ROM

*DM_Verity disabling
[Android Q&A, Help & Troubleshooting] Munirathinam:
Ok bro I'm waiting.

I have one idea to use Custom rom.view Dualboot Patcher app?? I don't know it's working or not.but root required.

After root we can install TWRP RECOVERY it's Possible.?? Pls tell bro.im waiting for TWRP and custom ROMs??
[Android Q&A, Help & Troubleshooting] alecxs:
[MENTION=7612623]jameeldroid[/MENTION] to clarify, in stock boot fstab there is a mount flag "forceencrypt" which forces to encrypt userdata partition on first boot. patching against encryption will just remove this flag. There is no way to become decrypted in any case, your userdata partition remains encrypted until you format. Even if you flash encryption disabler (or patched boot) and start with fresh formatted unencrypted device (the only way to become unencrypted), you still can encrypt your userdata partition from settings - security later, no worry. magisk works with encryption, and a proper TWRP will work with encryption too (i wonder why nobody port from X650B - just replacing kernel will work)

if you want to backup your userdata before unlocking bootloader:

1. try to get a root shell with mtk-su (dm-verity doesn't prevent it from work), or

2. try full rom dump with sp flash tool (read back)

tell if one of this works, so i can give detailed instructions for backup/restore
[Android Q&A, Help & Troubleshooting] jameeldroid:
have you upgraded to v236 to get the root?
[Android Q&A, Help & Troubleshooting] jameeldroid:
i have tried both 32 & 64 bit mtk-su, it gives the following error.

Infinix-X650C:/data/local/tmp $ ./mtk-su

Failed critical init step 4

This platform is not supported

1|Infinix-X650C:/data/local/tmp $

ok i have tried the sp flash read back method. drivers are ok. i turned off my phone and when i plug the usb cable it detects and installs the drivers successfully and it appears in device manager but after few seconds the charging sign appears on screen of phone and then the com port just disappears.
[Android Q&A, Help & Troubleshooting] alecxs:
That's expected behaviour. preloader does not receive instructions from SP Flash Tool. That's how it works. prepare readback and click download, then connect usb cable. preloader comes up for a second, SP Flash Tool is detected and readback will start immediately
[Android Q&A, Help & Troubleshooting] jameeldroid:
Hi everyone,

I have successfully ROOTED my infinix hot 8 X650C today. I did it after updating my firmware to V258. This is most recent update and i did it via OTA.

after that i searched my firmware zip over internet and patched boot.img from it via magisk, unlocked boot loader and flashed the patched image and it was done.

unlocking boot loader clears data, i relied on google backup for now and also moved data to my PC as backup.

---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------

hi, well it was a little difficult to backup via sp flash tool, i know it is possible but i haven't had much time, so i went with google backup and manual backup of files to pc for now. unlocked bootloader and gained root.

i would like to port twrp for this model. can you help me for this? i have searched a little and read about Carliv android kitchen tools for windows. would this work?

one more questions regarding porting twrp is that would it remove current root access after flashing?

thank you
[Android Q&A, Help & Troubleshooting] alecxs:
replace kernel, ueventd*.rc and edit entries in /etc/recovery.fstab (do not copy file from stock recovery there are lot entries not required, especially vold mounts may cause trouble) CarlivImageKitchen should be fine, also AIK will work (sudo.exe is required for repacking, you need to disable antivirus when unzipping). you can use TWRP+3.3.1+For+Infinix+hot+8+(X650B).zip as base (or try this or this) i bet Helio A22 or P22 will not make big difference so just replacing kernel may be enough. if nothing does give you a splash screen then repeat with another twrp for your exact SoC (MT6762). for userdata partition there are different methods for encryption, in fstab.mt6765 should look like (just example) if decryption unsuccessful play with this line:

/data ext4 /dev/block/platform/bootdevice/by-name/userdata flags=encryptable=/dev/block/platform/bootdevice/by-name/metadata

in default.prop prop.default (replace) there you should enable usb-debugging for TWRP by changing/adding these lines:

ro.adb.secure=0
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

windows users please use Notepad++ or you will end up with wrong line endings (CRLF) for linux/android (LF)

you won't lose root except for devices with no recovery partition where recovery-ramdisk is located inside boot.img or system-as-root devices, anyway you can test your build from fastboot without flashing

fastboot boot twrp.img

backup your stock recovery from terminal before flashing twrp (root required)

dd if=/dev/block/platform/bootdevice/by-name/recovery of=/sdcard/recovery.img

if twrp is crashing or boot-looping at splash screen, try to pull recovery.log from adb (you can upload for further analysis)

adb pull /tmp/recovery.log

as always - don't believe me anything, please double check and make your own research. good luck

edit: for more info read this porting guide
[Android Q&A, Help & Troubleshooting] Munirathinam:
Bro request a TWRP recovery for [MENTION=8355838]Augustoandro[/MENTION]

---------- Post added at 12:11 PM ---------- Previous post was at 12:08 PM ----------

TWRP Request Page

https://xdaforums.com/android/general/unofficial-twrps-devices-source-code-t3833338/page36
[Android Q&A, Help & Troubleshooting] Munirathinam:
How You Flash Patched Boot image view sp flash tool or Adb cmd??? I tried many times for upgrading firmware but sp flash tool not working what is the problem???
[Android Q&A, Help & Troubleshooting] Zanthob:
TWRP for infinix hot8 lite (X650_H8029)

Hi everyone, please I need TWRP for infinix hot8 lite .....I've searched for it on internet I didn't see it ......if someone can help I will glee

''

Android 8.1 (oreo), XOS 4.

2/3GB

2GzOCTACORE-Mediatek MT6762 Helio P22 chipset..

6.52 inches-720 x 1600 pixels

any Help will be greatly APPRECIATED..
[Android Q&A, Help & Troubleshooting] darylzero:
Please upload or provide the firmware v258 so other people can also root on it

thnx again
[Android Q&A, Help & Troubleshooting] jameeldroid:
i flashed it using adb and then fastboot commands.

---------- Post added at 10:31 PM ---------- Previous post was at 10:29 PM ----------

i have updated the link for firmware v258 in my earlier posts. i have tried your method to directly boot the ported twrp .img file and now my phone is in bootloop. should it be in bootloop for this? why isn't it booting to the OS ? :confused:

okay so i was able to get out of the bootloop. for this i had to flash v258 stock firmware with techno tool and wowwww it preserved all the user data, apps and settings etc, i mean it didn't touch anything everything is intact.. i am so relieved and happy.
[Android Q&A, Help & Troubleshooting] alecxs:
for fixing boot loop, try

fastboot format:ext4 cache

or flash cache.img should have same effect..

i don't know the reason. just booting from fastboot should not alter any data, except it can write logs to /cache partition. strange.

/cache/recovery/log file may give information whats going wrong, if read back works you can readback, mount the cache.img on a linux machine and view the logs
[Android Q&A, Help & Troubleshooting] darylzero:
to update i downloded the firmware v258 and used techno tool to update keeping all apps intact

after boot patch the boot.img and apply via fastboot to re-root

phone is now rooted with magisk and on firmware v258
[Android Q&A, Help & Troubleshooting] jameeldroid:
how to re-lock boot loader?
[Android Q&A, Help & Troubleshooting] AshhRED:
adb devices

adb reboot bootloader

fastboot devices

fastboot flashing lock

(Press VOL+ for confirmation)

fastboot reboot
[Android Q&A, Help & Troubleshooting] jameeldroid:
done.

---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------

would it remove root or erase userdata etc like it did when unlocking?

---------- Post added at 06:13 PM ---------- Previous post was at 06:10 PM ----------

i have followed both tutorials and ported recovery but it failed. i used X650B twrp for porting.

i tried the ported recovery by "fastboot boot <recovery image>" command but it booted to OS after few seconds.

then i tried the actual twrp for x650b too but it also booted to OS. does it mean that the twrps are not working or the phone is skipping them somehow? what is the case?

---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------

i have another questions too, yesterday i tried to uninstall google apps like youtube, drive, movies, music and some system apps like AHA games, Palmstore etc.

i did it with TB. the apps were removed on the go but when i rebooted the phone, they came back.

then i set selinux to permissive mode. used TB to remove apps and when rebooted all the apps were back.

then i used system app remover (root), an app from playstore, give it root permissions and then removed the same apps and this time my phone didn't boot to OS, it kept booting to fastboot mode everytime. whyyyyyyyy?

---------- Post added at 06:24 PM ---------- Previous post was at 06:16 PM ----------

another thing i have noticed is gsmarene says the chipset for this phone is MT6762 but the scatter file came with the stock rom says it is MT6765.

this is from scatter file and the name of the file also has MT6765.

general: MTK_PLATFORM_CFG
info:
- config_version: V1.1.2
platform: MT6765
project: x650c_h626
storage: EMMC
boot_channel: MSDC_0
block_size: 0x20000
[Android Q&A, Help & Troubleshooting] alecxs:
i guess it's the same SoC just with different clock rate and the Helio P35 is just a overclocked P22 (at least i don't know, just speculation). Try porting official TWRP for Xiaomi Redmi 6. if the fastboot testing method boots into normal boot instead, recovery has failed/crashed

common warning:

Do not re-lock bootloader this will brick your device and you may not be able to unlock again! You have to be completely stock for re-locking!
[Android Q&A, Help & Troubleshooting] AshhRED:
Rooting the device is easy, as many users on this thread successfully acheived... But Sustaining it on persistent level is another matter..

Because there is no official TWRP yet and no one successfully COMPILED the PORT for this Device..

The issue is with DM_Verity

The comman ERRORS are:-

*ORANGE STATE (Fastboot BOOTLOOP)

*Single BOOT ROOT ACCESS (device loses ROOT after reboot and can't patch the Magisk_patched.img due to Device Mapper)

*USER BUILD DEVICE

we can change the build.prop with

ro.build.type=userdebug

By ADB PULL system -rw/ and set permission while updating chmod 655

and use

adb disable-verity for Sustaining.

Or after the first boot with ROOT try using RASHR to flash

Disable_dm_verity.zip

with RECOVERY-SCIRPT_MANNAGER

to DECRYPT PARTITION..

But I think the safest and most STABLE way to ROOT is by CUSTOM-RECOVERY, in this way we can DECRYPT easily by FLASHING (.ZIP) files
[Android Q&A, Help & Troubleshooting] Munirathinam:
I created a TWRP recovery.anyone want to test this.i used Infinix s4 TWRP to build Infinix hot8 recovery.now who want to test this????
[Android Q&A, Help & Troubleshooting] GRPPANDIAN:
Plz upload twrp for x650c

Upload I like to testing...
[Android Q&A, Help & Troubleshooting] Zanthob:
No problem upload it
[Android Q&A, Help & Troubleshooting] Munirathinam:
Note:if TWRP not work maybe device can brick or Bootloop.so try this your own risk.

And tell what problem you're faced.after installed this.

Link.

(Link removed )
[Android Q&A, Help & Troubleshooting] are_goenk:
Will I lose my root access if I update my firmware from X650C-H626DEJ-P-191023V236 to X650C-H626DEJ-P-191127V258?
[Android Q&A, Help & Troubleshooting] GRPPANDIAN:
Yes Sure u loss ur root access if u firmware upgrade.But after upgrade u can re root same method.v258 also supports Magisk root method.

---------- Post added at 08:40 AM ---------- Previous post was at 08:30 AM ----------

@MuniRathinam...Bro remove that file immediately. when i flashed its a Result is Bootloop only.So Dont flash that recovery which one u ported from S4.
[Android Q&A, Help & Troubleshooting] AshhRED:
Never direct Flash unsigned (.imgs) files, for testing always use

"fastboot boot *******.img"

In this way even if the file is currupted , Your STOCK build is unaffected..
[Android Q&A, Help & Troubleshooting] Munirathinam:
Root users one help pls.

Download and install Dualboot Patcher apk.and check this app working or not.

I used this app for custom rom but this app said your device is not supported.

Guys check and tell me pls.

(Open Dualboot Patcher app and give root access.and go to settings.and install Boot UI) Boot UI not supported on custom ROMs ) Now you guys check and tell me.

App link

https://sourceforge.net/projects/dualbootpatcher/
[Android Q&A, Help & Troubleshooting] GRPPANDIAN:
[MENTION=5679040]rathinam[/MENTION] ...sure cant bootpatcher usage.coz at this stage we are in only systemless Root so cant change or modify system files.so we need to wait for some mods for compile TWRP.
[Android Q&A, Help & Troubleshooting] InfernoCR:
My device is 3gb/32gb variant but it shows as x650c(4/64 variant).can i use patched boot image for x650c?
[Android Q&A, Help & Troubleshooting] alecxs:
if you can post a screenshot of settings - about phone - build no, somebody will tell you
[Android Q&A, Help & Troubleshooting] InfernoCR:
Edit:i can't post any photo
[Android Q&A, Help & Troubleshooting] Munirathinam:
Why??.you have any problem about uploading photo??
[Android Q&A, Help & Troubleshooting] InfernoCR:
Yeah,in xda labs it says "bad request" and in browser the image doesn't display at all
[Android Q&A, Help & Troubleshooting] Munirathinam:
Bro we are crossed already 11 Pages but we got problem still finding TWRP recovery only.

I don't have any hope.
[Android Q&A, Help & Troubleshooting] InfernoCR:
Can someone post x650c unpatched boot.img(v258 if you can) mediafire/gdrive/mega link?I want to do some experiment
[Android Q&A, Help & Troubleshooting] alecxs:
you can use V258 boot.img

see post #30
[Android Q&A, Help & Troubleshooting] alecxs:
there is no ramdisk in boot.img i wonder how magisk can patch this? for system-as-root you need a different porting guide (sorry for misleading). also confusing there is a separate recovery partition (which implicates this is a non-A/B device) but there is also ramdisk-recovery.img along with recovery.img in stock rom. data partition seems to be f2fs not ext4. in recovery.img there is a folder /system_root i guess system needs to be mounted to /system_root in recovery instead of / in normal boot. this is a mistake in recovery.fstab

edit: you need to set the flag "Magisk in recovery" in Magisk Manager app and patch recovery.img instead of boot.img. root only applies if you boot into recovery and release the keys on splash screen. you need to press key combo each boot

magisk-in-recovery

unpatched V258 recovery.img

(attachment removed)
[Android Q&A, Help & Troubleshooting] AshhRED:
[MENTION=7285913]aIecxs[/MENTION]

Tnx for clearing this..

Quick Wondering...

1. since it's patching the ramdisk partition in RECOVERY.img, what's is the correct flashing cmd ?

Or

2. If Magisk can't patch the BOOT.img then how did it install SU-binaries in /sbin/ ?
[Android Q&A, Help & Troubleshooting] alecxs:
1. the magisk patched (recovery.img) must flashed to recovery partition, second cmd is right

2. i am not sure how/if magisk did this, magisk usually won't place any files to system. according to your screenshot it looks like SuperSU. well i have no clue, maybe the magisk documentation is outdated, or it was rooted before upgrading to pie? you should know better than me
[Android Q&A, Help & Troubleshooting] InfernoCR:
Someone want to try this twrp?most likely wont boot/bootloop,but worth a try

use fastboot boot twrp.img

WARNING!!! IM NOT RESPONSIBLE FOR ANYTHING CAUSED BY THIS,

DO IT WITH YOUR OWN RISK

http://www.mediafire.com/file/axtr75108i4gqge/twrp.img/file

*Anyone noticed there is new update for x650c?
[Android Q&A, Help & Troubleshooting] AshhRED:
Unlikely.... I'll give it a try.

Let's hope for the BEST
[Android Q&A, Help & Troubleshooting] AshhRED:
ORANGE STATE BOOTLOOP

*DONT TRY* Had to reflash the whole firmware using techno flash tool.

Patched boot.img for root access but am sure it will subside once I reboot so just waiting for TWRP for disabling DM-VERITY