Question Anyone Willing To Build TWRP For Barbet? - Google Pixel 5a

I've tried multiple times, but keep hitting errors...I'm not super familiar with building TWRP from source, but I'm hoping someone here could possibly help out and put together an unofficial twrp for barbet?

having a working unofficial twrp for this device would be a definite plus.

So I'm guessing it's fair to say that this claim is fake then, right?

There is an official version for the 5 now. So it should be possible.

MrPolite said:
There is an official version for the 5 now. So it should be possible.
Click to expand...
Click to collapse
I wonder if the pixel 5 version is compatible with pixel 5a.

I've tried multiple times, but keep hitting errors.

we need the wizard @Captain_Throwback to make an unofficial twrp. he's made a lot of unofficial twrps over the years and does a damn good job at doing it.
​

rchris494 said:
we need the wizard @Captain_Throwback to make an unofficial twrp. he's made a lot of unofficial twrps over the years and does a damn good job at doing it.
​
Click to expand...
Click to collapse
Unless someone buys me one, I won't be doing that. I don't build for devices I don't have anymore, unless they're essentially similar to a device that I do. And this device doesn't fit that scenario. I'm sure at some point a dev will come along to help. You'll just all have to be patient.

saibotnoob said:
So I'm guessing it's fair to say that this claim is fake then, right?
Click to expand...
Click to collapse
Yep. I think all they do is copypasta other tutorials and make money with ad revenue.

I tried to build it, but I ran into issues. anyone have any idea the proper repos I'm supposed to use? also, when getting to the blobs point, extractblobs script is missing from lineage repos. (I also tried to build for android 12
Point me in the right direction!

eriklion said:
I tried to build it, but I ran into issues. anyone have any idea the proper repos I'm supposed to use? also, when getting to the blobs point, extractblobs script is missing from lineage repos. (I also tried to build for android 12
Point me in the right direction!
Click to expand...
Click to collapse
You should use the official Google device repo for A11, along with the minimal manifest for TWRP. Then just follow the same process as the bonito repo to retrofit it for TWRP.
The easiest way to extract blobs is to do so from the factory images.
EDIT: If I can find some time I may help with this, as long as you're willing to do the building and testing, I can probably create a mostly complete device tree for you to start with.

Someone want to see if this TWRP boots?
twrp-3.6.0_11-0_CPTB-20211220-01-barbet.img
drive.google.com
No idea if it'll boot or if touch or vibration will work or anything, but it's a first attempt.

Captain_Throwback said:
Someone want to see if this TWRP boots?
twrp-3.6.0_11-0_CPTB-20211220-01-barbet.img
drive.google.com
No idea if it'll boot or if touch or vibration will work or anything, but it's a first attempt.
Click to expand...
Click to collapse
Doesn't boot, stuck at Google logo. Just FYI the official twrp-3.6.0_11-0-redfin.img for Pixel 5 boots beyond Google logo and gets stuck at TWRP splash screen with ADB ability... Running A12.

nijel8 said:
Doesn't boot, stuck at Google logo. Just FYI the official twrp-3.6.0_11-0-redfin.img for Pixel 5 boots beyond Google logo and gets stuck at TWRP splash screen with ADB ability...
Click to expand...
Click to collapse
Are you sure it's not booting? Did you confirm that adb isn't working by checking adb devices while on the logo screen?

Captain_Throwback said:
Are you sure it's not booting? Did you confirm that adb isn't working by checking adb devices while on the logo screen?
Click to expand...
Click to collapse
Absolutely sure, stuck at Google logo before getting to TWRP at all so ADB doesn't see any devices.

nijel8 said:
Absolutely sure, stuck at Google logo before getting to TWRP at all so ADB doesn't see any devices.
Click to expand...
Click to collapse
Can you get a recovery log and logcat from the redfin build so I can see why that one isn't working? If that boots then it may be relatively easy to get it working on this device. That's probably the best place to start.

Captain_Throwback said:
Can you get a recovery log and logcat from the redfin build so I can see why that one isn't working? If that boots then it may be relatively easy to get it working on this device. That's probably the best place to start.
Click to expand...
Click to collapse
Sure...

