yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] baymon:
as mentioned before, another thing that you should've tried is to call the helpline and see if there's an outage in your area. I've been experiencing the same problem in a very particular area (3G hand-off to EDGE problem only happens on campus). Tried different radios and problem still exist, so I gave them a call today and turned out that there is an outage here.
[Tilt, TyTN II, MDA Vario III General] stooby:
In my case, it's not caused by a network outage - 3G works fine on my Hermes in the same locations.

Good thought though.
[Tilt, TyTN II, MDA Vario III General] Zaf:
Relax boys...I have'd the same problem... The only solution is to go with your phone for warranty return. There they will change your TyTN II mother board and all will be ok. IT IS THE ONLY WAY.

PS do the same thing I did http://xdaforums.com/showthread.php?t=418375
[Tilt, TyTN II, MDA Vario III General] drevogel:
i post this thead and the solution

i post this tread an the solution came on tha answer of various of you great ideas i get the solution changing the rom and the wm to 6.1 and the rom is the dutty's it has worked almost perfectly in any wy itested only some install on the gps progrms but no mayor problem tks all you friens for a great support
[Tilt, TyTN II, MDA Vario III General] alt236:
The same thing has happened to me as well (Orange UK).

Initially I thought that it was an outage in my area as my friends had problems connecting to 3G as well, but their problem has been fixed but I still cannot.

I'll be contacting their tech support dept. later today and I'll post back.
[Tilt, TyTN II, MDA Vario III General] microsys:
I live in Buffalo, NY and have had NO problems with making phone calls via 3G or E. BUT, when I recently traveled to Atlanta and New York City - I was unable to make or receive calls. I had 5 bars and other AT & T customers were making calls perfectly fine.

Spoke with AT & T customer service and escalated issue to top level support - they were stumped. THey cold see I was pulling signal from the tower but could not explain why I was unable to make/receive calls. I spent HOURS with them debugging this very frustrating problem. The signal would bounce from H to 3G (unable to make/receive calls in these modes, although in Buffalo - 3G worked fine!), but if I made a call when it cycled to E or G service, all was well. No option is settings on phone to "force" only one specific service.

When I return back to Buffalo, all is perfect again - using 3G service!

Summary - AT & T will be replacing my phone(less than one year old) and "hopefully" this will reolve this issue. Will keep you updated as things progress.
[Tilt, TyTN II, MDA Vario III General] alt236:
Just to avoid double posting, any updates will be in this thread:

http://xdaforums.com/showthread.php?t=423134

Just an interesting note though, according to an Orange UK staff member, it might be better to call 156 for 3G/PDA problems in the UK.
[Tilt, TyTN II, MDA Vario III General] hetspookje:
No provider service on Kaiser

After upgrading to the original HTC WM6.1 ROM the Kaiser can't connect to the network anymore. Tried many things from HardSPL3.28 and many ROM's and radios. :mad:

On manual it sees the network Vodafone NL, but fail to connect. The SIM is ok because I tested it on a different phone and also tried different SIM's and changed the band setting etc. Notthing works so I think the HTC TyTn II need to be serviced.

The GPS and WiFi works fine.

If someone has an other suggestion, then this will be welcome. :confused:
[Tilt, TyTN II, MDA Vario III General] samvds:
I do have to same problem as described above...

Anyone has a soution for this??

Sam
[Tilt, TyTN II, MDA Vario III General] Yuanlong:
I'm currenlty in Australia using Optus. I can get on to Optus 3G or HSDPA network but only for 1-2 sec before it drop off totally. However when I switch over to telstra sim card, I can use 3G or HSDPA without a problem.

The problem shouldn't be with the sim card or setting as I've check the setting with optus and check the sim card using a mobile modem. Anyone had similary problem with a solution?
[Tilt, TyTN II, MDA Vario III General] Offar:
I used to have the same problem. I sent back to HTC service centre and the change for the the transmitter (not sure if its a right term). After that i have no issue of that!

By the way... I'm in Malaysia. I believe its one of the classic problem with Tytn II or Kaiser or whatever u call this phone.
[Samsung Galaxy Nexus] nikkky:
Hello, can you please give me one kernel that support color changing (I think this is called KCAL support). I want it for Unlegacy Android 6 but if you have for other Android versions including Android 4.4.4 or Android 7.1.2 or even <Android 4.4.4 I will try with Android 4 or Android 7. I found some kernels with rgb color changing but links are very old and not alive.
[Samsung Galaxy Nexus] woodman:
Thread closed at OP request.

woodman

