Database Info

Root Gigaset GS4

Hi guys. Is there any root method for the Gigaset Gs4? Thanks.

Anyone?

As long as you have the stock images there is.
Im currently trying to get the stock ROM in any way. If anyone has some tips please reply
Currently I'm trying to get the stock ROM using the image here: https://www.google.com/amp/s/unofficialtwrp.com/download-twrp-3-2-3-mediatek-mt6771-8-1/?amp
I hope that I can extract boot.img with it, to patch it with magisk.
Also take a look here:
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Software root method for MediaTek MT67xx, MT816x, and MT817x! So it's no big secret that not too long ago, I found a way to achieve temporary root on MediaTek chipsets. No preinstalled root solution or device unlock was needed. The tool I...
forum.xda-developers.com
Edit: I found another image for the mt6771 that might work as well but keep in mind that it is not made for the Gigaset GS 4: https://www.techswizz.com/twrp-recovery-for-cubot-note-20-pro/ DOES NOT WORK!!
As soon as I got the patched image I think you can use this bypass to flash it: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/amp/ DOES NOT WORK!!

StarMiner99 said:
As long as you have the stock images there is.
Im currently trying to get the stock ROM in any way. If anyone has some tips please reply
Currently I'm trying to get the stock ROM using the image here: https://www.google.com/amp/s/unofficialtwrp.com/download-twrp-3-2-3-mediatek-mt6771-8-1/?amp
I hope that I can extract boot.img with it, to patch it with magisk.
Also take a look here:
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Software root method for MediaTek MT67xx, MT816x, and MT817x! So it's no big secret that not too long ago, I found a way to achieve temporary root on MediaTek chipsets. No preinstalled root solution or device unlock was needed. The tool I...
forum.xda-developers.com
Edit: I found another image for the mt6771 that might work as well but keep in mind that it is not made for the Gigaset GS 4: https://www.techswizz.com/twrp-recovery-for-cubot-note-20-pro/
As soon as I got the patched image I think you can use this bypass to flash it: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/amp/
Click to expand...
Click to collapse
i managed to extract the stock boot.img and recovery.img using this guide with some modifications:
How to use Wwr MTK + SP Flash tool to backup Mediatek rom
This is a step-by-step guide on how to use Wwr MTK tool & SP flash tool to backup Mediatek (MTK) firmware. We had previously created guides on how to backup or dump firmware from a Mediatek (MTK) devi
forum.hovatek.com
things i did different:
i could not preform the ram test to determine the size of emmc_user so i just used a random length(0x3a3e00000) later on WwR told me that emmc_user should be: 0xe8f800000 i used this value to again read the emmc_user region and loaded it into WwR and continued on the rutorial.
now with this information we should be able to patch boot.img using magisk and flash it to our devices to root it.
to flash your device do the following: reboot into fastboot mode (power + volume up and select fastboot) then in a terminal type:
to unlock the bootloader:
fastboot flashing unlock
to flash an image to your device:
fastboot flash <partition> <image>
the stock images and the scatter file will follow

I managed to succesfully root my smartphone using magisk there was a single problem which is the following:
Android verified boot
you need to flash a new vbmeta image
i made my own empty vbmeta image and flashed it now its working and my smartphone is rooted

[HOW TO ROOT AND HOW TO INSTALL TWRP]
DISCLAIMER:
I will not be responsible for any damage to you device !!!!
step 1 :
make a backup of your smartphone data
step 2 :
unlock your bootloader
1. go to settings -> about phone -> click a few times on the build number
2. go to settings -> system -> developer options -> allow OEM unlocking
step 3 :
install adb and fastboot on your computer
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/ <- you can download a minimal version here
step 4 :
enable usb debugging
go to settings -> system -> developer options -> enable usb-debugging
step 5 :
open a console on your computer and do the adb and fastboot stuff
type the following commands into your cmd:
adb reboot bootloader <- this will reboot your smartphone into fastboot mode
wait until your phone enters fastboot mode
as soon as your phone entered fastboot mode type the following:
fastboot flashing unlock <- this will unlock your bootloader you have to press volume up to confirm it
then flash vbmeta and magisk patched:
fastboot flash vbmeta vbmeta_disabled.img <- this will flash the new vbmeta file
[ROOT]
fastboot flash boot magisk_patched-23000_tvNQq.img <- this will flash the new boot image
[TWRP]
fastboot flash recovery twrp.img <- this will flash the new recovery image
step 6 :
reboot your phone and reconfigure it
Youre Done!
EDIT: please download the twrp image from the official TWRP site: https://twrp.me/gigaset/gigasetgs4.html

