{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My flashable firmware zips include bootloader, modem and latest twrp recovery for your device,
they do not update your ROM.
I'm only using XEU Firmware, no country specific/carrier files.
Supported Devices:
SM-G95XF, G95XFD
You only have to flash the latest zip file in twrp, your device will auto-reboot and boot up with latest firmware and twrp installed.
TWRP-Flashable Firmware Updates
OP STILL UNDER CONSTRUCTION.
Code:
Please do not take anything without asking me first. I will 99% allow you to use anything, just ask first though.
You cannot use any of my work which hasn't been released in an official release unless given express permission.
I'm not responsible for anything that happens to your device while using this files.
By using my files you agree with the above terms.
XDA:DevDB Information
[G95xF/FD] TWRP Flashable Firmware Updates, Tool/Utility for the Samsung Galaxy S8
Contributors
SoLdieR9312
Version Information
Status: Nightly
Created 2017-08-16
Last Updated 2018-09-17
Found you. Nice one mate
sent from dans R.I.C.E powered V8+ on one of jesses kernels
Great work [emoji6][emoji16]
@SoLdieR9312
Welcome & thanks for this!
Hängt in Samsung logo kein booten. Bin nach der obigen Anleitung vorgegangen
You need a ROM on AQG5 or higher, it'll not boot with old software. In addition zips confirmed working by 30+ others, so something at your end.
Danke, werde mich mal damit beschäftigen
help, i stuck on bootloader, i try to flash recovery not odin keep showing failed
Thanks for doing this!
Easier access for more people than directing them to, say, the Renovate website.
I have a question (or suggestion), if you don't mind: is there a reason why flashing the firmware zip entails an auto-reboot?
Maybe it's only me, but when I flash a ROM and firmware on other devices, it didn't matter what order I flashed the ROM or firmware. An auto-reboot script necessitates that firmware be last in the TWRP flash queue, and that a ROM be flashed first (when clean flashing).
This is not a criticism at all, I'm just honestly wondering why auto-reboot is there... Is it a safety reason?
Thanks for any info!
reaper000 said:
Thanks for doing this!
Easier access for more people than directing them to, say, the Renovate website.
I have a question (or suggestion), if you don't mind: is there a reason why flashing the firmware zip entails an auto-reboot?
Maybe it's only me, but when I flash a ROM and firmware on other devices, it didn't matter what order I flashed the ROM or firmware. An auto-reboot script necessitates that firmware be last in the TWRP flash queue, and that a ROM be flashed first (when clean flashing).
This is not a criticism at all, I'm just honestly wondering why auto-reboot is there... Is it a safety reason?
Thanks for any info!
Click to expand...
Click to collapse
I think u need to reboot to apply changes
reaper000 said:
Thanks for doing this!
Easier access for more people than directing them to, say, the Renovate website.
I have a question (or suggestion), if you don't mind: is there a reason why flashing the firmware zip entails an auto-reboot?
Maybe it's only me, but when I flash a ROM and firmware on other devices, it didn't matter what order I flashed the ROM or firmware. An auto-reboot script necessitates that firmware be last in the TWRP flash queue, and that a ROM be flashed first (when clean flashing).
This is not a criticism at all, I'm just honestly wondering why auto-reboot is there... Is it a safety reason?
Thanks for any info!
Click to expand...
Click to collapse
You need a special reboot to save firmware to phone. If you just go back to twrp and flash something other, firmware will not saved. So no way to remove the auto reboot at the end.
SoLdieR9312 said:
You need a special reboot to save firmware to phone. If you just go back to twrp and flash something other, firmware will not saved. So no way to remove the auto reboot at the end.
Click to expand...
Click to collapse
Hi @SoLdieR9312, because of this fact, should I flash the rom first, ej. Renovate 4.0 under TWRP 3.1.1.1 and then secondly this frmware? Thanks.
Yeah you can do so.
can I use it with stock firmware too?
Only if you are using TWRP already.
opps, no mirrors found??
probably afh issues again, try on pc or try again later
I just tried the update from AQDG to AQH3, and it totally soft-bricked my phone, I even had to reflash TWRP, but it still does not boot. Anything I might be doing wrong here?
AQH3 needs a AQG5 or higher software to boot.. you probably was on old, because your fimrware is the first one that came with s8 in april Oo
You need to update mate.
Is there any new bootloader/modems for the S8+ note 8 ports or still AQH3
Sent from my BadBwoi-S8+ using XDA Labs
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why use this ROM ???
For the simple reason that if you like having the latest official update without modifications to make things your way, but want to have bugs that lead often changes made by developers, if you want to keep track unlocking the bootloader (there were rumors that in an update could become blocked from using Bump! to release the bootloader and would lose all ability to install roms.
Features:
Last Firmware D855
Root & Busybox
Adblock Host
Removed gapps that are available in playstore (book, magazine, youtube, gmail, chrome, hangout etc.)
Disabled LG OTA (I will only disable firmware updates, the apps for the lg will be available without problem).
Installation:
Root & TWRP (http://forum.xda-developers.com/lg-g3/orig-development/bump-unlock-lg-g3-twrp-d852-d852g-f400-t2900614)
Download Zip and copy
Reboot in TWRP
Full Wipe (Dalvik, Cache, System & Data if it is the first time you install, should be a next update reaches only to wipe cache and dalvik but mistakes is advisable to perform a clean installation)
Install Zip
Reboot
WARNING !!!!
The rom only contains what is described above, the rest is 100% stock. The installer performs the same only wipe system alone so the other wipes borne by each user.
Excludes bootloader and modem, only system and kernel.
DOWNLOAD
Thks: Cloudy (script root and busybox), thecubed (bump!)
ScreenShot Last Firmware...
Can't wait to try
Sounds very promising. Will be checking this page frequently throughout the day . Thank you!!
Do put up flashing instructions in the 1st post once uploading completes. Thanks for your efforts. Much appreciated !
Nice !
Thanks !
I'm currently on AndroidNow HD 1.7. How would I flash this? Would I be ok to do an advance we(system,data,cache & dalvic) and just flash from there?
Yes
Thank you!
What's the kernel build date of this version?
freaked9 said:
Thank you!
What's the kernel build date of this version?
Click to expand...
Click to collapse
Oct 22 20:42:38 KST 2014
Link aviable
Im running stock D855 - software 10i - is it OK to dirty flash this to keep all my other stuff and really just add the benifits of the new firmware?
Cheers.
trying this when ready thanks
Vivasanti said:
Im running stock D855 - software 10i - is it OK to dirty flash this to keep all my other stuff and really just add the benifits of the new firmware?
Cheers.
Click to expand...
Click to collapse
For once maybe you do it first and share your experience with us.
Vivasanti said:
Im running stock D855 - software 10i - is it OK to dirty flash this to keep all my other stuff and really just add the benifits of the new firmware?
Cheers.
Click to expand...
Click to collapse
when you flash with lg flash tool you have to cse flash that you dont get errors... i dont know but it may be that you must do a full wipe.
but try it and share it with us
Flashed and all ok did try dirty flash and phone booted ok but couldnt unlock home screen so had to use adb reboot to bump twrp. There did full wipe and install all is good
this is official firmware flash with recovery !?
steveria79 said:
this is official firmware flash with recovery !?
Click to expand...
Click to collapse
Yes do full wipe
So how do we flash this then Op thanks in advance
Sent from my LG-D855 using XDA Free mobile app
Post updated...
Great work thank you ☺
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OFFICIAL DOWNLOADS FOR SUZU:
https://twrp.me/sony/sonyxperiax.htmltwrp-3.x.x_x-x-suzu.img: Official TWRP image
DEVELOPMENT DOWNLOADS FOR SUZU:
Folder: https://sourceforge.net/projects/loire-development/files/twrp-recovery/suzu/twrp-3.x.x_x-x-YYYYMMDD-suzu.zip: Flashable unofficial TWRP to FOTAKerneltwrp-3.x.x_x-x-YYYYMMDD-suzu.img: Unofficial TWRP image
INSTALLATION
MANUALLY TO FOTAFastboot: Adapt the image name and install this way:fastboot flash recovery twrp-3.x.x_x-x-suzu.imgfastboot rebootFROM EXISTING RECOVERY
Enter to the current recovery
Install flashable TWRP
Reboot/Power off
HOW TO ENTER TO THE RECOVERY:
Power off your phone
Press Power and Vol- buttons at the same time until vibration
Wait for TWRP load
Sources:
TWRP device tree: https://github.com/TeamWin/android_device_sony_suzu/tree/android-9.0Kernel: https://github.com/Chippa-a/kernel-copyleft/tree/34.4.A.2.xxxThanks to the TWRP Team!
Backup-Restore function working fine so far, only issue I am seeing is phone is heating up pretty faster than before while backing up in compression mode.
Another minor thing is that earlier when entering recovery mode a purple light used to blink, now its missing.
Just saw this now and I'm really grateful. Big ups to you, man. Great work.
And I was afraid there would be no 3.2.1 for this device;
@Chippa_a makes it possible - intensified thanks! :highfive::good::good:
Thank you!!
I can't flash the zip because twrp does not give access to that part of the storage, weird.
fusk said:
I can't flash the zip because twrp does not give access to that part of the storage, weird.
Click to expand...
Click to collapse
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Updated from TWRP, backup/restore works, no problems so far apart from it needs more than a minute till TWRP GUI appears after boot. Thanks for update.
Do you use the stock kernel? I installed the recovery built by oshmoun in the omnirom thread. It uses the aosp kernel. It starts faster, has a better sdcard naming and can flash oem images. Maybe you could try this kernel.
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
I mean the kernel used with the recovery, not the rom kernel.
I_am_Blackford said:
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Click to expand...
Click to collapse
This is what i did. Download img, place file on phone. Download twrp app, pick choose a file, browse to recovery.img, flash. Power off, boot to recovery = win.
Reboot to system, retry installing new update = great success.
mase76 said:
I mean the kernel used with the recovery, not the rom kernel.
Click to expand...
Click to collapse
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
privatim said:
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
Click to expand...
Click to collapse
I dont know if there is a connection, but i've tested the recovery with OmniROM 7.1.2, where display is not responding. It can be installed, shows 3.2.1, but display remains dead 4 touch.
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
mase76 said:
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
Click to expand...
Click to collapse
Same result, whether fastboot or flashtool, display is dead.
Certainly missed ODM LOIRE v12, v11 is installed.
Not really sure is the latest bootloader.
Does restoring a backup change the bootloader as well?
Edit: Solved: the answer is 'yes'.
3.2.1 does not work @7.1.2 restore because of outdated bootloader.
privatim said:
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
Click to expand...
Click to collapse
Moved to XGEN ROM and now TWRP starts without delay. :good:
privatim said:
Moved to XGEN ROM and now TWRP starts without delay. :good:
Click to expand...
Click to collapse
What I do not understand, maybe bootloader or encryption, but why is 3.2.1 not backwards compatible on Suzu?
Is Omni 7.1.2 kernel (more I have not tried) or not current boot loader the reason?
Installed on last nougat internal storage 0 help
Inviato dal mio F5121 utilizzando Tapatalk
I'm glad that you finally managed to crack this damn decryption. I felt really bad with my broken promise of delivering the working build. I'm sorry, guys. @Chippa_a congratulations on your hard work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Hi to all dear Z3c users. This is my first TWRP build, I used omni minimal TWRP source and kernel from Sony git.
I hope you enjoy this.
How to install
Fist of all you MUST flash lastest 23.5.A.1.291 firmware with FlashTool at least one time, for upgrade the bootloader (You need this upgrade for boot on recovery).
Via fastboot
Reboot your phone on fastboot mode.
Flash recovery using this command:
Code:
fastboot flash FOTAKernel <filename>
Via zip (You need a working recovery installed)
Download the zip and put it on your internal or external memory.
Reboot to recovery.
Flash the zip.
Via Official TWRP App (You need root)
Install the app from Google Play Store and download the zip.
Extract recovery.img and copy it to your internal or external memory.
Open the app, give root permissions and tap on TWRP FLASH.
Tap on Select a file to flash...
Select the recovery.img and flash it.
Download
TWRP
Thanks to
@GreyLeshy a lot of thanks for this great dev, he helped me a lot for make this possible, build this recovery and he had a lot of patience with this noob dev.
@Dees_Troy for TWRP.
omni Team for TWRP Minimal Source.
XDA:DevDB Information
TWRP for aries, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
ShadowElite, GreyLeshy
Source Code: https://github.com/ShadowElite117/android_sony_shinano_twrp/tree/aries
Version Information
Status: Stable
Created 2018-09-01
Last Updated 2018-09-02
FAQs
Q. How boot on recovery?
A. With the device turned off, press power and vol- at same time until it vibrates.
Q. Does it works with stock or custom ROMs?
A. At this momment I know that it is fully compatible with stock ROMs (or stock based ROMs) but at this momment is not tested with custom ROMs, so you users have to test it and report.
Installed the TWRP 3.2.3-0 on CarbonROM 6.1 (Android 8.1). So far so good, seems alright to me.
neckronus said:
Installed the TWRP 3.2.3-0 on CarbonROM 6.1 (Android 8.1). So far so good, seems alright to me.
Click to expand...
Click to collapse
Yeah but the question is if this recovery works for flash custom ROMs, I know that it work perfectly with stock roms, if you can test it and report here, I really apreciate.
ShadowElite said:
Yeah but the question is if this recovery works for flash custom ROMs, I know that it work perfectly with stock roms, if you can test it and report here, I really apreciate.
Click to expand...
Click to collapse
Just tried flashing the latest Carbon and it worked for me. Haven't tested flashing stock ROMs myself though
Just tried to install the zip on my Z3 compact.
My phone has full encryption enabled (complete including the sd card).
Your build of TWRP is not able to decrypt the phone.
It always tells me "Password failed, please try again!" even though the given passsword is correct (I can start the system with the same one).
amazing
Installed on OMNI with TWRPapp, flahed Carbon and then RR.
All it was fine and, finally, no "Error 7".
Thank you for this!
I have a question, I have encrypted my device (CarbonRom cr6) and now when I try to access TWRP I draw my security pattern and I get a failed to decrypt message.
The pattern is the one I use on a daily basis to use my device so this is related to TWRP. Any suggestion?
Maybe this twrp has a problem with support encription?
Carbon ROM expects TWRP with ro.build.product or ro.product.device equal z3c (not aries) . Modified original image using this method https://forum.xda-developers.com/t/...because-of-empty-system.3554252/post-85881113
For Lineage (18.1), this (3.3.1) TWRP version is recommended, but it seems to have issues preserving the survival scripts (e.g. of Magisk) over OTAs. Unfortunately, the device isn't supported on twrp.me
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Hi,
I recently did the same but on purpose. This was advised in the Syberia OS ROM installation instructions. https://forum.xda-developers.com/poco-f1/development/rom-syberia-project-t3862622
You might want to try that(format data, install newest vendor+firmware etc) and then try to install a custom ROM.
SirSitu said:
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Click to expand...
Click to collapse
If you're stuck you can back to stock with fastboot rom
Boot to fastboot and launch Xiaomi Flash on your pc.
SirSitu said:
Hello xdadevelopers,
I recently bought myself the Poco F1 and tried to follow LTT's guide on how to make the Poco F1 like a Pixel, but I accidentally wiped everything (by going into additional settings and clicking every box). I can still access TWRP, but can't seem to install the custom rom (errors).
Is there anything I can do to continue with the process of making my phone like a pixel? I'm still a major novice in this so if possible, please use layman terms.
Thanks a lot,
Sirsitu
Click to expand...
Click to collapse
The best thing that you can do is flash the latest fastboot stock ROM available. It'll reset the phone to as if it was new and also lock the bootloader. But you can unlock it back without the waiting time this time.
FieryAura said:
If you're stuck you can back to stock with fastboot rom
Boot to fastboot and launch Xiaomi Flash on your pc.
Click to expand...
Click to collapse
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
Use the latest unofficial twrp, format data, wipe everything and install beta from 24/12 EU (xiaomi.eu)
Share your results afterwards
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
Try this version its older but compatible with miflash:
http://bigota.d.miui.com/V10.0.6.0....FH_20181113.0000.00_8.1_global_ad6e716a76.tgz
SirSitu said:
I've downloaded Xiaomi Flash and the stock rom, but when I try to flash it in, I get an error saying "can not find file flash_all_lock.bat" I think I've bricked my phone
Click to expand...
Click to collapse
That't not fastboot flashable file, genius. You are trying to flash the full ROM file. Download the fastboot file which comes in .tgz format. Extract it twice and you will get the main file. Once you extract the file, you would see the file name has a lot of "underscore" (_) marks See the attached screenshot). Moreover, you didn't mention what errors are you getting on TWRP while trying to flash the custom ROM. When creating a thread, try to include as much information possible, i you want someone to understand your problem and help you accordingly. Or else, you are just adding up thread counts.
---------- Post added at 14:24 ---------- Previous post was at 14:23 ----------
123Opie said:
Try this version its older but compatible with miflash:
http://bigota.d.miui.com/V10.0.6.0....FH_20181113.0000.00_8.1_global_ad6e716a76.tgz
Click to expand...
Click to collapse
LOL! All stock fastboot ROMs are compatible on MiFlash tool. It doesn't matter which version it is as long as it is fastboot flashable and you know how to extract and place it in the correct place.
"LOL! All stock fastboot ROMs are compatible on MiFlash tool. It doesn't matter which version it is as long as it is fastboot flashable and you know how to extract and place it in the correct place."
Yeah but from what I can see on this is just a normal firmware and has to be updated thru twrp or settings.
But that older version has a fastboot version to flash idk though.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
SM-T860 that is unlocked, rooted with Magisk, TWRP recovery installed, WETA Kernel installed, running ASK1 November security update firmware.
I'm not new to rooting and all, but am fairly new to Samsung devices and am still learning all the tricks and tips.
I know that OTA updates are not possible in my current state, but Is it possible to some way manually update the firmware to the ASL3 version without having to just reflash stock and loose everything, starting from scratch to reroot, TWRP, reinstall all my apps etc?
I already have Odin installed and have downloaded the full ASL3 firmware package.
You don't have to lose everything - just flash ASL3 on top of ASK1, then install the rest of the mods (WETA kernel, TWRP, Magisk). In the downloaded zip of ASL3, you should have five files: mostly the same file names, except for the beginning few characters, similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So the five images you'll most likely have are AP (the main system + boot.img), BL (bootloader, modem, other low level stuff), CP (other small tidbits), CSC (carrier-specific customizations, also contains country-specific stuff, basically the layer above system that makes the OS specific to a country, with apps, configurations for WiFi, 4G/5G, Bluetooth, and even things like Samsung Pay), and HOME_CSC (same as CSC, but doesn't flip the "wipe device" flag).
What you need to do is do the update via ODIN using the default files, then for the CSC field, select HOME_CSC instead of the regular CSC file. The only difference between the two is just this, HOME_CSC won't wipe the device, CSC will.
Same applies if you want to go back to complete stock, just flash the phone using ODIN, and use the regular CSC image instead of HOME_CSC.
Thank you for the detailed explanation of what to try and what all of the different parts of the big firmware packages are. I've had this Tab S6 just about a month now and have been doing my best to get used to how Samsung does things. Lots of reading various posts, lots of experimenting. I've gotten the basics down on flashing firmware using Odin, but don't yet have a solid grasp on what all is really going on. I've just been very carefully following directions, and praying to the Android/Samsung gods I don't end up with a brick when I hit "start." LOL So far so good!
I'll give it a go doing what you described. If it works, Yay! If not, no big deal and I'll start over from fresh/stock. I've grown used to that being "just the way it is" when you want to run modified/custom stuff. As long as I don't permanently brick the thing I do enjoy the experimenting and learning process.
Thanks again.
ragtop429 said:
Thank you for the detailed explanation of what to try and what all of the different parts of the big firmware packages are. I've had this Tab S6 just about a month now and have been doing my best to get used to how Samsung does things. Lots of reading various posts, lots of experimenting. I've gotten the basics down on flashing firmware using Odin, but don't yet have a solid grasp on what all is really going on. I've just been very carefully following directions, and praying to the Android/Samsung gods I don't end up with a brick when I hit "start." LOL So far so good!
I'll give it a go doing what you described. If it works, Yay! If not, no big deal and I'll start over from fresh/stock. I've grown used to that being "just the way it is" when you want to run modified/custom stuff. As long as I don't permanently brick the thing I do enjoy the experimenting and learning process.
Thanks again.
Click to expand...
Click to collapse
Please tell me how it goes!
Daniel Hjelvik said:
Please tell me how it goes!
Click to expand...
Click to collapse
Well, it worked... sort of. The system booted and ran, but I started to get random reboots for no apparent reason. I wiped cache and such but nothing helped.
Ultimately I decided to completely wipe the tablet, flash back to stock, and then reroot and just reinstall everything "clean."
Did you apply TWRP and the WETA kernel again? If so, my gut is that the old kernel is not compatible with the updates. Just my thoughts, nothing to support this but an update should work. This is one of the reasons I am waiting till the updated TWRP is released with the new SL3 kernel.