So, I was trying to root a model of Samsung galaxy tab a sm-t380 2017 8" and I came across a boot loop and thought of a possible solution that is following, In TWRP I saw an option wipe/AdvancedWipe /RepairOrChangeFileSystem then finally I saw change file system and it then showed 6 options of formats to format the system to a different format rather than the default and to sum this up I wanted to know if changing one of the options would stop the supersu boot loop of the default device animation. PS: I said this because at the top of the final option it says in red "some roms or kernels may not support some file systems. proceed with caution!"
TheRealYiDa said:
So, I was trying to root a model of Samsung galaxy tab a sm-t380 2017 8" and I came across a boot loop and thought of a possible solution that is following, In TWRP I saw an option wipe/AdvancedWipe /RepairOrChangeFileSystem then finally I saw change file system and it then showed 6 options of formats to format the system to a different format rather than the default and to sum this up I wanted to know if changing one of the options would stop the supersu boot loop of the default device animation. PS: I said this because at the top of the final option it says in red "some roms or kernels may not support some file systems. proceed with caution!"
Click to expand...
Click to collapse
DON'T change the file system! I don't have a T380 but in general, when you get a bootloop on Samsung tablets it is because of kernel mismatch. IOW, the kernel version of TWRP doesn't match kernel version of the ROM you have installed. Also, instead of supersu, try using Magisk.
Related
I'm not allowed to post in the Development forum, so I will ask my question here:
I updated to ICS successfully by changing the update-script in the update.zip.
I removed the lines which delete the recovery or reinstall it; I deleted the whole recovery folder as well.
But now I can't get back into CWM, it just doesn't start, it stops during "booting into recovery kernel" ( it was not overwritten).
So, is the ICS update changing so much in the system that CWM stops working? (through google I found something about different kernels, but didn't understand it)
I think I'll try to install the original recovery, better than nothing.
(this may also be a warning to people who think that they can roll back to honeycomb with CMW - apparently, once the update was succesfull that's it with honycomb)
daniel
I think it might have to do with the updated bootloader that comes with the ICS OTA.
I just had a look at the "blob"-file in the update.zip and was able to unpack it with the BlobTools for the Asus Transformer (https://github.com/AndroidRoot/BlobTools). Inside it was an EBT-file, which, according to my research, should be an image for the bootloader.
Looking through the strings in the blob, it seems to be one indeed: "Bootloader Start at:%d ms".
So I guess the new bootloader loads the recovery system from a different address or partition than the HC bootloader, which is why CWM won't start.
So adding the lines for flashing the OTA recovery-from-boot.p to the updater-script and re-running the update over HC should theoretically solve the issue. Or, if that doesn't work, flash the recovery image manually and flash the blob via nvflash (I'm not sure, though, if that is possible without the keys).
Maybe then someone with enough reverse-engineering skills could determine what has changed in the update and patch CWM accordingly...
Similar Issue..
In CWM, from [ROM][JB] CM10 for Ideapad K1 [Updated 8/29] (I'm running version 2). Whenever I attempt to use any of the features it asks me to install the recovery (which I know I have, and can boot to it) and asks me to choose my device.. Which it then only gives me the ASUS TRANSFORMER as an option.
So, on Version 1 of this build, some time back. I said, what the heck, why not. Let it do its thing,rebooted.. and the system would not ever boot. Just hung at the CM10 boot animation.
Whatever. I used the NVFlash version, got it back up and running. Rebooted in to CWR, and flashed the [ROM]CM10 for Ideapad K1 version 2 CWM version on it. Id really rather not have to wipe my device again to go to version 3, or 4.. and I don't want to get stuck at a boot animation again.
Any thoughts?
It will work again. Just find the file "k1recovery" from the system/bin folder of a rom that has it. Push it in the device, fix permissions and execute it using ADB. The combination Power Btn & VOL+ doesn't work on some devices.
I tried a variety of modifications i9300i4.4 boot animation but without success, who would modify the boot animation
Has anyone else had this problem with the S3 Neo?
Misterlzh said:
I tried a variety of modifications i9300i4.4 boot animation but without success, who would modify the boot animation
Click to expand...
Click to collapse
Hi. I too have had this problem. Previously I've found changing the boot animation on a rooted phone pretty straightforward. I've used data/local - put the zip file in there and it's worked. With the S3 Neo, nothing changes. I've tried other suggested locations but no success so far. Anyone got any ideas?
Yeah the stock samsung roms have a different format so you cant easily change the boot animation.
Just flash this zip and then it will work. http://www.mediafire.com/download/1kl7xuu08fdusfo/CWM_CustomBootanimation_44_Enable.zip
Thanks Laurisss
Laurisss, thanks. Unfortunately it didn't work
I tried flashing the zip using adb sideload and direct from the sdcard. In both cases it gave an error saying that the footer format was wrong. I've been able to get the bootanimation working on other Samsung devices - my old S2 was pretty straightforward. Something has been changed in the S3 Neo that gets in the way of all of the usual workarounds. Any other suggestions?
paulsbirch said:
Laurisss, thanks. Unfortunately it didn't work
I tried flashing the zip using adb sideload and direct from the sdcard. In both cases it gave an error saying that the footer format was wrong. I've been able to get the bootanimation working on other Samsung devices - my old S2 was pretty straightforward. Something has been changed in the S3 Neo that gets in the way of all of the usual workarounds. Any other suggestions?
Click to expand...
Click to collapse
You have to have CWM (ClockWorkMod Recovery) flashed on your device, because stock recovery is checking the zip files, if they are legitimately signed by whitelisted certs (or something like that).
Edit: Just use Odin3 with CWM Recovery package for Samsung Galaxy S3 Neo, kill any Samsung Kies3/Kies app that is running, and you should be good to go, just put the recovery package in "PDA" part, if there is no "RECOVERY" there. It's been a long time since I last opened Odin and I forgot the precise layout it had.
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Lenovo Tab 4 Plus with and without LTE and both 8 and 10 inch versions (TB-X704L/F, TB-8704X/F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Download
TWRP for TB-8704X/F (8 inch plus): AndroidFileHost
TWRP for TB-8704V (8 inch plus Verizon): AndroidFileHost (provided by @3m1k)
TWRP for TB-X704L/F (10.1 inch plus): AndroidFileHost
TWRP for TB-8504X/F (8 inch): AndroidFileHost (touch input may only work after connecting mouse)
TWRP for TB-X304L/F (10.1 inch): AndroidFileHost
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.3-0-<your-filename>.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Backup at least system and boot partitions. Choose "System Image" for the system partition backup. Keep this backup for OTA updates.
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Writable System Partition
Some mods and root apps require write access to the system partition. By default the system partition is read-only to prevent any modification. Please note that if your system partition is modified in any way it needs to be restored to its original state before a system update (OTA) can be applied.
@dywersant has created a Magisk module here to achieve write access
@KreAch3R has updated the Magisk module to the latest version here
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000037) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000037) for the update to succeed.
Credits
@wonderfulme - for testing the 8" version
@Teddy01 - for testing the 10" version
@3m1k - for providing the 8" Verizon version
TeamWin
Source
TWRP Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Device Tree (TB-8704X): https://github.com/Matshias/twrp_android_device_tb_8704x/tree/android-7.1
Device Tree (TB-8704V): https://github.com/3m1k/twrp_android_device_tb_8704v
Device Tree (TB-X704L): https://github.com/Matshias/twrp_android_device_tb_x704l/tree/android-7.1
Device Tree (TB-8504X): https://github.com/Matshias/twrp_android_device_tb_8504x/tree/android-7.1
Device Tree (TB-X304L): https://github.com/Matshias/twrp_android_device_tb_x304l/tree/android-7.1
Changelog
v3:
Update to TWRP 3.2.3-0
v2:
Update to TWRP 3.2.1-0
v1:
Initial Release
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): no longer needed. Final version in first post
matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
I can test the 8 inch tomorrow. Thanks for building this btw.
---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
w0rdie said:
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
Click to expand...
Click to collapse
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
matshias said:
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
Click to expand...
Click to collapse
Just landed there myself. I'll give it a go tomorrow morning and update this post.
Thanks again.
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
boza12 said:
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
Click to expand...
Click to collapse
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
matshias said:
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
Click to expand...
Click to collapse
Yes It does - it happened to me last night also.
EggZenBeanz said:
Yes It does - it happened to me last night also.
Click to expand...
Click to collapse
Can you send me the logs (dmesg output and /tmp/recovery.log) after it happens?
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
EggZenBeanz said:
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
Click to expand...
Click to collapse
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
matshias said:
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
Click to expand...
Click to collapse
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
EggZenBeanz said:
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
Click to expand...
Click to collapse
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
matshias said:
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
Click to expand...
Click to collapse
Thanks!!!! Confirmed TB-X704F
matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
On my Tab4 8 the touch is also not working with this image.
I think the following lines from dmesg.log are showing, that the touch driver ist not loading:
<4>[ 1.323216] [HXTP] Himax common touch panel driver init
<4>[ 1.323221] [HXTP][ERROR] himax_common_init failed, compare_tp_id = 1
w0rdie said:
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
Click to expand...
Click to collapse
Do you have the TB-8504X or TB-8504F? Very strange that the touch driver won't load. if you have the F variant then maybe it has a slightly different hardware in which case I'll have to compile separate TWRP for this variant. Can you extract me your stock boot or recovery image and send it to me? I'd then build TWRP with the kernel from your tablet and we'll see what happens
EggZenBeanz said:
Thanks!!!! Confirmed TB-X704F
Click to expand...
Click to collapse
Here is the system image in sparse format for fastboot flashing: MEGA
matshias said:
Here is the system image in sparse format for fastboot flashing: MEGA
Click to expand...
Click to collapse
Amazing, thank you so much. All worked and back to normal. I'll root again with the screen off and provide logs
Sorry if this is off topic, but is there a way to convert the Chinese versions of the Tab 4 / Plus to the Global rom? I'm thinking of getting one from China when I'm there but the lack of Google Play support is a major deal breaker.
What I have:
I have a Samsung J5 (2015) SM-500FN which ran out of storage and basically hung itself up. There is no data I want to recover, but I want to install either a stock ROM or (preferably) something else like Lineage - I just want to get a usable phone again.
My problem:
I have tried to download *many* stock ROM
s from reputable sources like SamMobile (for this specific phone, but trying different release dates and country codes) but every single one of those ZIPs is corrupt, even when downloading from a different computer.
Flashing with ODIN anyway gives a FAIL result and a device that cannot boot, not even into recovery: It gives a green screen with the text: `An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.`
Ironically, the Smart Switch software just says this device is not supported. The older Kies3 software lets me enter the exact model# followed by the serial# - but then it says this device is not supported. So neither Samsung software is usable, but I can still use ODIN.
Even with the phone in this broken state, I can install TWRP again. So it is not completely bricked. I boot into TWRP and copy a LineageOS ZIP file to /sdcard, but when I try to install that, the TRWP console says: `E3004: This package is for device j5nlte,j5nltexx; this device is .` Note how it doesn't appear to recognize that this device is indeed the model j5nlte!
Android.SE says that "E3004" means my TWRP is too old, but I use `twrp-3.1.1-1-j5nlte` which is currently the newest version for this phone.
I would also like to try a factory reset, but that requires the stock recovery which won't boot (see step 2 above).
My question: How do I get out of this catch-22?
It seems that if I could just get around that E3004 then I would be fine. But I have found no ways to trick the installer into ignoring that error.
Flash an updated twrp .IMG file which you can extract from the file here j5nlte (TWRP)
Just flash the img in twrp and reboot to recovery
Then with the updated twrp try flashing the rom again
garylawwd said:
Flash an updated twrp .IMG file which you can extract from the file here
Click to expand...
Click to collapse
THANK YOU! This did the trick. May I ask: what is the origin of that TRWP image? How could I have found that on my own?
torbengb said:
THANK YOU! This did the trick. May I ask: what is the origin of that TRWP image? How could I have found that on my own?
Click to expand...
Click to collapse
No problem at all, glad all is working for you now. Happens all the time with people having the wrong recovery its no big deal but a lesson learned is always make a backup in twrp before going tinckering around with things or keep a copy of a rom, that you know works, on your SD card.
From the bootleggers pie rom thread.
The Dev of that also builds his own twrp for all j5 2015 models.
he's a really great guy to have supporting our j5 community
I can boot into Samsung recovery and can boot into Download mode. I have tried factory resetting the tablet. I have tried reflashing the stock image with Odin 3.09 in Download but everything I try just fails. It comes up with a message in stock Samsung Recovery that says:
#REboot Recovery Cause is [[check_boot_mode]RebootRecoveryWith Key]
#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
dm-verity verification failed. . .
E: Failed to clear BCB message: failed to open /dev/block/bootdevic
e/by-name/misc: No such file or directory
Could someone please help me figure out what I need to do. I am familiar with Odin for the most part. I would be FOREVER GRATEFUL! Thank you! :victory:
TWRP to save the day!
obtain stock rom and after flashing with Odin 3b patched also flash twrp and then and using either an external storage sd card or USB otg cable and a flash drive restore them twrp backup available elsewhere on the site , try use samfirm or whatever and go to android file host and search t380 and sort thru it but everything you need is there
mrstuffandthings said:
TWRP to save the day!
obtain stock rom and after flashing with Odin 3b patched also flash twrp and then and using either an external storage sd card or USB otg cable and a flash drive restore them twrp backup available elsewhere on the site , try use samfirm or whatever and go to android file host and search t380 and sort thru it but everything you need is there
Click to expand...
Click to collapse
mine also has the same problem, another problem is my OEM is locked. So I cannot install twrp.
Hello there, I`ve bought a vietnamese Samsung Galaxy Tab A 8.0 2019.
Can I flash the european Rom on it?
Is there maybe twrp to flash and perhaps Custom Rom's?
I wanna use it as a german model.
I am not an informed authority whatsoever but I did have quite a few close calls with my same device and I repeatedly managed to get it going. That must hurt to hear without a clear step by step specific with links instructions I know but let me not mislead you either. What good is that?! Well I can refer you to some of the resources I had luck with , it’s been a few years since too so I will go look and see if I have anything concrete , off the top of my head I want to say thanks to magisk the bootloader never did get unlocked , and I only ran the boot.img thru the app and then had my tarp ready to flash right after, be persistent I must have mangled and recovered over two dozen times here and there and again ambiguous encouragement empty as it is I can say from my experience that more than a few things that worked ended up being very simple but minor factors such as unchecking the auto reboot and flashing the twrp right after , another saving grace came in the form of a few die hard twrp flushable zips that enabled simple functions while in twrp bc I remember I would get as far as twrp and then loose the bootable os until I had reflashed the correct boot from inside twrp and I recall dmverity can be mitigated with a zip flashed inside twrp , now that sounds great but only just the right twrp would allow for this flashing feature at all so again hit and miss , I’ll go look at some of those files and review before I make any specific suggestions which would drive me nuts but if your lucky I was actually just noticing I still had an old custom rom that I had cooked up with one of those command line rom kitchens, so standby for real info but for now off hand …
Androidfilehost.com was a killer source of roms and where I found the working twrp
Back then samfirm was already depreciated but still worked and it was the fastest around but
Samsung firmware download - find All Official Android & Samsung Updates | updato.com
Are you looking for the official Samsung software to download? At updato.com, you'll find the latest Android device updates. Check on your own!
updato.com
Jonny boy , again knowing I don’t really know I want to say your good to go as I flashed all manner of rom from all over but I do remember something about I think the us version that seemed XAR less appealing I think bc it was a little more locked down but you would do well of course to refer to that list of the country codes for the roms obv, and as far as twrp I found mine on that android file host but on that same site was an identical looking version that once inside couldn’t flash or mount things properly , see what the trick was , was once armed with a twrp flashable zip i would wipe everything and include the dmverity disabled and whatever else , the patched boot.img And so if your careful even if you flash the wrong twrp first you can inside still flash that other one and reboot to it , my custom rom is nothing to get interested in all it were was a trimmed down stock , tho I did manage later to get some neat custom boot animations , I’ll check out my old files and return sooner this time
WARNING : I JUST COPY PASTED THIS FROM A SEARCH FOR sm-t380 on androidfilehose but it seems someone has been busy since i...
god mode?
Search Results for "sm-t380" | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
please lmk how things gel, or not
hope i was not all nonsense