Database Info

[Recovery] TWRP 3.0.2-0

{
"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"
}
Credit: Captain_Throwback​
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.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Downloads:
- twrp-3.0.2-0-a16
- md5: 552620e0834ab9be3e0a588258a4bc14
*Optional*
- ADB_Fastboot
- md5: fc78b03f23e562c919bfbaea0ef9bc79
Install Instructions:
- Unlock Your Bootloader (Instructions)
- Boot your device into Download Mode (adb reboot download)
- Flash TWRP via Fastboot (fastboot flash recovery <twrpfilenamegoeshere>)
*Optional*
- Boot into TWRP (adb reboot recovery)
- Go to advanced, then enable sideload
- Flash supersu (adb sideload <supersufilenamegoeshere>)
Original Root/S-OFF guide by jcase can be found HERE​

Will we get the latest twrp recovery?

wilbigdaddy2000 said:
Will we get the latest twrp recovery?
Click to expand...
Click to collapse
As soon as I get a chance buddy. I've been working some crazy long days(60hrs/WK) and dealing with family issues.
Just stick around and hopefully me or another SlimDesire Dev will get to it ASAP.

Wow only one person well 2 now hit the thanks button. Show your thanks people.
Thanks by the way dev

Appreciate the love Josh, but I've been in the Android game here on XDA since 2008 and know that not all things are appreciated. No worries, Captain_Throwback deserves all the thanks for this build anyways.

AndroidSamurai said:
Appreciate the love Josh, but I've been in the Android game here on XDA since 2008 and know that not all things are appreciated. No worries, Captain_Throwback deserves all the thanks for this build anyways.
Click to expand...
Click to collapse
You good bro I've been here since around 2008 myself. My first phone was HTC mytouch 4g lol and uneven the first Android phone the G1 and so forth. I know the G1 was the was the first Android phone but I didn't hear about rooting until HTC mytouch 4g. Been doing it ever since, I even ported few roms like MIUI. Maybe soon I will be porting to this device.