Senior Moderator
[T-Mobile Samsung Galaxy S8 Questions & Answers] D200P13:
Can someone link me the newest way to root it please.
[T-Mobile Samsung Galaxy S8 Questions & Answers] jdmark:
You can't. This phone is a piece of ****.
[OnePlus 7 Pro Questions & Answers] sudhiryadav:
After updating latest version no battery is fine
[SuperR Kitchen] SuperR.:
Welcome to SuperR's Kitchen Donate version!

This thread is intended to organize release posts. All discussion regarding this kitchen can be found in the thread linked below.

https://xdaforums.com/t/windows-linux-mac-donate-superrs-kitchen-v3-2-1-0-12-6-2020.3601702/
[SuperR Kitchen] SuperR.:
v3.0.0.1

Changes:

Download and extract Android Image Kitchen (Linux) directly from the XDA thread.

Fixed extracting tar.gz files.

Fixed crash if the main tools download/extract fails.

Fixed crash in Linux when updating the kitchen launcher.

Fixed crash when running the updater if there is no update available.

Added logging to img extract operations.

Fixed crash if Java 8 is not installed on Linux.

Added check for proper java installation on Windows.

Fixed language files other than English.
[SuperR Kitchen] SuperR.:
v3.0.0.2

Changes:

Fixed extracting Pixel firmware.
[SuperR Kitchen] SuperR.:
v3.0.0.3 (Donate version)

Changes:

Fixed custom zips on Pixel devices.

Removed attempts to pip install packages from within the kitchen.

Added logging to adb operations.
[SuperR Kitchen] SuperR.:
v3.0.0.4

Changes:

Require kitchen restart after updating.

Fixed duplicate unmount commands in updater-script when extracting extra img files.

Fixed some language file checks from crashing.

Added official Windows launcher (superr.exe).

The kitchen should install psutil (win/linux) and colorama (win) packages now if they are not already installed.

Thanks to [MENTION=7874870]Xennet[/MENTION] for the launcher idea. It makes running the kitchen in Windows a lot easier :)

NOTE: You should restart the kitchen manually after the update. This will be the last time you will have to remember on your own :)
[SuperR Kitchen] SuperR.:
v3.0.0.5

Changes:

Fixed Windows kitchen trying to update the Linux launcher.

Fixed cyfile errors.

Fixed system.img.ext4 not being renamed automatically if not in an archive.

Added dialog informing we are getting the plugin list when installing a plugin.

Check for and show error message when trying to run Bash plugins in Windows.

Remove all set_metadata lines with a context of "?".

Add all files in /system/bin to the updater-script.

edit: I forgot to reset the language file in this update, so if you update you will get an error when you try to install a plugin.

Easy fix after update (fresh installs do not need this):

Misc tools >> Reset language - After restart no more error :)
[SuperR Kitchen] SuperR.:
v3.0.0.6

Changes:

Hopefully fixed crash after signing zips when checking for update-binary script.

Updated Imgextract.exe to 1.3.7.
[SuperR Kitchen] SuperR.:
v3.0.0.7

Changes:

Ignore commented lines in build.prop.

Do not create set_metadata lines for files/directories that do not exist.

Do not use fstab with nodata in the name.

Removed duplicate /system/vendor/firmware set_metadata line.

Fixed tar creation for future use.
[SuperR Kitchen] SuperR.:
v3.0.0.8

Changes:

Minor improvement to set_metadata generation in Windows.

Fixed Android O rom not building due to lack of xbin.
[SuperR Kitchen] SuperR.:
v3.0.0.9

Changes:

zipalign - check to make sure files exist before renaming and record in main.log.

Fixed assert getting broken when building rom.

Fixed line endings in updater-script when running in Windows (thanks to [MENTION=2545403]chevycam94[/MENTION] for pointing it out).

NOTE: You may need to change perm types to something else and back to whatever you want to get the line endings sorted out. Fresh extract will all be good now :)

NOTE2: If you go to ROM Tools >> Asserts Menu >> Reset asserts to default you will get your assert back to normal if it was broken.
[SuperR Kitchen] SuperR.:
v3.0.1.0

Changes:

Fixed crash when choosing main menu from root zip options menu.

Fixed crash when getting by-name through adb.
[SuperR Kitchen] SuperR.:
v3.0.1.1

Changes:

Fixed crash in Windows when checking for app_chimera at the start of deodexing N and O.

Fixed crash when finishing deodex on M and L.

Fixed crash and show error message when entering the wrong syntax for custom asserts.

Fixed boot/AIK still being part of the repo and causing Windows tools install failure after resetting tools and boot extraction failure on Linux.