Just booted into official twrp for Pixel 5 with no issue
Edit: magisk rooted, android 11
More editing as I am testing:
The first thing I tried to do was boot into fastboot through TWRP. It goes back to TWRP screen and then back to TWRP, never entering any fastboot.
Okay, I did not plan this out well at all lol.
Just Completed Factory Flash to Android 11 through the Android Flash Tool
Booted into Pixel 5 TWRP
Did not get an 'Allow Modifications Pop Up.
Tried to run fastboot through TWRP and TWRP when back to its logo and than returned to the menu.

SolGonNet said:
Just booted into official twrp for Pixel 5 with no issue
Edit: magisk rooted, android 11
More editing as I am testing:
The first thing I tried to do was boot into fastboot through TWRP. It goes back to TWRP screen and then back to TWRP, never entering any fastboot.
Okay, I did not plan this out well at all lol.
Just Completed Factory Flash to Android 11 through the Android Flash Tool
Booted into Pixel 5 TWRP
Did not get an 'Allow Modifications Pop Up.
Tried to run fastboot through TWRP and TWRP when back to its logo and than returned to the menu.
Click to expand...
Click to collapse
Did you manage to flash something with twrp?

I have interest in this process as well. I see that Magisk recommends TWRP to install, and it seems that may be require for SafetyNet verification. I am fairly unclear on that point though: is TWRP the only reasonable way to use magisk? And, also, does a custom ROM not automatically provide a user with root access? Why is Magisk needed in that case?

Related

[RECOVERY] TWRP Recovery 2.8.7.0 - Apollo/Thor