Hope this is not considered as spamming threads. I just think this message is relevant to this thread in particular since is TWRP-related.
In case some of you can not load the TWRP image from the first post in this thread in your devices after flashing it, i recommend you try this another image also by Captain_Throwback. It worked with no problem on a HTC Desire 530 from Claro Chile, and maybe it will work on other versions.
Captain_Throwback said:
Alright, rebuilt TWRP with dtb separated (though that really shouldn't make a difference). If this one doesn't boot, I'll try using the dtb from the 3.0.2 TWRP, and if that still doesn't work, I'll just revert to the kernel/dtb from the original 3.0.2 release. I was hoping to be able to use the source-built kernel to patch the touch driver and clean up/fix some things, but that may not be possible. Unless this works, in which case, yay!
Click to expand...
Click to collapse
Click on the arrow inside the quote title to see the full post, so you can also see the link to the image file.

Everytime I try to make a back up in TWRP the phone reboots as soon as the back up begins. Anyone else had this happen? I'm used to nexus phones and this one is complicated to me

OP Junior Member9 posts Thanks: 0
In my devices htc desire d530u do not have any RUU file or any other ROM.
device have problem that it show HTC logo and do not start after this logo,I do all process which is given to internet ,it do not working.................................
IF any one have solution of this problem PLZ help
-----------------------------------------------------Devices info---------------------------------------
htc download mode
****RELOCKED*********
HTC_a16ul PVT s-on
LK-1.0.0.0000
RADIO-01.01_U113251482_62.02.60930G
OpenDSP - UNKOWN
OS - 1.32.709.12 taiwan version
Oct 11 2016,21:00:37{796991}

First of all I would like to thank anyone and everyone who has made phone rooting guides, they definitely help out!
Now my question, does anyone have the stock RUU: RUU_A16_UL_M60_DESIRE_SENSE70GP_TMUS_MetroPCS_US_1.36.1550.5_Radio_01.01_U113251531_68.01.61229G_release_495720_signed_2.exe
I cannot find this file anywhere, even the download link on HTC's website is broken. Unfortunately TWRP wont work on my Desire 530 because I upgraded my ROM to 1.36.1550.14. So I need to downgrade from what I've heard in order to get TWRP working, then I can install an S-OFF kernel and install Super-SU. Make sense to anyone?
I unlocked my bootloader and flashed TWRP to my recovery. When I reboot my phone into recovery I see the TWRP screen, then the phone reboots. I've tried clearing my cache partition, and that hasn't helped. I managed to do this by following directions for clearing cache partition on T-Mobile website with stock recovery image BTW. I also tried flashing several different versions of TWRP, some experimental builds by Capt Throwback, and some builds for other phones. I just can't get any relief.
Thanks in advance!

Help!
Hello when I want to install the twrp in cmd it keeps saying device not found, while my phone is connected pls help! I am a noob when it comes to phone rooting and stuff!!!

Hey there. So I tried to flash this after updating to the 7.0 Nougat update but it fails to boot.
---------- Post added at 04:13 AM ---------- Previous post was at 04:12 AM ----------
Haruncosovic said:
Hello when I want to install the twrp in cmd it keeps saying device not found, while my phone is connected pls help! I am a noob when it comes to phone rooting and stuff!!!
Click to expand...
Click to collapse
Have you got it working. It's been almost a month so I'm sure you have.

can you please reshare the files? im not able to download.. Thank you very much

Vortex SYNQ Dev Thread (TWRP Image & Bootloader Unlock!!!)

During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
UPDATE: We now have enough people to really get the ball rolling for some development for this phone, so as we accomplish more things we'll post them here

Anything you try from here, you do so at your own risk. This may void your warranty, break your device, etc.
HOW TO UNLOCK THE BOOTLOADER
Go to Settings>About Phone>Build Number and tap this a lot really fast to enable developer mode
Go to the new developer mode option in the Settings menu, check the switch that says Allow OEM Unlock
Plug your phone into your computer, enable ADB Debugging, open up a terminal on your computer, and initiate an "adb reboot fastboot" to put the device into fastboot mode
In your computer terminal again, type in "fastboot oem unlock". If it fails, run it again. If it fails again, reboot to fastboot one more time and try a couple more times. Eventually it should work after a couple tries, it did for us
Confirm the device unlock on the phone (pressing volume up at the prompt I believe), and wait for the phone to reboot. Note that it's not stuck in a bootloop at this point, it's just factory resetting after the unlock, so give it time to work
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 1
Pull a recovery image from the phone with SPFT using a proper mtk6739 scatter file which I can't exactly find
Port TWRP to the phone from another device's mtk6739 TWRP image with carliv image kitchen tool, and flash it back to the phone with SPFT
Flash Magisk in TWRP, reboot, profit
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 2
Pull a boot image with SPFT
Use the Magisk APK to inject magisk into the boot image
Flash the boot image back with SPFT (or maybe fastboot), reboot, profit
HOW TO FLASH TWRP TO THE PHONE (STILL EXPERIMENTAL)
Download the TWRP image from here
Reboot to the bootloader
Assuming you unlocked the bootloader from before, just do "fastboot flash recovery [imagename]" to get it on there
If fastboot complains about it not being able to flash, try running the command one more time
CUSTOM ROMS FOR THIS PHONE
This phone came with 8.1 Oreo, so that means it has to be Treble enabled. I'm no expert with Treble stuff but I believe GSIs made for arm a-only partitions SHOULD work on here. We haven't tested this for ourselves yet though
Like mentioned before, feel free to drop by and leave a message if you're willing to help us out on our endeavors. I also want to try and get 'Thew a working recovery on his phone again if possible, since for some reason when we try to flash back the image we pulled (with our "best guess" mt6739 scatter file) it didn't work

i might have one.. i will check as soon as i get to the shop

jasonmerc said:
During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
Unfortunately during our testing, he seems to have messed up his recovery image and is unable to restore a stock one on there. If there's any other owners out there willing to help us out (and maybe willing to risk their device for some test builds of TWRP too) I beseech thee to make yourself known.
Click to expand...
Click to collapse
i have one .. if you need

desbloqueokings said:
i have one .. if you need
Click to expand...
Click to collapse
Check your PMs on here, just sent you something

So the other 6739 scatter files we found didn't exactly work for this phone, so we pulled our own with a tool we found on Hovatek. This isn't a "port" from another phone, this directly came from the Synq itself.
Give major thanks to @desbloqueokings for pulling this for us!

The group we had seems a bit inactive now, so I'll post my new creations up here for all you guys here to test and tell us all if it works or not. One is a patched boot image that contains Magisk, all you'd need to do for that is flash the boot image and install a Magisk APK and you should be good to go for root. The other is a dirty port of TWRP Recovery I did from another MT6739 phone. It was hard finding an image to port from, so I want to give a huge thanks to @lopestom who sent me a 6739 image he had that I could port from
PLEASE BE AWARE THAT THESE ARE TEST IMAGES. I DONT HAVE THIS PHONE MYSELF AND CANT TEST IT MYSELF, SO IM NOT SURE IF THESE WILL WORK OR NOT. PLEASE MAKE A BACKUP OF YOUR CURRENT BOOT & RECOVERY IMAGES WITH SPFT USING THE SCATTER FILE ABOVE BEFORE TRYING ANY OF THIS. WHAT YOU DO TO YOUR OWN PHONE IS YOUR OWN RESPONSIBILITY. WHILE I WILL TRY TO HELP YOU IF SOMETHING BREAKS, IM NOT RESPONSIBLE FOR WHAT YOU CHOOSE TO DO
With that being said, here's the Mega folder containing the boot and recovery images. You can either flash these through SPFT like most people do with mediatek phones, or through fastboot, whatever you can get working. I'd also recommend you unlock your bootloader using the method posted above before doing any of this
Let me know if this stuff works or not, if you choose to flash it

Our victory was bittersweet, but a victory nonetheless
We got a working recovery image from @lopestom that seems to work fine on the surface, but when we need to flash the zip that disables dm-verity (disables force encryption) it supposedly breaks the /system partition on the stock ROM. My recommendation would be to take a backup of your /system directory in recovery before trying to flash anything. But since this is a Treble-enabled device, that means GSI ROMs could also work when flashed.
Here's a link to the recovery image we were using. We flashed it in fastboot with an unlocked bootloader but I imagine it would work just fine in SPFT too. I was told by the person that made the image that it's apparently not a good idea to flash the disable-force-encryption zip on a dirty port of a TWRP image like this (and to also never wipe /data). While you should be able to use this TWRP to flash something like Magisk, don't do those other two things for now.
Here's some screenshots from @Matthew702 to show the phone booting to TWRP (we made the mistake of trying to wipe /data and trying to flash the disable-encryption zip, please do not do 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"
}