Fixed crash removing knox in Windows.

Fixed crash deleting plugins if example does not exist.

Heapsize errors now return you to heapsize options instead of Misc Tools.

Added confirmation when deleting projects.

Tried to fix META-INF1 remaining after builing rom.

Thanks to [MENTION=2545403]chevycam94[/MENTION] for testing like a mad man :)
[SuperR Kitchen] SuperR.:
v3.0.1.2

Changes:

Fixed logs crash when check for updates on start is enabled.
[SuperR Kitchen] SuperR.:
v3.0.1.3

Changes:

Change root status to rooted when adding Magisk using the plugin.
[SuperR Kitchen] SuperR.:
v3.0.1.4

Changes:

Display root type instead of Rooted.

Fix error during deodex cleanup on L and M.

Fix crash when removing knox.
[SuperR Kitchen] SuperR.:
v3.0.1.5

Changes:

Disable sepolicy-inject root method for Windows.

Fixed sepolicy-inject root method for Linux.

Fixed some debloat/knox checks.

Updated smali/baksmali to v2.2.1.
[SuperR Kitchen] SuperR.:
v3.0.1.6

Changes:

Fix crash when signing zips that use an update-binary script in Windows.

Log zip signing in sign.log.

Fixed update-binary conversion on roms that do not use by-name.

Make a copy of *_statfile.txt after extracting img files in Windows.

Add *_statfile.txt to support zip.

Add META-INF directory to support.zip.

Fixed Downloading/installing screen that disappeared.
[SuperR Kitchen] SuperR.:
v3.0.1.7

Changes:

Fixed manually signing zip when there are more than one to choose from.

Added ability to convert all flashable zips to update-binary script when building.

Added per-project option in Misc Tools for update-binary script - Always convert, Never convert, Ask every time.

Added check for delete_recursive when converting to update-binary script.

Fixed mount command not getting converted to update-binary script if rom does not use by-name.

NOTE: The default of the new update-binary conversion switch is "Ask every time". Remember, this is per project so you will need to change it for all projects if you want it changed globally.
[SuperR Kitchen] SuperR.:
v3.0.1.8

Changes:

Windows: Use 7-zip (included) to extract img files instead of Imgextractor.

Windows: Fixed missing symlinks in updater-script.

Windows: Fixed many file contexts not being set correctly.

Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.

Linux: Do not create metadata lines for symlinks.

I think this will fix most of the flashing problems. Let me know how it goes :)

WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.

IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
[SuperR Kitchen] SuperR.:
v3.0.1.9

Changes:

Windows: Fixed b key press not being recognized.

Added a Back option to the root method options.

Only allow key presses that correspond to menu options.

Fixed project name adding an extra superr_ when creating new project from the project selection menu.

Set permissions of configure.sh to 777 instead of /tmp to 755.
[SuperR Kitchen] SuperR.:
v3.1.8.1

Changes:

Fixed the possibility of a rare crash when starting the kitchen.

Fixed pulling img files from Samsung devices through adb (hopefully).

Fixed lag during extraction after entering your custom signature and after choosing the perm type.

NOTE:

All plugins must be updated to work in v3.1.8.1. Sorry about this. The easiest way is:

Plugin Manager > Check for plugin updates

A few plugins that were broken in Linux have been fixed as well.
[SuperR Kitchen] SuperR.:
v3.1.8.2

Changes:

Fixed ramdisk menu not showing status and not working.

Do not allow empty passwords.

NOTE: This update was primarily to fix the ramdisk regression from v3.1.8.0. Sorry about that.
[SuperR Kitchen] SuperR.:
v3.1.8.3

Changes:

Make the language dictionary available in plugins to allow translation.

Linux: Use the included Python for plugins that require root instead of your local Python install.

Hopefully fixed pulling img files through adb from Samsung (and possibly others) when booted to custom recovery.

NOTE:

Once again, all plugins must be updated to work with v3.1.8.3 and the kitchen must be updated to run the new plugins. The easiest way to do this is update the kitchen first, then check for updates in the plugin manager.

aroma_install plugin has been updated. I fixed what I think was broken, but I did not test on device so let me know how it goes.
[SuperR Kitchen] SuperR.:
v3.1.8.4

Changes:

Do not allow creating the same custom directory twice.

Added option to remove custom directories when trying to add the same directory again.

Store custom directories in srk.conf instead of its own file.

Fixed double forward slash in updater-script when adding custom directories.

Updated adb binary from the latest sdk platform-tools packages.

Windows: Tried again to fix system.img building for a few unlucky users still having issues with permissions.