@StarMiner99 as I'm thinking about buying it I'm glad to know it can be rooted.

bmwdroid said:
@StarMiner99 as I'm thinking about buying it I'm glad to know it can be root
Click to expand...
Click to collapse
well it was not easy to get the stock images xD

im currently also trying to port lineage os and twrp to the gigaset gs4

StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
That's good to hear.
Although if it can be rooted it might be sufficient for me to kill all not needed apps via adb and use Magisk for AFWall+.
Actually I've read about the possibility of a GS version with a better camera so I might wait a while before getting one.

well there arent any unneeded apps

[STOCK ROM + SCATTER FILES + PRELOADER]
here are the stock rom files, the scatter file and the preloader in a zip archive
1.5 GB file on MEGA
mega.nz

StarMiner99 said:
[STOCK ROM + SCATTER FILES + PRELOADER]
here are the stock rom files, the scatter file and the preloader in a zip archive
1.5 GB file on MEGA
mega.nz
Click to expand...
Click to collapse
Hey StarMiner99, is the ADUPS software updating malware in the image you uploaed still working? Could hyou please explain briefly how to flash this stock rom? I have adb and fastboot already running and a rooted device too.
Thanks a lot!

StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
any progress on this?
could i do something to help?

First of all: Thank you very much! Everything has worked so far and the device is rooted.
But I still have one question. How does the device behave when the official updates from Gigaset are installed via OTA? The GS4 reports it would have security updates. Can I install them without losing root privileges? Does anyone already have experience? Thanks in advance!

UserSven said:
First of all: Thank you very much! Everything has worked so far and the device is rooted.
But I still have one question. How does the device behave when the official updates from Gigaset are installed via OTA? The GS4 reports it would have security updates. Can I install them without losing root privileges? Does anyone already have experience? Thanks in advance!
Click to expand...
Click to collapse
I have now simply installed the June 2021 update. The good news: It worked. The slightly less good news is that you have to flash the images again. But flashing also works with the latest version and the update check tells that there are no new updates. So it seems to work.

UserSven said:
I have now simply installed the June 2021 update. The good news: It worked. The slightly less good news is that you have to flash the images again. But flashing also works with the latest version and the update check tells that there are no new updates. So it seems to work.
Click to expand...
Click to collapse
Which recovery do you use?
I've read in their forum that updating doesn't work when on TWRP.

StarMiner99 said:
im currently also trying to port lineage os and twrp to the gigaset gs4
Click to expand...
Click to collapse
Why are you not just using the LineageOS GSI?
I have LineageOS17.1 running on my GS4 since Feb. without any issues so far.

ChrisMucDev said:
Why are you not just using the LineageOS GSI?
I have LineageOS17.1 running on my GS4 since Feb. without any issues so far.
Click to expand...
Click to collapse
Is there a tutorial on how to do that?