Thank you!

You guys are amazing.
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx

xAlimorAx said:
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx
Click to expand...
Click to collapse
Yeah it showed up in Russian for our tester too. Not sure why it does that, but otherwise it should still work fine

Need your assistance
Season greetings to you my friend, I ended up formatting my vortex synq using Sp flash tool, after attempting to root, now I have black screen only vcom for sp flash tool works but I need preloaded files and others to unbrick, it was gonna be a Xmas gift for my aunt, but I messed it up, wont turn on just vcom when connected to PC, I have the files stckboot and recovery but sp tool needs pre-loader error, plz help me

Please back up vortex synq
Good I ask for a help to see if someone will have or could make a back up for this vortex synq cell phone since some of us have problems in the firmware when modifying it and we do not have a previous backup if someone can collaborate, it would be infinitely appreciated.

I know this post is old but if somebody can backup the firmware from this it would be awesome, because i am trying to restore my vortex snyq (its hard bricked) but i can't find the preloader for this phone anywhere, when i tried to flash the preloader with sp flash tool it gives me this: STATUS_DA_HASH_MISMATCH, the preloader has to match this phone, if anyone has a backup of the firmware feel free to post it here or dm me, but yeah just wanted to post here.

also need firmware having the same issue ages now
any help much appreciated
safe 2021-2022

use this to unlock bootloader and backup fw https://github.com/bkerler/mtkclient

Making this post to do a dump of the Vortex Synq stuff I had on Mega. XDA allows us to upload large files to here now, and my Mega account is getting pretty full, so I want to transfer everything I have that's Vortex Synq related from there to here. That means any download links pointing to my Mega will be broken, but all of that stuff previously linked by me can be found in this zip.
disclaimer
Feel free to use any of my stuff in any way you see fit. The only thing I ask is that if you do improve on something, share it with everyone else and don't just keep it for yourself. Keep it going for the good of the community/public.
Also, know that it's been a long time since I've messed with this phone, so I don't remember what mods/images/etc in my Mega repo are functional or not. Anything contained within this zip, FLASH AT YOUR OWN RISK.
/disclaimer

Infinix smart 5 x657

Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks

I
Gentleman101 said:
Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks
Click to expand...
Click to collapse
I have been searching for it's twrp but have not been able to get it so incase you do inform me please