Windows: Clean up project directory if system.img build fails due to permissions.
[SuperR Kitchen] SuperR.:
v3.1.8.5

Changes:

Linux: Fixed pulling img files from device while booted to rooted Android.

Linux: Fixed building zip files with parenthesis in name.

Windows: Fixed some languages not displaying properly in the menu status fields.

Added dead project message when choosing SuperSU root method and ask for confirmation.

Moved Magisk to option 1 in the root menu.

Actually delete the custom directory after you say yes to remove it.

Use project srk.conf to store directories included in the ROM from the mods_install plugin.

Added suggestion to change USB mode on device from charging to file transfer (MTP) if stuck when pulling img files from Android.

NOTES:

The mods_install plugin has also been updated.

Now you can choose the name of the mod directory instead of mod1, mod2, etc.

This new plugin will not work properly with v3.1.8.4 and below. It will run, but the mods you add will not be included in your ROM. Please update to v3.1.8.5 to use this updated plugin.
[SuperR Kitchen] SuperR.:
v3.1.8.6

Changes:

Added check in configure.sh to be sure SLOT equals either _a or _b before using it.

Refactored code to use a color dictionary instead of an import.

Send color dictionary to plugins.

Send kitchen version to plugins.

Strip trailing spaces and line endings from each line in bloat_custom before searching.

Allow sparse_dat perm type on system-as-root (slot a/b) devices.

NOTE:

All plugins have been updated to work with the new color dictionary. The old plugins will not work in v3.1.8.6+ and the new plugins will not work in v3.1.8.5-. The easiest way to solve this is to update to v3.1.8.6 and then check for plugin updates in the plugin manager.

NOTE2:

The following plugins are now obsolete and have been removed from the server:

omc_decode

sam_81deo_patch

samextras

tar_md5_create

There is a new plugin, samsung_tools, that includes all of the above functionality :)
[SuperR Kitchen] SuperR.:
v3.1.8.8

Changes:

Fixed ROM build error when there are special characters in the ROM name.

Windows: Fixed make_ext4fs not setting symlinks context properly when using file_contexts3-*.

NOTE:

Quick update to be sure everyone gets the new make_ext4fs binary :)
[SuperR Kitchen] SuperR.:
v3.1.8.9

Changes:

Fixed support.zip uploads.

Windows: Added option in Misc Tools to use make_ext4fs.exe.

Explanation of the new Windows make_ext4fs.exe option:

Some history. The kitchen used make_ext4fs.exe to build ext4 img files until v3.1.6.9. At this time, there were some system.img files that were not building properly and would not extract after building. I came up with a workaround using the Linux make_ext4fs binary. This is what we have been using since then. It fixed the issues we were having at the time, but has since created new challenges like renaming system to fakefs and back. I think even those issues are fixed now.

However, since the usage of file_contexts3 files was introduced in v3.1.8.7, some people are having issues building ext4 img files with the proper contexts. I am not sure why this only happens on certain PCs, but it does.

I believe the reasons the old make_ext4fs.exe had issues were file context and symlink related. I believe these issues are now fixed.

I compiled make_ext4fs.exe with all the new updates including file_contexts3 usage. This will not be used as the default right now as there has not been much testing. However, once updated to v3.1.8.9 you can go to Misc Tools > Use make_ext4fs.exe. This toggle is changeable between "Yes" and "No".

If you change the setting to "Yes", the new make_ext4fs.exe will be used to build your ext4 img files. If the setting is "No" (default), the Linux make_ext4fs workaround will be used (same as v3.1.6.9 - v3.1.8.8). It is a kitchen setting and will be used for all projects.

My experience has been perfect ext4 img creation with both the Linux workaround and the new make_ext4fs.exe. It is difficult to troubleshoot issues I am not able to reproduce, so please let me know how this goes if you decide to try it. Thanks :)
[SuperR Kitchen] SuperR.:
v3.1.9.0

Changes:

Fixed make_ext4fs not setting a context if file not found in file_contexts3-*.

Use kitchen generated file_contexts file as the backup when building an ext4 img and a file does not exist in file_contexts3-*.

If file_contexts causes an error, generate a minimal file_contexts to use as the backup and try again.

Update individual tools that have changed instead of downloading the entire tools zip each time a binary is updated.

Added support for extracting firmware with SpreadTrum pac files.

Try all downloads 5 times before giving up, with hope that AIK downloads will work better.

Reset All Tools is now more like refresh all tools, meaning we compare the checksums and replace only if they do not match.

NOTE:

I believe this will fix the remaining issues with ext4 img creation.

