Related
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?
ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?
Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.
I got a few battery saving apps and one or two of them required xposed. now my phone keeps boot-looping. i tried deleting what i could find of the apps in twrp, it did not help. i dont want to remove my root, custom kernel, and all my custom stuff in general.. and i have apps that i cant log out of without losing everything, such as chats, unread messages, etc. so basically i REALLY dont want to factory reset. ive done that probably 5 times over the past few months of having an android phone. what should i do? help
stiarlitserenity said:
I got a few battery saving apps and one or two of them required xposed. now my phone keeps boot-looping. i tried deleting what i could find of the apps in twrp, it did not help. i dont want to remove my root, custom kernel, and all my custom stuff in general.. and i have apps that i cant log out of without losing everything, such as chats, unread messages, etc. so basically i REALLY dont want to factory reset. ive done that probably 5 times over the past few months of having an android phone. what should i do? help
Click to expand...
Click to collapse
Can you mount userdata partition in TWRP? If so back up right away and move the backup data off your phone before continuing.
Do you have a TWRP backup you can restore? Start with system and boot. If you are lucky the bootloop is because of changes you made in system and this will get you booting.
If not, see if you can restore boot and system from factory images.
Worse case, you might need to factory reset again and reinstall yet another time.
Reflash rom, kernel and supersu. You shouldn't lose anything doing that.
sfhub said:
Can you mount userdata partition in TWRP? If so back up right away and move the backup data off your phone before continuing.
Do you have a TWRP backup you can restore? Start with system and boot. If you are lucky the bootloop is because of changes you made in system and this will get you booting.
If not, see if you can restore boot and system from factory images.
Worse case, you might need to factory reset again and reinstall yet another time.
Click to expand...
Click to collapse
im a newbie to all of this.. what will mouting user data partition do, and how do i do it?
backups dont work because i dont have enough free storage. i do have one backup but it was back when i restored my phone to factory settings.
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
stiarlitserenity said:
im a newbie to all of this.. what will mouting user data partition do, and how do i do it?
backups dont work because i dont have enough free storage. i do have one backup but it was back when i restored my phone to factory settings.
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
Click to expand...
Click to collapse
Lesson learned bud. Half of the reason for TWRP and CWM is to have a full recent/current backup. Its always been like this. All roms, tweaks, xposed, write-ups or threads all say "make a backup" A backup is needed when something goes wrong. Notice the word "when" its not a if something goes wrong. Playing with androids involves way to much stuff and things do go wrong. Everytime your gonna do something just make a backup and delete your previous backup. Keep the backup on a sd card and delete the previous one. You put yourself in a situation like street racing on the freeway in a thunderstorm on new years eve. Not being a **** but for years and years now there a thousands of tutorials on this stuff. How to use adb, fastboot, twrp, soft brick, hard brick, de-brick tool. I don't know where the link is but I have a xposed script to flash in recovery that disables xposed and all modules from recovery in case of a bad module. If that can be found still I suggest that using xposed
FYI. The two replies before this told you what to do. If your looking for a easy everything is 100% going to be ok and you won't lose your text messages its probably not going to happen.
stiarlitserenity said:
what will restoring boot and system from factory images do, and how do i do it? will i lose all the customization i have on my phone?
Click to expand...
Click to collapse
If you are on the stock rom, flash the stock boot.img and stock system.img either in TWRP or via fastboot will erase any mods in /system (including Xposed). This will return you to a stock setup. Your apps, sms, and data would be retained.
To do this, download the factory image that matches your rom base. The July OTA is MTC19Z by the way. June is MTC19V, you'll have to remember which one you were on. This can be found on Google's Nexus factory image website. Next, unzip the downloaded file then flash the boot.img and system.img in TWRP (transfer the files to your phone). Alternatively, you could learn to use fastboot. Follow section 10 of this amazing guide by Heisenberg, but flash only boot.img and system.img.
You *should* be able boot up and learn from your mistakes as others have said. If you still have issues, factory reset and charge this loss to the game.
Sent from my Nexus 5X using Tapatalk
Currently I'm using a OnePlus 3 on 6.0.1 (OOS 3.1.1) but I would like to update to Oreo (OOS 5.0). How do I do this when my device is rooted?
I've downloaded the latest OS off the oneplus website. Is it as simple as uninstalling SuperSU and then flashing the latest OS through recovery?
I also have TWRP recovery and Xposed installed.
Would appreciate any help.
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
The full zip of oxygen OS will overwrite the TWRP recovery with the stock one?
I can update with the zip in the recovery and root whenever i want or i have to do this at the same time?
Explorer23 said:
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
It's as easy as that? It's not a problem that I have xposed installed or anything?
What should I wipe before I install the new OS?
Sorry for all the questions, newbie here.
@Edo 91
I'm not sure about overwriting recovery, it's been a long time since I've used OOS (currently on PA, before than on LOS). If I remember correctly the recovery should stay if you DON'T boot into system right after flashing. So, flash the ROM, reboot into recovery first, then boot into system. Can't say if anything changed with Oreo, but that's how I remember it from Nougat and Marshmallow. You can however flash recovery again right after ROM, just to be sure.
You can root later down the road, no need to do everything at once.
@scalliant
Generally yes, it as easy as that. Xposed and root methods modify system partition - and that gets overwritten when you flash new ROM. That's why those modifications have to be flashed again after every update (some custom ROMs are exception, but rest assured the stock one will nuke all mods).
Anyways, we're talking about Android version upgrade here and not just a minor system update, so I'd recommend a clean installation (but you can try dirty first and then do a clean one in case you experience issues).
First of all, make a full nandroid backup (check everything except "system image" in TWRP). Copy all of your media content (pictures, videos, music ... whatever you don't wanna lose) to another device - better safe than sorry. Optionally, backup apps with Titanium or something similar.
To do it clean: wipe /system, /data and /cache. That means losing all apps and settings, but you'll keep stuff that was stored on the phone. After successfully booting into system you can restore app backups or install them and set up everything again.
To do it dirty: wipe just /system and /cache. You'll lose just system settings, but will keep apps and everything else. Less hassle, but higher chance of something going south.
Explorer23 said:
@Edo 91
To do it clean: wipe /system, /data and /cache. That means losing all apps and settings, but you'll keep stuff that was stored on the phone. After successfully booting into system you can restore app backups or install them and set up everything again.
Click to expand...
Click to collapse
I thought you loose everything when you do a clean install. So photos and files are preserved using this method? I assume text messages will be lost?
shobuddy said:
I thought you loose everything when you do a clean install. So photos and files are preserved using this method? I assume text messages will be lost?
Click to expand...
Click to collapse
Media is on a (virtually) separate partition and is preserved unless while internal storage is formated. Still, it's never a bad idea to have a backup.
Yes, text messages are lost if not backed up. There are many apps that do that (and can be set to upload to cloud regularly).
Sent from my OnePlus 3 using Tapatalk
Been running a stock rooted set up for a long time. Looking at flashing a few Custom Roms and trying them out. I want to backup my stock setup so I can go back if need be. Are backups working in TWRP? If so is there a certain version of TWRP that needs to be used? Also, what all needs to be backed up? I'm not familiar with backing up the A/B partition setup. I know on single partition phones you selected data, system, and I think maybe boot or one other thing. Thanks in advance!
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
Don't suppose you figured this out, I'm having a similar issue.... Have just seen TWRP now supports dynamic partitions which I guess might help?
apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition
Click to expand...
Click to collapse
klanbo78 said:
Don't suppose you figured this out, I'm having a similar issue.... Have just seen TWRP now supports dynamic partitions which I guess might help?
Click to expand...
Click to collapse
If you fastboot to TWRP you can install one of the full updates from the site. The update zips ( at least the full versions downloadable from the red magic.gg site will be enough to get your phone's working again.
The zips are official, so they will overwrite your recovery when flashed, but flash just the same without error over TWRP. Make sure you backup your data partition, and do a full wipe before so you can start fresh.
Thanks for that, I don't actually have the Red Magic, I did a forum wide search for the issue. Was hoping the fix would be similar for my device.
My phone doesn't have TWRP yet (Oppo Find X2 pro) ?