Hello, I've noticed that the [twrp of infinix hot 2 ](https://eu.dl.twrp.me/d5110/) does work on smart infinix 5 X657C .. Try it, It might work.
I couldn't get root access yet using Magisk, but this is literally my first time doing this so there's a good chance I'm doing something wrong.

actually after trying to flash the image I'm now stuck in an infinite looping boot (which is bad because this is my mom's phone and now I'm in trouble).

Gentleman101 said:
Any one working on a twrp recovery for infinix smart 5 x657?
I need of it.thanks
Click to expand...
Click to collapse
Where you able to root the phone in the first place? If you were, you shouldn't have so much need for TWRP. You should be able to flash GSIs from fastboot itself.
Traditional-Wind said:
actually after trying to flash the image I'm now stuck in an infinite looping boot (which is bad because this is my mom's phone and now I'm in trouble).
Click to expand...
Click to collapse
Trying to flash what image: the stock image of or custom one?

Traditional-Wind said:
Hello, I've noticed that the [twrp of infinix hot 2 ](https://eu.dl.twrp.me/d5110/) does work on smart infinix 5 X657C .. Try it, It might work.
I couldn't get root access yet using Magisk, but this is literally my first time doing this so there's a good chance I'm doing something wrong.
Click to expand...
Click to collapse
is x657 the same as x657C? if not, whats the difference

VicKrypt said:
Trying to flash what image: the stock image of or custom one?
Click to expand...
Click to collapse
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.

MrKonic said:
is x657 the same as x657C? if not, whats the difference
Click to expand...
Click to collapse
according to what I found online (i.e. https://www.mobilesum.com/mobile/infinix-smart-5) the only difference is the camera. IDK if that will affect something related to the firmware or the boot image (If your intention is the same as mine, which is to root the phone).
But I assume (and I hope) they're both the same on every other level (nothing else is mentioned so if there's any other differences, only the company knows).

Something to note. The phone asked me to send a bug report twice. And gave me the share dialogue (meaning that I can send it to whomever I choose). I sent them to myself using whatsapp. And now, I'm saving a copy of 2 bug report that I assume they should be sent to the company (seems like the bug report was produced by the system). AFAIK it's useless, but just in case. Here's the output of `tree` on linux. If someone thinks there's something useful there. I'll share it.

bt
Traditional-Wind said:
according to what I found online (i.e. https://www.mobilesum.com/mobile/infinix-smart-5) the only difference is the camera. IDK if that will affect something related to the firmware or the boot image (If your intention is the same as mine, which is to root the phone).
But I assume (and I hope) they're both the same on every other level (nothing else is mentioned so if there's any other differences, only the company knows).
Click to expand...
Click to collapse
btw, have you rooted yours?

There certainly are not any custom ROMs f
Traditional-Wind said:
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.
Click to expand...
Click to collapse
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!

VicKrypt said:
There certainly are not any custom ROMs f
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!
Click to expand...
Click to collapse
please elaborate this simply for the newbies present. including mineself

VicKrypt said:
There certainly are not any custom ROMs f
or the phone (given how unpopular it is), but I'm talking about Generic System Images. Using fastbootd and disabling AVB I believe it should be possible to change the OS and even root it!
Click to expand...
Click to collapse
I just realized that infinix smart 5 has a flashable stock ROM available online. I guess I didn't search well enough last time. Or maybe it wasn't available back then. So I bricked a phone for nothing unfortunately.
I couldn't find any (back when I wanted to do it) so I grabed a TWRP image of infinix hot 2 (because they have a similar CPU, and they're the same brand) and I tried fastboot boot instead of fastboot flash (just to try it out before flashing) it worked, but when I flashed it. The phone was bricked (beyond repair).

