[ROOT] [TWRP] Gigaset ME/ME Pro

[Plemyash]

Hello! Does anyone have football edition firmware?

 

[Rukh32]

What to do with gpl source file

Latest video: https://youtu.be/o6cpMa2Fo_c
Since 01.16 update Gigaset Me and Me pro use same ROM. So read carefully and take responsibility what you are doing on you device.
Gigaset Pure is not supported here.


GPL Source codes:
Me/MePro/ platform tools full : http://www.gigaset.com/de_de/cms/lp/open-source.html
Me/MePro platform tools uploaded in 1 file (gdrive): https://drive.google.com/uc?id=0B_81lkQEKce4bFlaRXk3dFFwQzA&export=download
Me/MePro kernel source (my repo on github): https://github.com/Eddie07/GIgaset_Me_MePro_3.10._kernel


Terms of Usage:
1. Everything posted on this post should be reposted with links to original post.
2. I'm not responsible for any damage to your phone.
3. If you are aware of bricking device by this or you don't understand some of processes described below - close this thread and leave it alone.
4. If you agree with p.1,2,3 go on to Step2.

GIGASET secret codes:

*#*#4636#*#* - phone info
*#*#2580#*#* -engineer mode (wif, bt tests, usb ports, adb root (pass:gigaset001), ota settings.
*#*#708#*#* - float system info (cpu speeds, m|b temp), shake test.
*#*#801#*#* - wifi test.
*#*#802#*#* - bt test.
*#*#803#*#* - bt test 2.
*#*#2588#*#* - factory hardware tests.
*#*#2581#*#* - Camera callibration??.

(Only ME/MEPRO)TWRP CUSTOM RECOVERY, UNBRICKING:


-FLASH CUSTOM RECOVERY ON ME/MEPRO HERE
-UNBRICK SOLUTION back to rom EU00_V1.1.20160616R ME/MEPRO (if you deleted system, recovery, boot) : BACKUPS--- UNBRICKING

(Only ME/MEPRO)CUSTOM ROMS:
LAST CM 12.1

(Only ME/MEPRO)PATCHES TO STOCK ROM TO BE INSTALLED VIA CUSTOM RECOVERY:

LAST MY "TUNED" TWRP BACKUP https://xdaforums.com/showpost.php?p=71180342&postcount=371
-PATCH#1 TWRP PATCH ME/MEPRO for CPU speeds uncap (1,9ghz), Thermal config fix, Fix of display size MePro HERE
-PATCH#2 Enable 4K video recording in stock camera app HERE
-PATCH#3 Enable Callrecording button in stock dialer app HERE
-PATCH#4 READ DESCRIPTION HERE
-PATCH#5 SystemUI patch HERE

ADB ROOT FOR STOCK ROM WITHOUT ROOT AND CUSTOM RECOVERY:
- Unlocking Me/Pro abd root via factory tool hidden in rom. (usage for Gigaset Me/Pro/Pure)

1) Type in dialer: *#*#2580#*#* to get in Engin. tool
2) Select "priviledge" tab.
3) Type "gigaset001" in pw field.
Get adb root
to check if is done enable USB debugging and try adb command from PC:
"abd shell" if command prompt ends with "#" then adb is rooted, if "$"-isn't!
4) Turn off adb root- type password again.

Dev I want to flash stock rom how do I do it without custom recovery I've downloaded gpl source file from link given above now I don't know what to do about .tar file

 

[Rukh32]

Dev I want to flash stock rom how do I do it without custom recovery I've downloaded gpl source file from link given above now I don't know what to do about .tar file

I'm nube I think I don't have unlocked bootloader, root, know nothing about recovery plz explain it in detail

 

[daffyjack]

someone knows how put fingerprint service on cm?

 

[dadyal]

i have issue with Gigaset Me it gets stuck on Logo screen every few weeks and i had to reset from Recovery to make it run again has anyone found any fix for this issue i am tired of losing data every few week ?

 

[lordmd]