Hello All,
NOTE: You should unlock your bootloader.
These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.
WARNING:
- Be sure to have a working /system partition before proceeding with installation.
Installation
- Ensure you are running stock firmware .3.2.3.2
- Obtain Root
- Copy the recovery image to the root of your sdcard
- Flash the recovery image by issuing the following commands:
Code:
adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Download
- Apollo Recovery Image
- Thor Recovery Image
Thanks
- @vortox for the exploit
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
r3pwn said:
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
Click to expand...
Click to collapse
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
vortox said:
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
Click to expand...
Click to collapse
Ah.
I wrote the recovery on my apollo device which is running 14.3.2.3.2_user_323001720 version and it appears to work flawlessly. I booted into recovery (TWRP) successfully and rebooted the system successfully as well. Awesome!
Thanks for the feedback, glad it's all working
I haven't got a device at the moment to try it out on.
Sent from my Kindle Fire HDX using Tapatalk
Thanks ggow. Could we expect CM roms soon from your new release?
Working on 14.3.1.0
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
Hello tuanda82,
It depends on Amazon, my unlocked Apollo stopped working so they sent me a new one but came pre-installed with 4.5.2.
They have refused to downgrade me back to the old firmware. And after a lot of to and fro they agreed to replace it again .
I hope I have luck with the new device been on the required firmware.
But yes I definitely would like to make such a release.
dangerous
jeryll said:
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
Click to expand...
Click to collapse
I would not be trying interchang eROMs and or backups ppluntil certain things are verified by our developersgosh it only takes a few minutes to understand that one is built for locked bootloader the other one bypasses and they both flash completely different partitions and have different installation scripts.you're just asking to be one of the ignorant whiners on the sidelines while we have fun ..stuck with your brick. be patient guys this is all new stuff if you can't afford to be a developer then I devise you let somebody else take the risk
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
tbm13 said:
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
Click to expand...
Click to collapse
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
r3pwn said:
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
Click to expand...
Click to collapse
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Håvi said:
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Click to expand...
Click to collapse
Flash the rollback image to stock slot. This will then enable you to get back to 3.1.0
ggow said:
Flash the rollback image to stock slot. You need to be on stock version < 3.2.4.[/QUOT
Edit, found answer in OP
Click to expand...
Click to collapse
I was able to roll back to 3.1.0 and installed twrp. I was able to make a backup and successfully restored the backup. However after about an hour I came back to my kindle an noticed it updated itself to 4.1.1. I was under the impression with recovery installed any new updates would . Not be able to install. Now when I try to boot into recovery it on l y boots kindle recovery not twrp.
Sent from my KFAPWI using Tapatalk
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
GSLEON3 said:
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Click to expand...
Click to collapse
Thanks gsleon but don't rob your mom
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
ggow said:
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
Click to expand...
Click to collapse
Crossing fingers

Need TWRP or CWM recovery to root Blackshark Helo!

It's been months since this device is launched, but there are no official or unofficial recovery or custom ROMs released till now. I need to root the device so that I can enjoy features like Viper FX and other Magisk modules. I have searched a lot of forums but there seems to be no thread regarding the rooting process of Xiaomi Blackshark Helo.
The device is a great gaming phone with very high specs. Surely, a lot of custom ROMs can be ported for this device since its OS is close to stock android (JOYUI). Is anyone willing to port custom recovery for this device? It will be really appreciated
Blackshark Helo users please rate this thread to show awareness of this device to the developers!
The twrp is not needed to root your phone
mauronofrio said:
The twrp is not needed to root your phone
Click to expand...
Click to collapse
But twrp is needed to flash magisk, isn't it?
mtayyabali said:
But twrp is needed to flash magisk, isn't it?
Click to expand...
Click to collapse
Not true, you can manually patch the boot.img, then boot it and make the root through magisk manager
I know that method but there is no boot.img available for black shark helo yet, so how do I even patch it? Since this device is becoming popular why isn't there any ROM or recovery available yet, I wonder.?
mtayyabali said:
I know that method but there is no boot.img available for black shark helo yet, so how do I even patch it? Since this device is becoming popular why isn't there any ROM or recovery available yet, I wonder.?
Click to expand...
Click to collapse
i have patched it for you
kanded said:
i have patched it for you
Click to expand...
Click to collapse
can you give tutorial how to root blackshark helo without twrp?
kanded said:
i have patched it for you
Click to expand...
Click to collapse
Thanks, I will get it a try. How did u manage to get stock boot img?
Saintrheno said:
can you give tutorial how to root blackshark helo without twrp?
Click to expand...
Click to collapse
the same way using magisk.
mtayyabali said:
Thanks, I will get it a try. How did u manage to get stock boot img?
Click to expand...
Click to collapse
by learning, and being not lazy to read from first page to last page.
i have flash your boot patched with root but my wifi il locking off and I can not activate it anymore
I changed the slot on B and it seems to rework everything, then I tried to go over A and extract the boot B and patch with magisk, I tried it with fastboot boot, but it remains the usual problem, no wifi no audio and no microphone
Sime90ita said:
i have flash your boot patched with root but my wifi il locking off and I can not activate it anymore
Click to expand...
Click to collapse
use your simcard. then update the magisk if its needed tobe updated. then, go to instal. and choose direct install. then reboot.
remember, fastboot boot is temporary. fastboot flash is permanent. so no worry if you think you lose wifi, after reboot, it will be fine. let me know.
woooo thanks kanded, now everything works perfectly and I also root! I think I will do a post with the guide on how to root
Is it possible to get twrp for this device? That will makes things easier and little bit safer..
mmmm, yes I'm going to work on twrp but still I'll make my boot patch available, which makes the phone fully functional but first I need someone with a black shark helo without root that tests my boot
I tested twrp for black shark, but the touch-screen does not work, surely it must be modified and adapted for black shark helo but I'm not able
Sime90ita said:
I tested twrp for black shark, but the touch-screen does not work, surely it must be modified and adapted for black shark helo but I'm not able
Click to expand...
Click to collapse
i dont know which twrp you tested, but if its mauro's twrp, best believe, our display is different, ips and amoled, but somehow, i tried the twrp into blackshark helo, and it went well, just the flipped things. but all functions still work as it should be.
search for mauronofrio's twrp for blackshark 1st gen. and try to fastboot boot it.
anyway, rooting is easy without twrp, i choose without twrp for rooting. but if you're more into flashing any flashable zips, lets say the decryptingzip, twrp is your choice.
happy bootlooping everyone.
kanded said:
i dont know which twrp you tested, but if its mauro's twrp, best believe, our display is different, ips and amoled, but somehow, i tried the twrp into blackshark helo, and it went well, just the flipped things. but all functions still work as it should be.
search for mauronofrio's twrp for blackshark 1st gen. and try to fastboot boot it.
anyway, rooting is easy without twrp, i choose without twrp for rooting. but if you're more into flashing any flashable zips, lets say the decryptingzip, twrp is your choice.
happy bootlooping everyone.
Click to expand...
Click to collapse
I tried mauronofrio's twrp, but touchscreen was really not working.. I am using CN variant by the way..
mtayyabali said:
I tried mauronofrio's twrp, but touchscreen was really not working.. I am using CN variant by the way..
Click to expand...
Click to collapse
touchscreen is working. its just flipped and upside down, left is right, right is left, up is down, down is up.
and those doesnt mean touchscreen not working or really not working.
kanded said:
touchscreen is working. its just flipped and upside down, left is right, right is left, up is down, down is up.
and those doesnt mean touchscreen not working or really not working.
Click to expand...
Click to collapse
I tried touching everywhere but it there was no response, i am on the screen where you have to enter password for decrypting data.

[RECOVERY][UNOFFICIAL] TWRP 3.5.2_10 for Moto G 5G (kiev)

DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff.
What has been tested and works:
- Touchscreen
- Installing flashable zips
- Flashing images
- Flashing the recovery itself
- Creating backups (to internal storage, sdcard or OTG)
- Restoring from backups
- Terminal
- adb
- Rebooting to system, recovery, bootloader, ...
That doesn't mean that other things don't work. It just means they weren't tested yet. As I proceed with testing I will update the above list.
Usage (without flashing)
Bash:
# boot to bootloader
adb reboot bootloader
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
If you want to flash you have 2 options
Bash:
# boot to bootloader
adb reboot bootloader
# ********* OPTION 1 *********
# Flash to active slot (replace <slot> with either a or b, depending on the current active slot).
# Of course, you can flash to both by first specifying a and then b.
fastboot flash recovery_<slot> twrp-3.5.2_10-kiev.img
# ********* OPTION 2 *********
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
# Once in the recovery, copy the twrp image file to your internal storage
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
# Then go to Install, then Install image, select the twrp image you pushed before.
# Then select the Recovery partition and swipe to confirm.
# Before swiping you will have the option to decide if you want to flash to both slots.
Download: google drive
Sources will be posted in due time and this post will be updated accordingly.
Built for: Motorola Moto G 5G (Motorla One 5G Ace)
My model: XT2113-3 (kiev)
Credits
To the guys over here for the device tree, especially to SyberHexen for providing me with useful information.
reserved
reserved
Great!
Tested on my Moto G 5G XT2113-3. Seems to work properly. Good job. Awaiting to flash it.
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
It won't brick. I used it. (only once)
clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
h3xmind said:
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
Click to expand...
Click to collapse
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Tomspector said:
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Click to expand...
Click to collapse
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me.
I will do it now,
I would help
h3xmind said:
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me
Click to expand...
Click to collapse
I will do it now
Tomspector said:
I will do it now,
I would help
I will do it now
Click to expand...
Click to collapse
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Tomspector said:
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Click to expand...
Click to collapse
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
h3xmind said:
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
Click to expand...
Click to collapse
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Ok, thanks for your help. I won't be testing anything tomorrow. I have a day off with my family
Tomspector said:
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Click to expand...
Click to collapse
Should be here: https://mirrors.lolinet.com/firmware/moto/kiev/official/
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Anyway, I flashed it by doing the following:
Bash:
# boot to bootloader
adb reboot bootloader
# boot to twrp
fastboot boot twrp-3.5.2_10-kiev.img
# push the recovery image to the Download folder
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
Once inside the recovery I went to Install, then Install image, once I selected the twrp-3.5.2_10-kiev.img file that I previously pushed, twrp asked me on which partition I would like to flash it. I selected the Recovery partition. (Although I ask myself why does the phone have a separate recovery partition if it is an A/B device. I still have to figure this out. Normally in these devices one would have to pack the recovery into the boot imate and than flash the whole thing to the boot partition.)
Then I rebooted to recovery and it took me directly to twrp. The problem, however, is that the touch screen didn't work anymore. So, I guess I got myself some extra work But it'll be fun. I can't wait to put my hands on it.
Did you manage to find the rom for your phone?
PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
I tried Hexen's recovery. It's easily fixable to make the touch work. It took me two minutes. I'll let the guys working on it know how to do it. But first I have to figure out why does the touch screen stop working once you flash the recovery.

Question SM-X205 32/3 How to install GSI?

Hello everyone. Can You please explain how to install GSI to SM-X205? I'm new to fastboot methods. I can't find proper TWRP for this particular model. I have achieved to unlock bootloader which took two steps (In old Android phone it was just easy with switch in developer options). I have installed TWRP from SM-X200 but it's not working. Restored everything by flashing Official Firmware. The main reason why I'm going to this is shortage of storage. I want to format external SD Card as Internal which is not allowed in new Andoirds. Thank you before hands and respect for ones who contribute their knowledge for community.
If TWRP is not available for your device, you can try using this to enable fastbootd. It won't have any TWRP specific features though.
As far as installing a GSI, you simply flash the system.img to /system. It's that simple. Make sure you wipe data.
SukhrobR said:
Hello everyone. Can You please explain how to install GSI to SM-X205? I'm new to fastboot methods. I can't find proper TWRP for this particular model. I have achieved to unlock bootloader which took two steps (In old Android phone it was just easy with switch in developer options). I have installed TWRP from SM-X200 but it's not working. Restored everything by flashing Official Firmware. The main reason why I'm going to this is shortage of storage. I want to format external SD Card as Internal which is not allowed in new Andoirds. Thank you before hands and respect for ones who contribute their knowledge for community.
Click to expand...
Click to collapse
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Piggybacking on this thread to drop some much needed general resources. I installed LineageOS on my s5e last year but struggled to find resources w/ GSI.
I appreciate all the hard work that the devs do, and typically documentation is not their strong suit, so in the future, maybe those of us who benefit from their work can create clearer documentation to spread around the burden a bit:
FAQ that covers topics like what is Treble, what is GSI, what is the naming conventions for GSI files: https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
Where as example of a GSI I can download : https://github.com/phhusson/treble_experimentations/releases/tag/v416
What should I know going in: Android 13 versions of GSI still have a few compatibility issues as per the first post in this thread. Android 12 is functioning 100% correctly.
Where can I see a more complete list of the GSI options available to me: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
w00tnezz said:
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Click to expand...
Click to collapse
I have followed all the instructions. But I'm stuck at stage where rebooting to fastboot from TWRP. Touchscreen stops to respond and I can't enable ADB.
SukhrobR said:
I have followed all the instructions. But I'm stuck at stage where rebooting to fastboot from TWRP. Touchscreen stops to respond and I can't enable ADB.
Click to expand...
Click to collapse
You don't need to enable ADB. When the screen says "Entering fastboot mode" then you are connected. You can check this by entering "fastboot devices" from your PC.
lewmur said:
You don't need to enable ADB. When the screen says "Entering fastboot mode" then you are connected. You can check this by entering "fastboot devices" from your PC.
Click to expand...
Click to collapse
Device list is empty after entering fastboot mode in twrp
SukhrobR said:
Device list is empty after entering fastboot mode in twrp
Click to expand...
Click to collapse
Do you have the latest version of the Samsung USB drivers? Earlier versions don't have the fastboot driver.
lewmur said:
Do you have the latest version of the Samsung USB drivers? Earlier versions don't have the fastboot driver.
Click to expand...
Click to collapse
Yes I do. I think it dependable on firmware version.
w00tnezz said:
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Click to expand...
Click to collapse
Does this allow me to use this (https://forum.xda-developers.com/t/...0-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691) for my SM-X205?

Should i use MediatekBootloaderUnlock or is it patched?

So, i've rooted my xiaomi note 5 with magisk, and i wanted to do the same with my main phone, and now i cant unlock my phone because i dont want my data lost (the apps are the most important and i have all my other data backed up) and i came across mediatekbootloaderunlcok and im just wondering is it patched or does it still work? because if it works then im definitely rooting my phone. id appreciate it if any of you guys answered my question
thanks
Just use mtkclient
boofiboi said:
Just use mtkclient.
https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
the hell is that lol
boofiboi said:
Just use mtkclient.
https://github.com/bkerler/mtkclient
Click to expand...
Click to collapse
also it worked and my phone is unlocked now but theres an issue, when i flash orangefox it just cant go to recovery then vibrates and goes back to the OS
Fixed. Its a tool that abuses mediateks BROM mode accesibility to do a bunch of stuff
SzymcioYa said:
also it worked and my phone is unlocked now but theres an issue, when i flash orangefox it just cant go to recovery then vibrates and goes back to the OS
Click to expand...
Click to collapse
Currently having the same issue. No other recovery other than Spark from BananaDroid works.
boofiboi said:
Currently having the same issue. No other recovery other than Spark from BananaDroid works.
Click to expand...
Click to collapse
R.I.P you guys.
Even TWRP doesn't work?
AltFantasy said:
R.I.P you guys.
Even TWRP doesn't work?
Click to expand...
Click to collapse
yup. it doesnt, tried it
The only TWRP version that works for me is the Dimenzino forks, but those only boot. ADB sideload crashes the recovery, decryption doesnt work thus MTP also doesnt work.
Any other recovery i try also locks me from booting before i reinstall spark.
I've been hating every second with this phone.
When i compare the experience of modding it to my old Redmi 8, this phone is such a pain.
IMEI backups
No ROM's work
No recovery's work.
Now that I have only 1 IMEI i can no longer even go back to MIUI.
boofiboi said:
Currently having the same issue. No other recovery other than Spark from BananaDroid works.
Click to expand...
Click to collapse
cant seem to find it, can you give me the link to the website?
SzymcioYa said:
cant seem to find it, can you give me the link to the website?
Click to expand...
Click to collapse
https://sourceforge.net/projects/rom-lord/files/A13/Recovery/Spark/recovery.img/download
This is the only recovery that has so far worked for me to install a ROM through sideload. Otherwise its pretty useless.
Looking at the rom-lord files, theres quite a few roms/recoveries in there, ill try to test the recoveries and let you know.
boofiboi said:
The only TWRP version that works for me is the Dimenzino forks, but those only boot. ADB sideload crashes the recovery, decryption doesnt work thus MTP also doesnt work.
Any other recovery i try also locks me from booting before i reinstall spark.
I've been hating every second with this phone.
When i compare the experience of modding it to my old Redmi 8, this phone is such a pain.
IMEI backups
No ROM's work
No recovery's work.
Now that I have only 1 IMEI i can no longer even go back to MIUI.
Click to expand...
Click to collapse
well, I mean, it's MediaTek....
you can just go port TWRP to your device by yourself, OR use GSI ROMs! (though, GSIs are very.... general, and so, they might not work with certain hardware inside your phone, because they're designed to be a one-size-fits-all solution.) even better, go make a custom ROM for your device by yourself!
boofiboi said:
https://sourceforge.net/projects/rom-lord/files/A13/Recovery/Spark/recovery.img/download
This is the only recovery that has so far worked for me to install a ROM through sideload. Otherwise its pretty useless.
Click to expand...
Click to collapse
all i want is to root my redmi 9 lol
i actually flashed this and it just still didnt do anything and just sent me to miu recovery soo.. yeah
SzymcioYa said:
all i want is to root my redmi 9 lol
i actually flashed this and it just still didnt do anything and just sent me to miu recovery soo.. yeah
Click to expand...
Click to collapse
So, I figured out how to fix SHRP and other stuff not booting.
Download the last android 11 firmware from here, get the fastboot version. Flash it and then just proceed to flash SHRP and all your roms like normal.
boofiboi said:
So, I figured out how to fix SHRP and other stuff not booting.
Download the last android 11 firmware from here, get the fastboot version. Flash it and then just proceed to flash SHRP and all your roms like normal.
Click to expand...
Click to collapse
so if i do it i can flash anything i want? sweet!
boofiboi said:
So, I figured out how to fix SHRP and other stuff not booting.
Download the last android 11 firmware from here, get the fastboot version. Flash it and then just proceed to flash SHRP and all your roms like normal.
Click to expand...
Click to collapse
but this will delete all my info right?
SzymcioYa said:
but this will delete all my info right?
Click to expand...
Click to collapse
Yes it will, back it up first
If you just want to root it, get the latest firmware from that website, extract the boot.img and patch it via the magisk app.
then just flash it via fastboot.
boofiboi said:
If you just want to root it, get the latest firmware from that website, extract the boot.img and patch it via the magisk app.
then just flash it via fastboot.
Click to expand...
Click to collapse
uh, can u fix it with any other way without needing to back up anything?

Categories

Resources