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.
Related
I have posted about my problem in several threads now, but I didn't get an answer yet, so I hope I can finally save my phone with your help here... It's been a major pain the cojones for two weeks already.
In short, here is what happened:
I unlocked the bootloader, installed TWRP and after flashing superSU (once I found out how to get into TWRP), I got a bootloop.
So I wanted to do a full wipe. But I messed up and wiped literally everything, even the OS
Then I went on to look for a stock ROM zip file. I found one, but I didn't read the whole article which said it was for H901. I installed it and found out it's branded T-mobile version on top of all.
Now I'm trying to get back to a H960A stock ROM, but no luck so far.
I have tried both methods from the LG V10 Stock Firmware (Go Back to Stock) KDZ & TOT Method thread
Then there was a shed of hope when I stumbled upon this thread, where the OP managed to do the same
http://forum.xda-developers.com/lg-v10/help/flashed-h901-h960-comrade-to-help-t3429025
I downloaded the modified Switzerland file mentioned in one of the comments, but it didn't do through for me.
I also tried to run the chkdzdev tool to change my EU version KDZ file, but agian, I got the same error (possibly I didn't do it right, since there is no manual whatsoever and the author doesn't reply)
Here is a screenshot of how it went:
{
"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 now, my only hope is to:
a) find a zip with H960A stock ROM (probably none exists on the interwebz)
b) find a TWRP backup that I can "revert" to (not sure if this would work, but if anyone would be so kind, I could find out...)
c) find someone who can modify the KDZ file and tell me how to do it
Anyone?
I messaged a good source about your problem, with any luck he will provide us with a nandroid for you to restore. I'll let you know as soon as I hear back.
If I helped you, please hit the "like" button. Thank you.
RealWelder said:
I messaged a good source about your problem, with any luck he will provide us with a nandroid for you to restore. I'll let you know as soon as I hear back.
If I helped you, please hit the "like" button. Thank you.
Click to expand...
Click to collapse
Any news?
Or anyone has any idea how do I fix this?
Anyone has any idea where to turn for help with this issue? If not on xda, where can I look for a solution?
Try this. There is some instructions here that might be different from what you've been trying.
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
It's saying after you load the firmware into LGUp, you have to close it and then open it again, select refurbish, and then make sure bin file is checked. Hopefully this can get you going. Good luck.
If I helped you, please hit the "like" button. Thank you.
RealWelder said:
Try this. There is some instructions here that might be different from what you've been trying.
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
It's saying after you load the firmware into LGUp, you have to close it and then open it again, select refurbish, and then make sure bin file is checked. Hopefully this can get you going. Good luck.
If I helped you, please hit the "like" button. Thank you.
Click to expand...
Click to collapse
I've tried this one... it wouldn't even let me load the kdz file without doing this...
Problem is, the firmware version is coded somewhere deep in the file and it won't let me install it on a device that has a different version (unfortunately mine was overwritten by the stupid stock ROM i've managed to install)
I thought it was time I sought some advice. I have been trying for several days to flash an upgraded ROM onto my wife's i545 model. The phone was bought by mailorder and we live in Australia. I have previously rooted my own phone; the biggest reason being to remove the obnoxious - check your battery cover - popup.
I have been able to root the phone with Kingroot.
So I 've been trying to flash an upgrade from Odin, but I can't find an appropriate tar or tar.md5 file. Scores of zips are available, but tar.md5s are nowhere to be found. I tried making my own tar.md5 from a youtube video. Basically, this involved using 7-zip to change a zip (I used cm12.1 and 13.1 direct from their website) into a tar file, and then using Cygwin to change it into an md5. When I load these home-created tar.md5s into Odin and press Start, Odin crashes.
I've also attempted to flash a recovery from the device itself, with twrp, clockworkmod and others. The flashing is "successful", but when I try to reboot to recovery, the device stops and says the bootup has failed.
So what suggestions do the experts have? Are the tar.md5s I created valid? Or are their valid tar.md5s available on the web? Is there something about this phone which prevents the bootup into recovery? The original complaint was the wi-fi connection. I also tried flashing a new kernel SCH-I545_MD2_423399_Kernel.tar.md5 and SCH-I545_MD2_562219_Kernel.tar.md5, philz_touch_6.48.4-hlte.tar.md5, TWRP-2.5.0.0-devjfltevzw.tar.md5, and TWRP-2.6.3.1-devjfltevzw.tar, all of which fail.
I've also tried Flash-Fire which insists the phone isn't rooted, although root-checker says it is, and Flashify which has the same problem of appearing to work but then booting up to error.
BillSchutt said:
I thought it was time I sought some advice. I have been trying for several days to flash an upgraded ROM onto my wife's i545 model. The phone was bought by mailorder and we live in Australia. I have previously rooted my own phone; the biggest reason being to remove the obnoxious - check your battery cover - popup.
I have been able to root the phone with Kingroot.
So I 've been trying to flash an upgrade from Odin, but I can't find an appropriate tar or tar.md5 file. Scores of zips are available, but tar.md5s are nowhere to be found. I tried making my own tar.md5 from a youtube video. Basically, this involved using 7-zip to change a zip (I used cm12.1 and 13.1 direct from their website) into a tar file, and then using Cygwin to change it into an md5. When I load these home-created tar.md5s into Odin and press Start, Odin crashes.
I've also attempted to flash a recovery from the device itself, with twrp, clockworkmod and others. The flashing is "successful", but when I try to reboot to recovery, the device stops and says the bootup has failed.
So what suggestions do the experts have? Are the tar.md5s I created valid? Or are their valid tar.md5s available on the web? Is there something about this phone which prevents the bootup into recovery? The original complaint was the wi-fi connection. I also tried flashing a new kernel SCH-I545_MD2_423399_Kernel.tar.md5 and SCH-I545_MD2_562219_Kernel.tar.md5, philz_touch_6.48.4-hlte.tar.md5, TWRP-2.5.0.0-devjfltevzw.tar.md5, and TWRP-2.6.3.1-devjfltevzw.tar, all of which fail.
I've also tried Flash-Fire which insists the phone isn't rooted, although root-checker says it is, and Flashify which has the same problem of appearing to work but then booting up to error.
Click to expand...
Click to collapse
The Verizon S4 had a locked bootloader. A custom recovery is not possible with the latest firmware. You can root using the methods in the General section. After you have root you can use Flashfire to flash zips. Stock firmware can be found at www.sammobile.com in case you screw up or get a bootloop. I recommend getting rid of KingRoot su for SuperSU. There is a YouTube video on doing it.
{
"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"
}
I have an S4 on MDK had TWRP 2.6.? on it, has been working great many ROMS.
I installed the official TWRP App, backed up my recovery to recovery.img and installed the latest TWRP 3.1.1 I think.
Upon reboot I now get the dreaded error mentioned above and that many others have gotten. I can boot into download mode but not into recovery. I've gone through the threads from others with this issue, but since I'm on MDK wanted to confirm the next likely step. (I think this guy has same issue as me https://forum.xda-developers.com/galaxy-s4-verizon/help/help-unauthorized-software-message-t3316858)
Do I likely just need to find MDK stock firmware and apply via ODIN and go from there? Or since I am on MDK does it not matter if I restore stock MDK.
I don't really care if I restore MDK or not but I"m having trouble finding the original stock MDK sammobile doesn't have it for example. I'm wondering if I can just use say:
- I545_OC1_Stock_Rooted_ROM (MDK Bootloader Users Only)
From
https://forum.xda-developers.com/ga...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
thanks!
generalnod said:
I have an S4 on MDK had TWRP 2.6.? on it, has been working great many ROMS.
I installed the official TWRP App, backed up my recovery to recovery.img and installed the latest TWRP 3.1.1 I think.
Upon reboot I now get the dreaded error mentioned above and that many others have gotten. I can boot into download mode but not into recovery. I've gone through the threads from others with this issue, but since I'm on MDK wanted to confirm the next likely step. (I think this guy has same issue as me https://forum.xda-developers.com/galaxy-s4-verizon/help/help-unauthorized-software-message-t3316858)
Do I likely just need to find MDK stock firmware and apply via ODIN and go from there? Or since I am on MDK does it not matter if I restore stock MDK.
I don't really care if I restore MDK or not but I"m having trouble finding the original stock MDK sammobile doesn't have it for example. I'm wondering if I can just use say:
- I545_OC1_Stock_Rooted_ROM (MDK Bootloader Users Only)
From
https://forum.xda-developers.com/ga...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
thanks!
Click to expand...
Click to collapse
If you can find a tar of TWRP you could probably just Odin that and it should fix everything. Don't use the TWRP app, it's junk and pretty much useless. It just causes problems. Use TWRPs website https://TWRP.me
{
"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"
}
bilgerryan said:
If you can find a tar of TWRP you could probably just Odin that and it should fix everything. Don't use the TWRP app, it's junk and pretty much useless. It just causes problems. Use TWRPs website https://TWRP.me
Click to expand...
Click to collapse
thanks for the reply i gave that a whirl but it gives me a FAIL in odin, I tried a few different twrp tars and odin versions.
Any thoughts on if this firmware might work (or do you happen to know another)
- I545_OC1_Stock_Rooted_ROM (MDK Bootloader Users Only)
From
https://forum.xda-developers.com/gal...k-mdk-t3097902
as I'm still unable to find any good links to the original stock for MDK
generalnod said:
thanks for the reply i gave that a whirl but it gives me a FAIL in odin, I tried a few different twrp tars and odin versions.
Any thoughts on if this firmware might work (or do you happen to know another)
- I545_OC1_Stock_Rooted_ROM (MDK Bootloader Users Only)
From
https://forum.xda-developers.com/gal...k-mdk-t3097902
as I'm still unable to find any good links to the original stock for MDK
Click to expand...
Click to collapse
It could, my device was definitely not on MDK when I had it.
Can you get your phone to start up normally again? If so, gomangoman may be able to help you out. I got an MDK unicorn and had the same issue. If you re-flash TWRP through Flashify it fixes the problem. At least it did for me! See post 593 on this page:
https://forum.xda-developers.com/showthread.php?t=2292565&page=60
Good Luck!
I have been trying to update my phone but everytime I try the OTA it says installation failed. I ignored it for a few months now bc I didn't want to lose root after updating. How can I install the OTA? I am on MetroPCS (BE88CF)
I tried disabling AdAway thought it may be blocking the servers but that didn't 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"
}
Pulled this from the OnePlus website
"Ok, looks like the download has failed/corrupted. Open the File Manager app > go to settings in the FM app and enable "Show Hidden Files" > then go to the device storage and look for a folder called ".OTA" - delete it and its contents. Then reboot your phone and try again."
Did you ever figure this out? I have the same problem. Not even unrooting fixes it. There is no .OTA folder on my phone either.
doodalydoo said:
Did you ever figure this out? I have the same problem. Not even unrooting fixes it. There is no .OTA folder on my phone either.
Click to expand...
Click to collapse
Flash stock boot.img for your model and firmware. Probably gonna need the original recovery image too if you've got anything besides stock.
Relock bootloader using fastboot.
As long as there's nothing that can be checked back as invalid, you should be able to update your phone proper.
ninjasinabag said:
Flash stock boot.img for your model and firmware. Probably gonna need the original recovery image too if you've got anything besides stock.
Relock bootloader using fastboot.
As long as there's nothing that can be checked back as invalid, you should be able to update your phone proper.
Click to expand...
Click to collapse
I tried reflashing stock recovery and boot images, but it didn't work. Relocking the bootloader shouldn't be necessary, but if it is I'll just go without updating. I don't feel like having to wipe out my phone to unlock the bootloader again every time there is an update.
doodalydoo said:
I tried reflashing stock recovery and boot images, but it didn't work. Relocking the bootloader shouldn't be necessary, but if it is I'll just go without updating. I don't feel like having to wipe out my phone to unlock the bootloader again every time there is an update.
Click to expand...
Click to collapse
Sadly it's a boatload of effort to get the update. Either you go back to 100% stock, or live with it.
I said screw it and just moved everything to my memory card before using the msm reset app
ninjasinabag said:
Sadly it's a boatload of effort to get the update. Either you go back to 100% stock, or live with it.
I said screw it and just moved everything to my memory card before using the msm reset app
Click to expand...
Click to collapse
I managed to get the last update installed by reinstalling 11.0.2 through the Oxygen Updater, then 11.0.3 installed fine. I was going to try to repeat this method with 11.0.3 to get to 11.0.4, but Oxygen Updater no longer allows me to download 11.0.3. I tried to sideload it and do a local update, but the phone won't find it. I can't even install it through fastboot commands because the OTA is incremental and the payload dumper won't work on it.
I was able to update by doing what you said and relocking the bootloader after reflashing stock and boot images. Relocking bricked the phone so I had to use the unbrick tool. Definitely a pain to have to do this every time, Then I ran into problems restoring my TWRP backup that I had to figure out lol. I'll probably just update every two or three updates from now on. Plus all this reflashing opens up more opportunities for RCS features to stop working on Google Messages because they are so finicky. Then my texts act up for 3-10 days until RCS starts working again. Luckily they reconnected right away this time.
Thanks for the help.
Hi all! I hope this is the right spot to post this. I'm looking to install a custom ROM onto my Moto E4 Plus (Owens XT1775), but I'm running into issues.
- Tried updating to a new version of TWRP, now it's saying I need a password to decrypt, and none of the tools I'm finding are helping
- Tried replacing TWRP with an older version, same issue happened
- Tried going back to a stock recovery but can't find any
- I really just want to a custom ROM on this thing >.>
Can someone point me in the right direction on figuring out my TWRP issues, even if it means starting all the way over? I've had TWRP and Magisk on here for more years than I care to count, so I don't even remember the version it was using. If anyone has recommendations on custom ROMs that would work on this device too, that's much appreciated.
miralusion said:
Hi all! I hope this is the right spot to post this. I'm looking to install a custom ROM onto my Moto E4 Plus (Owens XT1775), but I'm running into issues.
- Tried updating to a new version of TWRP, now it's saying I need a password to decrypt, and none of the tools I'm finding are helping
- Tried replacing TWRP with an older version, same issue happened
- Tried going back to a stock recovery but can't find any
- I really just want to a custom ROM on this thing >.>
Can someone point me in the right direction on figuring out my TWRP issues, even if it means starting all the way over? I've had TWRP and Magisk on here for more years than I care to count, so I don't even remember the version it was using. If anyone has recommendations on custom ROMs that would work on this device too, that's much appreciated.
Click to expand...
Click to collapse
Alright, so I found a guide that said factory reset from TWRP would help but now I can't boot into the OS at all, it keeps bringing me back to TWRP. I'm assuming I need a factory image to fix that but no luck finding one yet.
I have a file in my computer named OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. It's 1.3GB . Is that the stock rom that you are looking for?
I am looking for a guide to install custom rom into my Moto e4plus so I can install new versions of apps. Is that what you are doing? If so do you mind give me a few pointers once you are successful?
There are a lot of posts on here but I am confused as to which one to follow. My phone is rooted and is on service with Verizon and I don't want to lose either.
Thank you much!
aarinluk said:
I have a file in my computer named OWENS_RETAIL_7.1.1_NPR26.58-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml. It's 1.3GB . Is that the stock rom that you are looking for?
I am looking for a guide to install custom rom into my Moto e4plus so I can install new versions of apps. Is that what you are doing? If so do you mind give me a few pointers once you are successful?
There are a lot of posts on here but I am confused as to which one to follow. My phone is rooted and is on service with Verizon and I don't want to lose either.
Thank you much!
Click to expand...
Click to collapse
I'd super appreciate the file! I'm not sure if it's exactly what I'm looking for but it wouldn't hurt to try. I'm having a hard time finding support for this specific model of device, but I know there are some unofficial ROMs that are floating around for the owens/1775 model.
https://forum.xda-developers.com/t/rescue-and-smart-assistant-lmsa-motorola-lenovo-only.3951714/ This may have just saved my bacon, at least on the stock ROM part
Alright, so we're back to full stock, except now I cannot get my computer to recognize the device in fastboot... any ideas?
{
"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"
}
Alright, fixed that! Just had to install a newer minimal ADB program. Now to flash that pesky decryption file...
This is your problem. You put adb instead of fastboot *facepalm*