Hi. I recently bought a Gigaset ME - cause it was cheap depite having not too bad hardware. (I guess it is because they aren't updating Android for it anymore.) Now I wanted to play around a bit. And maybe trying to compile Android since vendor source stuff is available for Gigaset. But I'm still a noob to this.

So checking if flashing stuff works would be the 1st step - so I could reflash the original stuff again if something goes bad. Thanks to heineken for uploading the stock images. I managed to flash the TWRP recovery - works fine. Also I once had to reflash the systembackup.img I downloaded from here. After flashing it I had a display bug with the battery. (Powered off and charging or in the recovery it shows the correct percentage in the booted system it shows a few thousand percent lol.) [Edit]Reflashing everything as recommended per Unbrick-Post - this only worked in Windows for me the linux version of the tool bugged - fixed the error. Maybe fastboot created some errors or I needed the other files as well cause I tried only system with fastboot which got me that battery stats/percentage display error.[/Edit]

I flashed with fastboot - cause I'm used to it from another device. From checking/searching the Gigaset source stuff downloaded from their website ... it seems they block fastboot in normal fastboot/bootloader mode. From an adb shell in the system (or terminal in TWRP recovery) I could boot to the "real" fastboot mode.

Use: reboot oem-1a
(instead of reboot bootloader)

All the commands (flash and stuff like that) seem to work there. Unfortunately the "unlock oem" doesn't really seem to do anything. The fastboot you acces in a normal way (also some volume key + power key to boot directly from powered of device is possible) always still blocks all the commands. Necessary to boot into fastboot with "reboot oem-1a" every time.

 

[detsch75]

LineageOS for Gigaset ME pro

Hello everyone,

I'm trying to port LineageOS 15.1 to a Gigaset Me pro device. The device has a QCOM msm8994 soc. It is similar to Nexus6p or Oneplus2. I started with the original kernel, but it always ended in a boot loop and I couldn't figure out the reason why. So I took the Lineage repository for the kernel qcom_msm8994 and merged the Gigaset specific changes. Finally the device booted and TWRP and Lineage UI is working. I still have several issues to fix. One of them is an issue with the sound card. The sound card is not available as device because the tomtom_codec is not loaded. I know that the tomtom_codec is based on the WCD9330 chip and this is using the Slimbus. In the debug messages I can see that the function tomtom_codec_init is called. But what I don't see is a call to the method tomtom_probe. I have also checked the device tree and everything looks find. So my questions: Is the codec initialization somehow related to the start of a service? Should it be automatically detected by the kernel? How is the initialization process of codecs?

Many thanks in advance.

Best regards

Det

 

[nikosddesign]

many test days with other rom with many rom and many versions of 6-7-7.1.1-7.1.2-8 - 9 without results. I do not know what else to try. all launches with bootlop...................sickkkkk

 

[ColdIllyrian]

many test days with other rom with many rom and many versions of 6-7-7.1.1-7.1.2-8 - 9 without results. I do not know what else to try. all launches with bootlop...................sickkkkk

Oh well someone managed to boot Oreo ? so that's good, now lemme say something first and that is that this device was built with lollipop and now if devs for the Sony z5 can't even build Oreo with everything working and it's final update is 7.1.2 I would be amazed if you guys found a way to get it working with no bugs considering your jumping like 3 android versions straight away I would suggest contacting someone at gigaset maybe they can give you access to all files or something , good luck

 

[nikosddesign]

Oh well someone managed to boot Oreo so that's good, now lemme say something first and that is that this device was built with lollipop and now if devs for the Sony z5 can't even build Oreo with everything working and it's final update is 7.1.2 I would be amazed if you guys found a way to get it working with no bugs considering your jumping like 3 android versions straight away I would suggest contacting someone at gigaset maybe they can give you access to all files or something , good luck

thankfully we also have positive criticism from some .....:good::laugh:
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810-msm8994
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810-msm8994-v21
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810-msm8994-v2-1
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810-msm8994-v2-1-1-8
I do not care about kids doing xperia z5 and I do not care.
Trying to do it, which has always failed successively in all editions and in a series ...

 

[ColdIllyrian]

thankfully we also have positive criticism from some .....:good::laugh:
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810-msm8994
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810-msm8994-v21
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810-msm8994-v2-1
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810
https://www.kimovil.com/el/lista-kinhton-apo-epexergastes/qualcomm-snapdragon-810-msm8994-v2-1-1-8
I do not care about kids doing xperia z5 and I do not care.
Trying to do it, which has always failed successively in all editions and in a series ...

Ok then well let's hope your able to finally develop a fully working custom rom for this device xd

 

[nikosddesign]

Ok then well let's hope your able to finally develop a fully working custom rom for this device xd

port port port

 

[ColdIllyrian]

port port port

Oh your porting, that's bound to have problems you have one problem you fix it then you get another one

 

[heineken78]

you guys are funny and sounds like Indians
device needs updated tz (trustzone) even to use it with A6.
other side it doesn't require signature (is not secureboot from factory).. guess what, Lineage 16 is even possible..

 

[ColdIllyrian]

you guys are funny and sounds like Indians
device needs updated tz (trustzone) even to use it with A6.
other side it doesn't require signature (is not secureboot from factory).. guess what, Lineage 16 is even possible..

Oh wow so is there a chance it will be developed it would be nice to have a good rom on my spare phone ? I am from London btw xd

 

[DeepakSonix3]

you guys are funny and sounds like Indians
device needs updated tz (trustzone) even to use it with A6.
other side it doesn't require signature (is not secureboot from factory).. guess what, Lineage 16 is even possible..

I might help with the build from scratch . I have resources for it but need a guide .
Can't find a reliable guide on net for an unsupported device.
Just a Good Working GUIDELINE.:fingers-crossed:

 

[monikalabuda]

Ok. I have problem. Last time I used it: xdaforums.com/showpost.php?p=71180342&postcount=371
Now I want to know if is new version to update my phone where new problems are fixed. If yes, where can I find it? Or how can I handle it from beginning?

 

[PixelLucas_3408]

google service again

Hi, I get my Me pro in china, but I don't know any about flashing or custom ROM. Is there any easy way to get google service in this phone without root?

 

[frygy27]

hello

Hello. I have a Gigaset Me Pro GS57-6 phone. I need firmware and I can't download it from anywhere. I can't find it anywhere on the forum. The problem with the phone is that it remains locked in the Gigaset Logo. I can't even enter TWRP. If you can help me with firmware (ROM) for GS57-6.Thanks for having a nice day.

 

[frygy27]

Hello. I have a Gigaset Me Pro GS57-6 phone. I need firmware and I can't download it from anywhere. I can't find it anywhere on the forum. The problem with the phone is that it remains locked in the Gigaset Logo. I can't even enter TWRP. If you can help me with firmware (ROM) for GS57-6.Thanks for having a nice day.