Windows: This version still has both make_ext4fs.exe and the Linux make_ext4fs workaround. To get the full functionality of this update, you should enable make_ext4fs.exe in the Misc Tools menu. The only real difference is that the Linux make_ext4fs workaround will not try again if the file_contexts file generates an error. This error has only happened on one firmware so far that I am aware of so it is a rare issue. However, only the make_ext4fs.exe method tries again with a minimal file_contexts file if it does happen.

Please let me know if there are further issues with ext4 img file creation by sending a support.zip after the build. Thanks :)

Thanks to [MENTION=4694583]malchik-solnce[/MENTION] for testing several things I could not reproduce :)
[SuperR Kitchen] SuperR.:
v3.1.9.1

Changes:

Linux/Mac: Fixed tools not getting set executable until after reboot when resetting tools, causing the reset to quietly fail.

Linux/Mac: Added fallback options to extract ext4 img files; 1 by mounting; 2 by using 7-zip.

Windows: Added fallback option to extract ext4 img files by using 7-zip.

Windows: Fixed kitchen hanging due to lack of permissions to delete some unpacked boot.img directories.

Mac: Fixed mac_tools not downloading during initial setup.

Reduced ext4 extraction time for all perm types except set_metadata by only preparing metadata when set_metadata is selected.

Added option in Misc Tools > Flashable zip options, to control the ROM zip compression level (0,1,3,5,7,9)(default is 5).

update-binary conversion options have a new menu under flashable zip options, and the settings are now global.

Fixed more ext4 img builds by searching for additional error codes in the output that trigger a retry.

Misc code cleanup.

EXPERIMENT: Added config option (brotli_comp) to build sparse_dat with dat.br files instead of dat; Specify brotli compression level (0-9)(default is 0).

NOTES:

The new dat.br config option allows you to create for example, system.new.dat.br instead of system.new.dat, and allows you to set the brotli compression level (0-9). See below for a usage example.

Open the file kitchen/tools/srk.conf

Add the following line, changing the 0 to the desired compression level (0-9)

brotli_comp=0

Save the file

Build a ROM.zip with sparse_dat perm type

IMPORTANT: In Windows, make sure you use an editor that supports Unix line endings to edit srk.conf. Notepad++ is one such program.

The update-binary in the kitchen will probably not work with dat.br files. I am trying to figure out a solution. In the meantime, if your original firmware is dat.br you can use the update-binary from there. Just replace it in the META-INF directory in your project before building your ROM zip. Once I figure out a solution, I will add a menu entry to turn it on/off.
[SuperR Kitchen] SuperR.:
v3.1.9.2

Changes:

Mac: Added support for sepolicy patching (thanks [MENTION=5617466]Andmoreagain[/MENTION] for fixing the bootimg binary).

Fixed crash when choosing set_metadata perm type.

NOTE:

sepolicy_injector plugin also updated to allow Mac to patch sepolicy.
[SuperR Kitchen] SuperR.:
v3.1.9.3

Changes:

Windows: Request administrator privilege to modify ramdisk files if .su file and/or .backup/.subackup directory exists.

Windows: Only request administrator privilege to delete ramdisk if .su file and/or .backup/.subackup directory exists.

Fixed crash if we find a malformed symlink in a system.img during extraction.

Removed concatenation of system_*.*img files from the kitchen extractor in favor of the concatimg plugin.

Do not move boot.img or ramdisk to/from the AIK directory (Thanks to [MENTION=4544860]osm0sis[/MENTION] for making this possible!!).

Fixed AIK downloads not working consistently (Thanks to [MENTION=4544860]osm0sis[/MENTION] for allowing private AIK links!!).

Use new update-binary in sparse_dat ROMs to allow flashing dat.br (Thanks to [MENTION=1162986]Captain_Throwback[/MENTION] for modifying and compiling!!).

Also updated the concatimg plugin.
[SuperR Kitchen] SuperR.:
v3.1.9.4

Changes:

Added menu option to enable/disable brotli compression for sparse_dat ROMs.

Fixed adding dat.br.br to updater-script when brotli compression is enabled.

Fixed crash if quit is chosen after downloading a new language.

Fixed crash during Android Q deodex (Q deodex will be supported if/when vdexExtractor supports the new dex version).

The new brotli menu option is located:

Misc Tools > Flashable zip options (global) > sparse_dat brotli compression (dat.br)

NOTE: The file downloads have moved to a new host in this version, and the old host is no longer working. New installs of older kitchen versions will fail because the downloads no longer exist. New installs of v3.1.9.4 and existing installs of lower versions will work without issue.