Wolfgang-Z said:
Is there a tutorial on how to do that?
Click to expand...
Click to collapse
Here is, what I did: (on your own risk)
As far as i can remember, i did not have any issues.
Step 1: Unlock your device
1. Enable Developer Options: Tap 10x on Build-Number (Setttings -> About the phone -> Build-Number)
2. Enable Bootloader Unlocking -> activate OEM-Unlock option (Settings -> System -> (More) -> Developer-Options)
3. Enable ADB Access -> Enable USB-Debugging / ADB (Settings -> System -> (More) -> Developer-Options)
4. (Set USB-Settings (Message-Center) from "No tx" to "PTP")
5. Connect phone to usb port, grant permissions on phone and check connection with `adb devices`
6. Boot to bootloader: `adb reboot bootloader`
7. Unlock Bootloader: `fastboot flashing unlock`
Step 2: Download GSI
1. Reboot your phone and install Treble Info App
(https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=en&gl=US)
GS4 should support AB-Partitions
2. Download GSI: https://sourceforge.net/projects/andyyan-gsi/files/
For GS4: treble_arm64_bv*
Step 3: Install GSI
1. Boot to recovery: `adb reboot recovery` or Volume Down + Power
2. Wipe data
3. Wipe cache
4. Enter fastboot
5. Flash GSI: `fastboot flash system <extracted-gsi-image>`
6. Reboot and enjoy
*. (just in case it does not boot, reboot to recovery -> enter fastboot and flash vbmeta: `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`)
This vbmeta-image should work (see post #6): https://forum.xda-developers.com/attachments/vbmeta_disabled-img.5325563/

Unbrick your Realme C12

What is a brick?​If there is no usual way to recover your mobile, then it is called brick in my opinion. That means if you can't able to go to recovery and fastboot mode or the device is just blank with no sign of life.
When brick happens?​It will happen because of locking bootloader with custom images or just because of Mediatek/Realme strange behaviour.
What we have to do if brick happens?​Simply we have to flash stock firmware with Smart Phone Flash Tool(aka SPFlash Tool). With only SPFlash Tool we can't do anything, since we don't have permission for it. But with the advent of MTK-bypass, we can have full control over our device. If we don't have this MTK-bypass, then we have search for costly alternative's.
You can't flash only if your eMMC is damaged, which is the worst case because oppo phones are prone to eMMC failure.
Click to expand...
Click to collapse
Where to get firmware to flash?​Download decrypted .ofp firmware from https://drive.google.com/file/d/1SOmRxix9_UtjOLLanXPYxf4YK1NrA_RW/view
Thanks to @bx2_nero for it.
What is the procedure for using MTK-bypass and SPFlashTool?​MTK-bypass is a Python script and it needs different USB ways for working. So with these two in place, we can get our work done.
Linux Users​For Linux we have to use FireISO or patched kernels for working of MTK-bypass.
Use the Linux guide by @bx2_nero at https://forum.xda-developers.com/t/...our-realme-6-6i-india-6s-linux-method.4251077
Windows Users​For Windows we have to use libusb32 filter for MTK-bypass working.
Use the guide by @daeSundae at https://forum.xda-developers.com/t/...india-6s-using-spflash-tool-for-free.4222027/
MTK-bypass Official instructions​See Github ReadMe at https://github.com/MTK-bypass/bypass_utility and XDA support thread at https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377/
Credits​xyzz / xyz`: GitHub | XDA
chaosmaster / k4y0z: GitHub | XDA
Dinolek: GitHub | XDA
References​- https://forum.hovatek.com/thread-37957.html
- https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/
- https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
- https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
- https://forum.xda-developers.com/t/...ash-tool-authentication.4236881/post-84627359

MTKClient
After MTK-bypass got success, @viperbjk who is a reverse engineer came up with a FOSS replacement of SP Flash Tool.
MTKClient combines MTK-bypass and SP Flash Tool together and with many improvements and new features.
Ability to flash partitions without Scatter file
Ability to Readback partitions without specifying address and length
Ability to Format partitions without specifying address and length
Run multiple commands without reconnecting the device
Flash protected partitions(opporeserve2, special_preload, my_custom and cdt_engineering) with locked bootloader
Unlock bootloader without need of in-depth test/Deep testing app from Realme
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
www.github.com

Reserved

I need help, my C12 is stuck on fastboot mode. This happened after flashing a GSI using TWRP and flashing the image in the Super (System and Vendor) partition.
I tried rebooting to recovery mode by executing fastboot reboot recovery but it says that bootloader is not known.
I also tried to flash a GSI (taught it might fix the problem) using fastboot flash system system.img but it says that no partition named system exists.
Please suggest what I should do.

Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip

DFM23 said:
Bro, can you make a video about this? my realme c12 got hardbricked after I flashed ozip file from stock recovery while bootloader is unlocked. it got hardbricked when I reboot it after flashing ozip
Click to expand...
Click to collapse
What is the present state of the device? Can you able to boot to fastboot mode?

HemanthJabalpuri said:
What is the present state of the device? Can you able to boot to fastboot mode?
Click to expand...
Click to collapse
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.

How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.

youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
Use latest platform tools

youcancallmekhen said:
How can I reboot to recovery mode when in fastboot mode? The command fastboot reboot recovery is not working for me.
Click to expand...
Click to collapse
HemanthJabalpuri said:
Use latest platform tools
Click to expand...
Click to collapse
Sir I've finally able to reboot to recovery. I've tried flashing the OZIP file for my model but after some time it says Installation failed. When I was still using custom recovery, I wasn't able to mount System and Vendor. My bootloader is also unlocked sir.
Should I lock my bootloader sir?

youcancallmekhen said:
Should I lock my bootloader sir?
Click to expand...
Click to collapse
Don't lock bootloader.
Download this https://drive.google.com/file/d/1jLdDz7M0G_KPDn4jXjTeuFnO1C-MFaBs/view (It is from A.87 UI 1.0 Stock ROM)
Extract above 7z file and flash ONLY super partition from it and TWRP from https://androidfilehost.com/?fid=7161016148664807816 with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery TWRP.img
fastboot reboot recovery
Now enable 'Skip Treble Compatibility error' in TWRP settings and flash stock ROM .ozip in TWRP.
Thanks

HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
Oh my, thank you so much sir. You have no idea how much you are helping me sir! My parents will be so happy, and we won't waste money… Thank you so much sir…
I'll update you sir after doing these, thank you sir! ♥

HemanthJabalpuri said:
Don't lock bootloader.
Download this https://sourceforge.net/projects/realmec11/files/Fastboot-ROM/[email protected]/download
Extract above 7z file and flash ONLY super partition from it with below commands
Code:
fastboot -w
fastboot flash super super.img
fastboot flash recovery stock-recovery.img
fastboot reboot recovery
Now flash stock ROM .ozip in stock recovery.
Thanks
Click to expand...
Click to collapse
I don't have much data left today sir, so I will download this later. Thank you very much again sir, you're my hero!

DFM23 said:
it has no sign of life, cant go to recovery or fastboot. when I connect it to pc it goes connect and disconnected.
Click to expand...
Click to collapse
Follow the guide and you can get your mobile back to life.
Thanks

HemanthJabalpuri said:
Follow the guide and you can get your mobile back to life.
Thanks
Click to expand...
Click to collapse
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11

DFM23 said:
thank you bro, Ill follow your guide then. btw does the RMX2185 firmware you provided works with realme c12? I look it up and saw that it was for realme c11
Click to expand...
Click to collapse
Yes, both use same firmware.

I tried the guide but when I click download on sp flash tool it would stay in red bar for 1 min or more then message will appear saying STATUS_EXT_RAM_EXCEPTION. I have read a same comment here in xda about realme c12 I dont know if its only on realme c12.

Thanks for your works sir, you are super awesome!

I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?

Bhuprab said:
I rooted My Device (Realme X2 Pro) by Magisk. And Since My Device Bootloader was unlocked I Unrooted/Uninstalled MAgisk.
While Locking Bootloader My Device is Stuck where It displays { The Current Image (boot/recovery) have been destroyed dand cannot boot. Please flash the correct Image or Contact Customer Service to fix it }
While Trying to ENter the Fast Boot Mode {By pressing Volume + - and Power Button} Its Unresponsive
It shows Realme Logo And chrging Display for a Instant
Do you Know any way around to fix my Problem?
Click to expand...
Click to collapse
Since your device is Qualcomm, I don't know. In any device, we have to flash stock rom (or atleast the partitions that are modified) to get device in working state.
You may get better help at https://forum.xda-developers.com/f/realme-x2-pro-questions-answers.9439/
Thanks

how to reinstall Oxygen OS

HI Everybody,
I have a Oneplus 8T, European, I installed lineage recovery and Lineage OS 18.1, rooted, but now I would like to reinstall Oxygen 11. Please, can you tell me how to do or where to find the answer?
Please, don't tell me to use TWRP because at moment it's not available for this smartphone.
Thank you All in advance!

You'll need to download the msm recovery tool for your device. Will take it back to new

11mackey11 said:
You'll need to download the msm recovery tool for your device. Will take it back to new
Click to expand...
Click to collapse
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?

matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I guess you could try to fastboot flash a full rom zip I think that should work. If not you can just use the MSM tool to restore.
The steps to fastboot flash a full OOS rom zip should be the same as listed in this conversion thread https://forum.xda-developers.com/t/guide-convert-tmo-to-global-eu-or-other-variant.4188491/

matpack said:
even if it is not bricked? ideed my phone works perfectly. Is there any soft way for flashing the Oxygen rom?
Click to expand...
Click to collapse
I believe it can fastboot flashed. I just haven't tried it yet. I did see another post where the steps were laid out but remember where I saw it

I am also very interested in the answer to this question. And I think I know why the answer is "use the MSM tool".
Here's how I arrived at that:
If you use payload_dumper to have a look at what gets flashed when installing a rom, there's a number of image files that aren't listed in /dev/block/by-name such as odm, product, vendor and even system(!). This means that you cannot flash them using fastboot and the only way to flash them is via fastbootd (which is in recovery.img).
So the theoretical process is:
- boot into fastboot
- flash boot, recovery, and the other "normal" partitions
- start fastbootd using "fastboot reboot fastboot"
- flash the remaining partitions
- reboot
The problem with OOS is that fastbootd looks very much like recovery: it has no ADB/fastboot connectivity. So you cannot flash the remaining partitions.
Conclusion: the MSM Tool is the only way to return.
Acknowledgment: thanks to @chandu dyavanapelli for the Evolution-X rom installer script which helped me understand what's going on. See https://forum.xda-developers.com/t/...0_r34-evolution-x-passion-22-04-2021.4266067/

How To Guide Unlock the bootloader and install GSI ROM

So if anyone is interested in booting a GSI Image Here is the guide: also thanks to @Dollscythe I just updated it as he forget to write me a step for flashing the vbmeta.img..
1. you need to download the firmware file for your model
2. you need to open it with your zipping software of choice (i use 7zip) And after it unzips you need to unzip AP file to get to the recovery.img.lz4
3. you extract the recovery.img and you patch it to enable fastbootd https://github.com/Johx22/Patch-Recovery you will also find the info how to patch it on the link, it is easy if you know how to follow it) - Currently is NOT working, the dev said to me that he will fix this once his exams are over. (If you know how to Decompress the Iz4.img to get just the .img it will probably work - didn't try tho.
4. this step will wipe your device so make sure to back up (unlocking the bootloader) And it will also trigger your Knox!
To unlock the bootloader you need to go to settings, about phone - software info and press on the build number like 7times to enable developer options. After that go to developer options and enable OEM unlock.
Turn off the phone, put the USB C cable into the phone (but not into the computer yet!) Then hold the volume + and volume - button at the same time and put the cable into the phone.
When you are in the download mod you will see the instructions on how to unlock the bootloader.
5. Boot into the system and do the first time setup (make sure to connect to wifi, but skip any prompts to register or login to accounts)
6. double check if the oem unlock toggle is still on, then reboot to download mode
7. you need to flash the patched bootloader using odin - you flash your patched recovery in AP window in Odin. Then you immediately boot into the recovery (you gotta boot to your new recovery immediately after the flash is complete, make sure to hold the key combination for recovery immediately after pressing start in odin to get it right. otherwise, the system will wipe your newly flashed recovery and you'll have to do step 7 again)
8. You will now notice that your recovery has a new option: fastbootd mode (yes there's a d in there, it's not a typo, it stands for fastbootdynamic mode) 9. once you're in, your device now officially supports fastboot. you just do "fastboot flash system *the_name_of_the_system_image_you_downloaded.img", RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group) and once that is done flashing just exit fastbootd mode back to the recovery, then format data and then then reboot for system images, i recommend pixel experience https://github.com/ponces/treble_bu...4-ab-vndklite-12.1-20220518-UNOFFICIAL.img.xz 10. you'll be greeted by a google bootlogo and thats a success.
Good luck!

Bucika said:
RIGHT AWAY AFTER THAT flash vbmeta.img (it can be found in the telegram group)
Click to expand...
Click to collapse
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.

One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website

jdg007 said:
One thing I wish people on here would give more instructions than they do it's not easy on button the recovery image I don't know why you say it's easy cause it's not that makes no sense you don't put no links into the description of where to ago why don't somebody do like they used to do and actually give a s*** about what they put on this website
Click to expand...
Click to collapse
The purpose of XDA "Developers" was actually to share knowledge between developers, you know, people who actually know how the most basic stuff works. It's open up for the public, sure, but most of the stuff you can find here are not meant for the average noob that doesn't know how to unlock a bootloader.
The instructions are pretty clear for people who can use a google search. Don't expect everything to be spoon fed, put in a little effort.
There's a difference between saying "OMG this is too complicated why don't you explain it with a video or why don't you tell me step by step on how to flash custom firmware on my phone" and saying "Hey I'm stuck in step 3, I don't understand the part here. This is what I've tried so far..."
I bet for the most part, the first person would be ignored while the second person would more likely get a response.

That means to offend you in any way or whatever I just wished people would give more explanations on what they post because you know I don't make no sense on how you patch the recovery I'm new at this it's my it's my fault I do know how to unlock bootloaders not bootleggers and I do know how to install TWRP and Flash zip balls but as when it comes to patching something the only thing I know how to pack is using magisk That's the boot image I'm sorry hope Hope you can help me out

If you don't mind email me a copy of that recovery image that you got Text I sure would appreciate it Just looking forward For your reply

Thanks @Bucika, here's a guide that might be a bit more noob friendly. Also a big thanks to @Dollscythe for their help.
Files can be found here.
These are the latest GSIs.
1. Unlock bootloader by opening developer options and flipping the "unlock bootloader" switch.
2. Boot into download mode (press and hold vol + and - while plugging into computer).
Press and hold vol + to enter unlock mode. Accept and click enter. Your phone will reset.
3. Using Odin, flash fastbootd through AP. (recovery.img).
4. Press and hold volume + key as the phone reboots, as when you restart again it will reverse this step. You should be in recovery now.
Click on fastboot.
5. Get fastboot working on your computer. Test connection by using the command "fastboot devices" to see if your device is there.
6. Run the command fastboot flash system [name of gsi file]. (without square brackets)
7. When you're done, run ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
8. Go back to recovery and wipe your phone.
9. Go back into fastboot, flash magisk file if you would like root: fastboot flash boot magisk
10. Wipe again, reboot.
11. Once you are fully booted in, open settings > phh settings (first entry) > misc settings > then scroll down until you find "force fps"
Change that to the @120fps option.
Hope this helps! Note that this is unofficial and WiFi hotspot doesn't work, Samsung Health has issues too. I couldn't get my watch 4 working with GSI.
This will blow your Knox bit fuse!

Ivan Fuentes Hagar said:
I'd just add that the proper command to flash vbmeta.img is ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (I don't use "./" though, as I've included platform-tools in my path env variable).
Not disabling verity/verification sent me to a bootloop from hell after rebooting... I began reading more carefully the Telegram chat, found the proper command and I'm now setting my PixExp as I write.
Click to expand...
Click to collapse
I find myself in a bootloop too after this step, how did you get out of the bootloop?
edit, answer to my own question in case it helps someone in the future: plug phone into a pc and then hold `volume up + volume down` buttons to enter download mode.
edit 2 if after flashing a GSI rom your device wont boot, plug it into power and wait a few minutes.

I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?

ActuallyJammy said:
I know I am kind of late but after flashing the pixel experience GSI, it is stuck in the google logo. What do I do?
Click to expand...
Click to collapse
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12

TringQuack said:
flash another gsi this gsi doesn't work on a53 unless you use pixel experience 12
Click to expand...
Click to collapse
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.

ActuallyJammy said:
Alright, so I got an old build of PE 13 to work, but somewhy the newer security patches don't work. Is there any reason, or is it just not compatible at all? Also, there's a problem with the fingerprint; it detects it as if the fingerprint scanner is in the back when it is on the screen. Is there any fix? Mainly because it's my primary phone.
Click to expand...
Click to collapse
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13

TringQuack said:
new patch was introduced in trebledroid that fixes this fingerprint issue, you can either use another gsi built on trebledroid on the date of jan 31 or later, or wait for Ponces to make a new PE build for A13
Click to expand...
Click to collapse
Could you give me a GSI rom with a patch and similar to PE?

@TringQuack What's your current state with A53?
Running GSI? Stock?

ThugMaster said:
@TringQuack What's your current state with A53?
Running GSI? Stock?
Click to expand...
Click to collapse
Stock

@TringQuack How do I know if the build is compatible with A13?

[GUIDE] Gigaset GS5 (rephone) root with Magisk + unlock bootloader

hello I'm not sure if this is the right place to post this in but I'll be putting together a small guide on how to root the Gigaset GS5​the phone I own is called "rephone" it's apparently a sustainable version of the Gigaset GS5 with a removable battery recycled plastic etc etc. But specs wise it is the same as the Gigaset GS5
anyways I did this yesterday so it's possible that I forgot some steps, if you encounter issues feel free to leave a comment and I'll try to assist you
prerequisites:​- make sure you actually have this device
- make sure you are on Android 12 (ota update)
- make sure you back up your data
- make sure you read this guide carefully
UNLOCKING BOOTLOADER WILL WIPE ALL YOUR DATA!!! MAKE SURE TO BACK EVERYTHING UP​Proceed with caution, I am not responsible for anything that may happen to your phone, you are doing it at your own risk
Easy method (flashing pre-made boot.img) :​I would not recommend this method because I extracted the kernel from my rephone and I don't know if the firmware/kernel for that is 1:1 with the GS5, ideally you want to extract the boot.img of your own device but that takes way more time so only proceed with this if you're at a pinch or are too lazy to extract your own boot.img
Also please download CPU-Z on your device and check your Build ID under the System tab, if it matches with mine then feel to proceed with this method, if not then do not proceed and instead extract your own boot.img and patch that
Build ID for my rephone is: 2000_000170_00_12.0_V06_20221025
Set up adb&fastboot on your computer (google 15 second adb installer)
Grab the patched boot.img from my GitHub and copy it to C:/adb or wherever you installed adb&fastboot: https://github.com/astolfoaddict/GigasetGS5-Magisk
Unlock developer options in your phone and enable OEM Unlocking
Power off your device and hold volume up+power until you boot into bootloader
Select and boot into Fastboot Mode, connect device to your computer
At this point you're in fastboot, open CMD in C:/adb
Your bootloader is probably locked, to check run this command: fastboot getvar unlocked if the result is no, your bootloader is locked
To unlock your bootloader run this command and follow the instructions on your device: fastboot flashing unlock (THIS WILL WIPE YOUR DATA)
Once you unlock your bootloader, wipe your vbmeta partition. Follow Method 3 in this guide: https://www.hovatek.com/forum/thread-32719.html
Now flash the boot.img: fastboot flash boot boot.img
Reboot, set up the device, install Magisk Manager and enjoy!
Advanced method (extracting and patching your own boot.img) :​In this method we'll be extracting the boot partition from your device so you can patch it with Magisk and flash
Proceed with caution!
Install Mediatek VCOM drivers, follow this guide: https://www.hovatek.com/forum/thread-440.html
Dump your boot_a partition with MTK Client by running python mtk r boot_a boot.img follow this guide: https://www.hovatek.com/forum/thread-40865.html
Install Magisk Manager and patch your boot.img
Unlock bootloader, flash empty vbmeta and boot by following the method above
Important:
- Make sure you run python mtk r boot_a boot.img in MTK Client
- If you don't see Mediatek VCOM drivers in Device Manager after using the auto installer, try installing the drivers manually (check guide)
- Also booting into BROM mode is tricky, what usually works for me is:
Power off device and connect to PC
As it starts up and shows you the battery charge, wait until the screen goes out
At this point you should run the python command in MTK Client
Hold volume down+power and check the terminal
If you want to extract the entire firmware follow this guide: https://www.hovatek.com/forum/thread-21970.html
Be aware that your chipset will not be listed in WwR MTK so what you do is open Template.ini with Notepad++ and add MT6768 under the CPU section, don't worry about the chipset not matching what this phone has (MT6769), adding MT6769 to CPU and exporting scatter file will not let you import it in SP flash tool
Special thanks to axonasif and supremegamers for the guide I pulled most of the stuff out of: https://github.com/supremegamers/mt6769​Also thanks to hovatek for their helpful resources regarding MTK flashing/drivers/etc. <3​

Hy
Ubuntu Touch with Waydroid works fine with Gigaset GS5......only Unlock Bootloader and flash with UB Port Installer..........
and you can flash Sailfish Port per Fastboot .............

yeah you can install GSIs too like lineage os and other stuff

astolfoaddict said:
yeah you can install GSIs too like lineage os and other stuff
Click to expand...
Click to collapse
Hy
have you some flashable files from lineage os...........??????? im searching found nothing............would be great
Thanks

astolfoaddict said:
yeah you can install GSIs too like lineage os and other stuff
Click to expand...
Click to collapse
its only a fake to install GSI image!!!!!! Dont work!!!!!!

hugolight said:
its only a fake to install GSI image!!!!!! Dont work!!!!!!
Click to expand...
Click to collapse
what do you mean?

astolfoaddict said:
what do you mean?
Click to expand...
Click to collapse
i have found no one GSI img file to flash my gigaset gs5!!!!!!

hugolight said:
i have found no one GSI img file to flash my gigaset gs5!!!!!!
Click to expand...
Click to collapse
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
Hello dont work
fastboot flash system lineage.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/16 (131060 KB) OKAY [ 4.278s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
hy can you post the direct link for correct image (gigaset gs5)........thanks

astolfoaddict said:
hello I'm not sure if this is the right place to post this in but I'll be putting together a small guide on how to root the Gigaset GS5​the phone I own is called "rephone" it's apparently a sustainable version of the Gigaset GS5 with a removable battery recycled plastic etc etc. But specs wise it is the same as the Gigaset GS5
anyways I did this yesterday so it's possible that I forgot some steps, if you encounter issues feel free to leave a comment and I'll try to assist you
prerequisites:​- make sure you actually have this device
- make sure you are on Android 12 (ota update)
- make sure you back up your data
- make sure you read this guide carefully
UNLOCKING BOOTLOADER WILL WIPE ALL YOUR DATA!!! MAKE SURE TO BACK EVERYTHING UP​Proceed with caution, I am not responsible for anything that may happen to your phone, you are doing it at your own risk
Easy method (flashing pre-made boot.img) :​I would not recommend this method because I extracted the kernel from my rephone and I don't know if the firmware/kernel for that is 1:1 with the GS5, ideally you want to extract the boot.img of your own device but that takes way more time so only proceed with this if you're at a pinch or are too lazy to extract your own boot.img
Also please download CPU-Z on your device and check your Build ID under the System tab, if it matches with mine then feel to proceed with this method, if not then do not proceed and instead extract your own boot.img and patch that
Build ID for my rephone is: 2000_000170_00_12.0_V06_20221025
Set up adb&fastboot on your computer (google 15 second adb installer)
Grab the patched boot.img from my GitHub and copy it to C:/adb or wherever you installed adb&fastboot: https://github.com/astolfoaddict/GigasetGS5-Magisk
Unlock developer options in your phone and enable OEM Unlocking
Power off your device and hold volume up+power until you boot into bootloader
Select and boot into Fastboot Mode, connect device to your computer
At this point you're in fastboot, open CMD in C:/adb
Your bootloader is probably locked, to check run this command: fastboot getvar unlocked if the result is no, your bootloader is locked
To unlock your bootloader run this command and follow the instructions on your device: fastboot flashing unlock (THIS WILL WIPE YOUR DATA)
Once you unlock your bootloader, wipe your vbmeta partition. Follow Method 3 in this guide: https://www.hovatek.com/forum/thread-32719.html
Now flash the boot.img: fastboot flash boot boot.img
Reboot, set up the device, install Magisk Manager and enjoy!
Advanced method (extracting and patching your own boot.img) :​In this method we'll be extracting the boot partition from your device so you can patch it with Magisk and flash
Proceed with caution!
Install Mediatek VCOM drivers, follow this guide: https://www.hovatek.com/forum/thread-440.html
Dump your boot_a partition with MTK Client by running python mtk r boot_a boot.img follow this guide: https://www.hovatek.com/forum/thread-40865.html
Install Magisk Manager and patch your boot.img
Unlock bootloader, flash empty vbmeta and boot by following the method above
Important:
- Make sure you run python mtk r boot_a boot.img in MTK Client
- If you don't see Mediatek VCOM drivers in Device Manager after using the auto installer, try installing the drivers manually (check guide)
- Also booting into BROM mode is tricky, what usually works for me is:
Power off device and connect to PC
As it starts up and shows you the battery charge, wait until the screen goes out
At this point you should run the python command in MTK Client
Hold volume down+power and check the terminal
If you want to extract the entire firmware follow this guide: https://www.hovatek.com/forum/thread-21970.html
Be aware that your chipset will not be listed in WwR MTK so what you do is open Template.ini with Notepad++ and add MT6768 under the CPU section, don't worry about the chipset not matching what this phone has (MT6769), adding MT6769 to CPU and exporting scatter file will not let you import it in SP flash tool
Special thanks to axonasif and supremegamers for the guide I pulled most of the stuff out of: https://github.com/supremegamers/mt6769​Also thanks to hovatek for their helpful resources regarding MTK flashing/drivers/etc. <3​
Click to expand...
Click to collapse
I’d put the devicees in fastboot mode and run:
fastboot getvar product
Gigaset k69v1_64
Rephone k69v1_64_k419
GS5 and Rephone not the same!!!!!!

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
Hy
Mobile Data work with this image?

Hy,
my bootloader is unloock.......cant flash any image......
FAILED (remote: 'Not enough space to resize partition')
what can i do????

Hi
i have the same rephone with Build like yours astolfoaddict : 2000_000170_00_12.0_V06_20221025
and did the easy UNLOCKING method.
then i flashed "fastboot flash system lineage-19.1-20230418-UNOFFICIAL-a64_bvS.img"
an now my phone hangs in a bootloop.
did i missed something like the recovery.img cause i dont have that or what i have done wrong ?

Hi everybody,
is this a working method for installing lineage 19 on a rephone? w2273 and hugolight do you had success?
In other words, should i try or not ;-)
thanks.....