MrKonic said:
please elaborate this simply for the newbies present. including mineself
Click to expand...
Click to collapse
He suggested to do the same as this guide
[Guide] Unlocking Bootloader and Disabling VerifiedBoot
/* Your warranty is now void (or isn't ? who am I to judge ?) */ Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro. Thanks to barakcodam for leaking it, and Rizezky for providing a Google Drive mirror of it. Disclaimer...
forum.xda-developers.com
just with a different phone. But I assume you don't really have to care about it.
Instead, if you want to root the phone. Then here's a good video about how to do it.
When you need to download the ROM, you can get it from this link which I wish I found earlier :'(
Infinix Smart 5 X657/X657B Firmware Flash File (Stock ROM)
Android always opens the door to various possibilities such as flashing custom ROM or kernel or APK modding etc. So if you have accidentally bricked your
www.getdroidtips.com
I assume if you follow the video and use the stock ROM. You'll have a rooted infinix smart 5 by the end of the day.
Good luck (and please let me know if it worked, I'd be eager to know).

Traditional-Wind said:
There is no custom images for this phone. In fact, the firmware isn't released. So you can't nether root it nor flash a custom ROM. As I mentioned, I heard that using a similar enough twrp image (a custom one, and I mentioned the source) wasn't a success and resulted in a bricked phone. The goad was to acquire root access on the phone.
The reason that lead me to do it was because `fastboot boot` did, in fact, work. but didn't give me root access, so I thought maybe `fastboot flash` will work.
Click to expand...
Click to collapse
I've seen the firmware on a couple of sites bro

MrKonic said:
please elaborate this simply for the newbies present. including mineself
Click to expand...
Click to collapse
Talking about root, with the correct firmware (and techniques) there shouldn't be any reason why the phone would be non-root-able. There's no official TWRP for the device and I haven't seen anyone port one for it, so going the TWRP way would most likely cause a brick. But after patching the boot.img from the correct firmware and disabling AVB by flashing the VBMeta (which most people ignore), patched_boot should be flashable in fastbootd if not in fastboot.
Talking about custom ROMs, there are no custom ROMs for the device (just like there aren't for the Infinix Hot 8, Smart 3 Plus, Hot 10 Play, e.t.c), but a lot of people have successfully flashed GSIs. Generic System Images are pure AOSP code that run on Trebllized devices. You can do more research on GSIs yourself.

Traditional-Wind said:
He suggested to do the same as this guide
[Guide] Unlocking Bootloader and Disabling VerifiedBoot
/* Your warranty is now void (or isn't ? who am I to judge ?) */ Finally, we got a shiny DeepTesting.apk that compatible with Realme 6 Pro. Thanks to barakcodam for leaking it, and Rizezky for providing a Google Drive mirror of it. Disclaimer...
forum.xda-developers.com
just with a different phone. But I assume you don't really have to care about it.
Instead, if you want to root the phone. Then here's a good video about how to do it.
When you need to download the ROM, you can get it from this link which I wish I found earlier :'(
Infinix Smart 5 X657/X657B Firmware Flash File (Stock ROM)
Android always opens the door to various possibilities such as flashing custom ROM or kernel or APK modding etc. So if you have accidentally bricked your
www.getdroidtips.com
I assume if you follow the video and use the stock ROM. You'll have a rooted infinix smart 5 by the end of the day.
Good luck (and please let me know if it worked, I'd be eager to know).
Click to expand...
Click to collapse
I did not suggest you do exactly what was done in that video. The method may vary slightly for MTK devices. It'd be more similar to this (for rooting)
https://www.google.com/url?sa=t&sou...o7QBegQIBRAB&usg=AOvVaw1dN51TuGa6a9LA07Nota-q
For flashing GSIs it'd be similar to this
How to install GSIs on dynamic partition devices

Traditional-Wind said:
I just realized that infinix smart 5 has a flashable stock ROM available online. I guess I didn't search well enough last time. Or maybe it wasn't available back then. So I bricked a phone for nothing unfortunately.
I couldn't find any (back when I wanted to do it) so I grabed a TWRP image of infinix hot 2 (because they have a similar CPU, and they're the same brand) and I tried fastboot boot instead of fastboot flash (just to try it out before flashing) it worked, but when I flashed it. The phone was bricked (beyond repair).
Click to expand...
Click to collapse
'Bricked beyond repair'? A phone is hard-bricked only if it doesn't turn on at all when plugged in, and doesn't show up on the PC or show any sign of life. Else, you'd still be able to recover it.

Alright guys I finally flashed a GSI on my Infinix Smart 5 X657C yesterday. It's Lineage OS 19 (a64 bvS), Android 12 (I'd been on XOS 6.2 Android 10 previously). I got screenshots
{
"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"
}
to prove that it's possible to root the device, if done correctly. I'm yet to flash phh-Magisk and orange-state disabler anyway (I wasn't sure A12 would even work in the first place)

VicKrypt said:
Alright guys I finally flashed a GSI on my Infinix Smart 5 X657C yesterday. It's Lineage OS 19 (a64 bvS), Android 12 (I'd been on XOS 6.2 Android 10 previously). I got screenshots
View attachment 5642989 57c View attachment 5642991 View attachment 5642999 View attachment 5643001 View attachment 5643003 View attachment 5643005
to prove that it's possible to root the device, if done correctly. I'm yet to flash phh-Magisk and orange-state disabler anyway (I wasn't sure A12 would even work in the first place)
Click to expand...
Click to collapse
what's the process please
can you write down the steps
but mine isn't X657c

General OP9 (LE2117.11.C18) T-MOBILE Stock Boot.img && Root [No Firmware Decrypt] EASYYYYY!!

Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the
{
"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"
}
easy way all right?

NishiMoon said:
Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the View attachment 5675937 easy way all right?
Click to expand...
Click to collapse
No need to wait for months to get any image. You can use msm read back. F8 when it opens.( oneplus )password and read back the images you want to your C/drive.

Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18

NishiMoon said:
Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18
Click to expand...
Click to collapse
I have been looking for a way to do this for my LE2117 for so long could you. Type a quick walk through on your method with EDL and Terminal or I can just try with the MSM Tool Readback I just found that out as well.

NishiMoon said:
Was able to get T-Mobile's OnePlus 9 stock boot image c18. Without having to decrypt firmware OTA. It's been months ever since Android 12 came out that I've been scouring for a stock boot image so I could root my OnePlus 9. All I ever found was 1 + 9 pro or use any regions boot image it will work but I couldn't do it I couldn't take the risk of possibly soft freaking or breaking my phone. So all this work all this work all this work and I finally figured it out and it was way way easier than it should have been for how much time and effort I had done to research this. I literally was able to pull my boot image then back up all my partitions and the matter of 10 minutes on top of hatching the boot image and rooting my phone and passing the safety net. I honestly didn't think it could be done because T-Mobile has their firmwares on lockdown tighter than Bill Gates wallet. If anyone would like to know how I did this or anybody would like to get a copy of the stock boot image for le2117 c18 send me a message and I'll send you the file or I will invite you on the easy process of going through and pulling your own image and your own partitions without the help of somebody else's or a different firmwares or decrypting OTA let's do this the View attachment 5675937 easy way all right?
Click to expand...
Click to collapse
Any Link to this Stock Boot.img ?

Let me see if I can find it in my files

mattie_49 said:
No need to wait for months to get any image. You can use msm read back. F8 when it opens.( oneplus )password and read back the images you want to your C/drive.
Click to expand...
Click to collapse
Do I Need ROOT to do this on a T-Mobile OP9 ?
( seems too easy...)

barguybrady said:
Do I Need ROOT to do this on a T-Mobile OP9 ?
( seems too easy...)
Click to expand...
Click to collapse
No

NishiMoon said:
Or you could enter edl no need for msm. I found out that using terminal while in edl is far superior.
I'm just happy I can give the LE2117 stock boot.img out since I have yet to see it anywhere on xda or the web yet. Let alone a boot.img for recent update c.18
Click to expand...
Click to collapse
So...
Are you gonna offer any further supporting details, links, comments, or such about using EDL mode?
I cannot find any list of Commands, at least for a Linux Shell ?

barguybrady said:
So...
Are you gonna offer any further supporting details, links, comments, or such about using EDL mode?
I cannot find any list of Commands, at least for a Linux Shell ?
Click to expand...
Click to collapse
I don't know anything about Linux . I mentioned msm read back to pull images from what build your using. And how to use and password. One must partially find their own way eventually. We all have Google , I know there is info on what I shared.

mattie_49 said:
I don't know anything about Linux . I mentioned msm read back to pull images from what build your using. And how to use and password. One must partially find their own way eventually. We all have Google , I know there is info on what I shared.
Click to expand...
Click to collapse
Yes. I had one last time to access a Win 10 computer, late last night.
Using the MSM readback mode is Ridiculously EasY!
( maybe That's why some of these Forums have gotten quiet lately..? With Readback, getting ANY boot.img is almost easier than other methods...)
With root & magisk, I'm All Set !
May The Force Be With You All !

barguybrady said:
Yes. I had one last time to access a Win 10 computer, late last night.
Using the MSM readback mode is Ridiculously EasY!
( maybe That's why some of these Forums have gotten quiet lately..? With Readback, getting ANY boot.img is almost easier than other methods...)
With root & magisk, I'm All Set !
May The Force Be With You All !
Click to expand...
Click to collapse
If your into flashing builds may I suggest Pixel Extended here in the threads. Surely nice.

mattie_49 said:
If your into flashing builds may I suggest Pixel Extended here in the threads. Surely nice.
Click to expand...
Click to collapse
Hah !!
I was thinking about That One !
Bought the OP9 for the camera - and after 19 months on Lineage, with g-Cam & Open Cam, I was contemplating switching to Pixel Ext for it's advertised camera compatibility...
But, I doubt I'll keep this phone for much longer, mostly due to All the Issues that brought me here in the first place, carrier branded.... yadda, yadda, yadda....
SO, with Root, I think I'll keep using OOS, handle the Updates from t-MO as they come along, and Every Time I get Frustrated at this thing - use that as a reminder to Buy an International and Unlocked Phone from my Guys In Chicago....and run what-ever I wish, in any way I wish - WithOut Advertising or Bloat ! !

barguybrady said:
Hah !!
I was thinking about That One !
Bought the OP9 for the camera - and after 19 months on Lineage, with g-Cam & Open Cam, I was contemplating switching to Pixel Ext for it's advertised camera compatibility...
But, I doubt I'll keep this phone for much longer, mostly due to All the Issues that brought me here in the first place, carrier branded.... yadda, yadda, yadda....
SO, with Root, I think I'll keep using OOS, handle the Updates from t-MO as they come along, and Every Time I get Frustrated at this thing - use that as a reminder to Buy an International and Unlocked Phone from my Guys In Chicago....and run what-ever I wish, in any way I wish - WithOut Advertising or Bloat ! !
Click to expand...
Click to collapse
Fyi latest 5.7 PE has fully functional Oos cam. All video modes working perfect like stock. Slo-mo ,4k 8k. I'm real picky and always msm back to stock. I've def found a home.

mattie_49 said:
Fyi latest 5.7 PE has fully functional Oos cam. All video modes working perfect like stock. Slo-mo ,4k 8k. I'm real picky and always msm back to stock. I've def found a home.
Click to expand...
Click to collapse
That's quite AN Endorsement !

[ROM][UNOFFICIAL][11][ARM64] LineageOS 18.1 for Amazon Fire HD 10 (maverick/9th gen)

{
"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"
}
Disclaimer
Code:
/*
* Your warranty is... still valid?
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are the one choosing to make these modifications.
*/
IMPORTANT
This ROM is only for the Amazon Fire HD 10 2019 (maverick) Do not try to flash it on any other device.
This ROM requires the temporary bootloader unlock found here. Read the instructions carefully and come back once you have a working temporary unlock.
This thread will be updated should another unlock method be available.
This ROM requires that you be on the 7.3.1.0 launch firmware. If you have temp unlocked your device, you should already be on this firmware.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
This is a custom build of LineageOS for the Amazon Fire HD 10 9th generation (maverick) which is 64-bit, allowing you to run 64-bit applications and benefit from better performance, unlike the stock OS which is 32-bit.
Working
Audio
Bluetooth
Camera
DRM L1 (playback not tested)
DT2W (double-tap-to-wake)
Media Playback (Hardware OMX)
Sensors
SDcard
USB (MTP, PTP, etc)
Wi-Fi
Not Working
SELinux is Permissive
Deep Sleep (?)
Hotspot
Notes
The stock gallery app has some issues playing media which is higher than 1920x1080, if you face this issue please try a third-party gallery app.
If you have flashed GApps, you should wait for the device to "settle" after completing setup wizard. During the first 10-ish minutes of use, the tablet could heavily lag and freeze.
Since this is a beta build, you should be prepared to face bugs and issues, along with possible stutters and lags.
You are free to use any recovery to flash this ROM, however, I recommend using the attached recovery (Lineage Recovery) to flash this ROM in order to avoid any potential issues.
How to Flash?
Spoiler: Flashing Instructions
It's important to note that you will have to boot your device with mtkclient every time you reboot!
First of all, boot the device into fastboot mode. Once you see something like => FASTBOOT mode... appear on your devices display, you can flash the Lineage Recovery image with the following fastboot command:
Code:
fastboot flash recovery lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick-recovery.img
fastboot reboot recovery
This flashes the custom recovery to the devices recoverypartition, and then tells it to reboot into recovery mode.
To make sure the device boots into recovery upon the next reboot, hold the volume up button on the device after sending the preloader again with mtkclient.
DO NOT let the device boot back into FireOS at this point, as it will flash the old recovery back to the device, and you will need to start from the beginning again.
The unlocked LK indicates which mode the device will boot into, you should see something like lk boot mode = 2 on the devices display, meaning it is booting into recovery mode.
Once in Lineage Recovery, tap on "Apply Update", and then tap on "Apply from ADB". There are also options to apply updates from external storage if you wish.
Now, it's time to actually install the ROM. We are going to sideload the Lineage ZIP to our device using adb with the following command.
Code:
adb sideload lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick.zip
At this point, all you need to do now is wait for the flashing process to complete.
Once finished, you will be brought back to the apply update menu. Simply press the back button to go back to the main menu.
Now, tap on factory reset and tap on the option Format data/factory reset. This is going to erase all of the old FireOS userdata from the device.
If you do not wish to install GApps, skip to the finishing up process below the GApps flashing instructions.
Optional: Flashing GApps
To install Google Services to your new ROM, you will want to start by downloading the recommended GApps package (see Downloads section).
Once downloaded, you can follow a similar process that you did for installing the ROM ZIP.
Tap on "Apply Update" again, and "Apply from ADB".
Once you have done that, you can sideload the GApps package with the following command:
Code:
adb sideload MindTheGapps-11.0.0-arm64-XXXXXXXX_XXXXXX.zip
If you wish to install other addons (e.g. Magisk), repeat the same steps, substituting the GApps package file name with the Magisk zip file name.
Finishing Up
Once you have done everything you need to do in Lineage Recovery, it's time to boot into the new ROM.
It's important to note that the reboot system now option does not work correctly, so follow these steps to workaround it.
Tap on Advanced, and then tap on Reboot to bootloader.
Once you see => FASTBOOT mode... on the devices display once again, type the following fastboot command to reboot.
Code:
fastboot reboot
After a short while, you should see the LineageOS boot animation on your device. First boot usually takes 5-10 minutes, especially if you have installed Google Services.
Wait for the device to boot and you should be presented with the setup wizard. Enjoy!
Downloads
ROM
Recommended GApps
Source Code
Device
Kernel
Vendor

Screenshots attached below.

Reserved #3

Amazing job.

@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
The device tree is currently private for whatever reason. I will let bengris know through Telegram.

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
Hey, currently the new device tree is not open source yet, I will make it open source once I fix the remaining issues (mainly getting SELinux Enforcing). Kernel tree is open due to the GPL license.

Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?

I will pay $1,000 or more to anyone who can open bootloader to the new systems amazon

jasonjohn95 said:
Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?
Click to expand...
Click to collapse
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.

Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate

ＤＥＭＯＮ said:
Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate
Click to expand...
Click to collapse
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...

Michajin said:
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...
Click to expand...
Click to collapse
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?

ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....

ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
that being said, i hope you have updates disabled, because there might be another root option coming.

bengris32 said:
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?
Click to expand...
Click to collapse
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops

Michajin said:
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....
Click to expand...
Click to collapse
Thank you very much for your answers, I don't know when I bought the Tablet, I forgot, but I imagine that it is possible to downgrade to Fire OS 7.3.1.0 in some way which I don't know, apart from I don't understand the tutorials that I found on XDA, I really have 2 days and my head hurts a lot because I do not understand the explanations of the users, if there was even the slightest possibility that you could contact me and tell me step by step what I should do and I will show you with screenshots how I progress and do everything to have a guide, I promise to pay you if I succeed in installing this ROM by PayPal

jasonjohn95 said:
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops
Click to expand...
Click to collapse
Let's try to dump pstore from the device when it's trying to boot then.
Wait for the device to reboot after being on the amazon logo, immediately on the next boot up, go into recovery mode. Then, enable ADB.
You can dump pstore with the following adb command (adbd should run as root in recovery):
adb pull /sys/fs/pstore
Hopefully there should be some logs in there which you can attach here, if not, keep retrying until you get something in there. If you are 100% nothing is being dumped to pstore, just let me know.
As a side note, I am using the kernel source and blobs from the 7.3.2.7 firmware, so I'm not sure why it's not seeming to boot on later firmware.

bengris32 said:
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.
Click to expand...
Click to collapse
It works!
Completed a Lineage build using the info on "amazon-mt8183-devs" repo - now installed & working fine.
Many Thanks