My device IS emmc 15, I HAVE learned to root/bootloader unlock. My issue is I am trying to install ubuntu touch, and I have verified that it is unofficially supported, meaning that the OS is not fully complete and the auto installer doesn't work.
Can a developer help me understand what I need to do to make this work? The ubuntu instructions aren't working for me. I am trying to use TWRP to install it and the files I have tell me that it cannot locate the meta-inf file, then fails to flash.
Here is the article I am trying to use. Maybe one of you fine wizards can test this out and tell me what I am doing wrong.
Samsung Galaxy S5 • Ubuntu Touch • Linux Phone
Flash your Samsung Galaxy S5 with the latest version of the Ubuntu Touch operating system, a privacy focused OS developed by hundreds of people.
devices.ubuntu-touch.io
Related
Hello Guy´s
I have a Samsung TAB GT-P7500 10.1 with Android 4.04.. I found on this Internetside a Custom Rom AOSP 7.1.2 für P4 Tab. I put it on the Device but when I want to make the first Installation, I can only Change the Language and the second Window is with activate a SIM CARD. Now for this Device a haven´t a SIM Card. I want to SKIP this Windows but the Device is bending the Installation. I can only switch the language. I can´t make any more settings because the Device be ending the installation. I make a Factory Reset but the result is the same.
The second, I install the MArshmellow 6.0.1 on this Device. The installation was successful but the devise is very slowww, very very slow…
Which one Firmware I can use with any problems with my Device? Which Version of APP´s need this device?? ARM APPS`??
I have installed successful the TWRP 3.1.1 on this device and it working fine.
Many thanks.
Silav said:
Hello Guy´s
I have a Samsung TAB GT-P7500 10.1 with Android 4.04.. I found on this Internetside a Custom Rom AOSP 7.1.2 für P4 Tab. I put it on the Device but when I want to make the first Installation, I can only Change the Language and the second Window is with activate a SIM CARD. Now for this Device a haven´t a SIM Card. I want to SKIP this Windows but the Device is bending the Installation. I can only switch the language. I can´t make any more settings because the Device be ending the installation. I make a Factory Reset but the result is the same.
The second, I install the MArshmellow 6.0.1 on this Device. The installation was successful but the devise is very slowww, very very slow…
Which one Firmware I can use with any problems with my Device? Which Version of APP´s need this device?? ARM APPS`??
I have installed successful the TWRP 3.1.1 on this device and it working fine.
Many thanks.
Click to expand...
Click to collapse
Rather late than never. I followed this guide to install Decatf's AOSP 7.1 rom on my P7500 today. Works pretty nicely but haven't tested it fully. Not sure if the 3G modem is working but I mostly use it with wifi anyway.
So I've been out of the game for many many years but I want to add a newer custom ROM to my SM-T350. I've been reading for days and just keep getting more confused because of old methods mixing with new ways. Saying you have to have bootloader unlocked to install this but in order to unlock bootloader ya need this other thing that needs this. Just seems to go round and round. Do we have an updated list of instructions somewhere on how to do these things for this particular tablet?
Me too.
So, I have used TWRP which was prior installed and flashed a bunch of the rooms you can get now on mostly XDA.
Make sure to make a recovery backup. I used Crdroid two versions 9 and 10. Just remember to go to OPEN GAPPS website and download the version that is right for the ARM (Pica) your android version number. i.e., 5, 6, 8, 9, 10.
Apparently somewhere around or before version 10, I read that the file structure is different than older versions of android started to conflict because of memory and system placement. place meant. However, I can not yet get back to 4.4.4 where I can play HL2.
With TWR installed my tablet seems to take any ROM for the sm-t350 58wifi 2015.
Hi,
For context, I've been custom romming and rooting for probably over 10 years by now so I know quite well how this works but this device is a new challenge.
I've tried numerous methods on the internet and XDA but apart from softbricking (and restoring every time, msm tool), I just can't get it to work.
Had multiple Qualcomm crash dumps and currently stuck in the bootloader unlocked message. I can still reach fastboot.
All I want is the most recent LineageOS (or preferably dotOS but with the last version Bluetooth audio wasn't working. I managed to flash this one successfully until everything started to go wrong) with Magisk and xposed (or lsposed).
Can someone point me to a resource which most probably would work? I both have Linux and Windows VM's (not macOS) so that's not an issue.
Thanks!
Could someone please point me in the direction of a custom ROM that will (or even might) work on Samsung j7 sky pro SM-272VL(GP)
Before anyone suggests, I have already read all of the information out there on rooting, ODIN, TWRP, etc for this phone. It sounds like several have tried, but no one has actually been able to gain root, although there may be hope for that due to security flaw https://www.exploit-db.com/exploits/45379 mentioned in this post #21
SM-S727VL Analysis, Partition Table, and Factory
-- UPDATE #1 (11/05/18) added So I've got myself a Tracfone Variant of the Samsung J7, The "Galaxy J7 Sky Pro" [SM-S727VL] CDMA. As far as I can tell, this variant is sold on both the Tracfone and StraightTalk carriers, and it seems to just run...
forum.xda-developers.com
I have also read all of the only other thread out there on this device on the subject of rooting, or anything really:
SM-S727VL Root and Recovery
I cannot for the life of me get this phone rooted or a recovery installed. Odin always fails and ADB doesn't recognize the device. Does anyone have any info on rooting this device? I really just want to at least be able to update this thing to...
forum.xda-developers.com
However not much was accomplished in these peoples attempts other than a bricked phone or 2, and most of the participants seem to have moved onto other devices.
I however do not have any issue with needing to root as I own the device, and as it is I can boot into a recovery ODIN mode that says that FRP Lock is off, and the screen is showing a "download in progress" background to a console, waiting for me to send the updated firmware/custom ROM/whatever from the USB cable. See attached image.
I run Linux and have for the last 20 years have used too many Distros to count, but can work with most any, but prefer debian based although I have much respect for Gentoo, and their compile everything package management, and have spent considerable time on it as well. l have unlocked and installed custom ROM's of of many types on many phones, and am working with the combined experience of myself, and my friend who has done the same, except even more on more different devices than myself. But neither of us has worked on such an obscure model as this one with so little information posted publicly on the internet for anyone to find as this one. But if there is a way to do it, I'm sure between the two of us, we can and will make it happen.
Can anyone be of any help? I would really like to get something out of the phone for the $100 that it cost me. Things I would like to run would be Kali Nethunter, and/or Andrax or Cyanogenmod/LineageOS or really any other AOSP that is not google f***ed. Basically any custom ROM (whichever, whatever type and version has the best chance of working on this phone, since there are none posted publicly that are specifically made for this device that we can find for this obscure, excessively undocumented model of phone. Just getting TWRP will be a good start, and I'm pretty sure we can handle that. However in the mentioned posts even the the TWRP file that is made for this phone, people are having troubles installing in their experiences, and bricking their phones in the process, so I definitelly would prefer not to have a repeat of what happened there.
Thank you in advanced for any and all information, hints, tips, tricks, etc. I would like to not brick this phone as the only other person who attempted to do anything with this phone unfortunately had done.
Hi,
the other day a friend gave me her old Samsung tab 4 7.0 (SM-T235). It's in its default state, running Android 5.1.1 stock ROM with all the most recent (5 year old) updates. "KNOX" appears to be ok, afaik.
This is my first Samsung device, up to the date I had experience with HTC Desire, Sony Xperia (2x) and OnePlus devices. I unlocked / rooted and installed custom ROMs on all of them.
Done quite a bit of googling and playing around with my "new" Samsung to see where it's different compared to my other devices. But there still are some blank spots, and there doesn't seem to be too much information out there regarding that specific tab 4 device. Before I start messing around I'd love to have some input from experienced Samsung users in regards to custom recoveries and ROMs, and possibly rooting. If there are comprehensive guides etc. out there that I simply didn't find don't hesitate to give me some hints:
First of all it appears to me that this device is going under the codename "degas". Correct? (meanwhile confirmed)
I hooked up the device to my PC, made sure that adb found it alright, then called "adb reboot recovery". That worked nicely, got me into Samsung recovery
Next I again tried to connect through ADB to the device still being in recovery, but that didn't work. To be expected?
Still in recovery I chose the "boot to bootloader" option, but that got me back into system instead.
So from system I again connected to adb then called "adb reboot bootloader". Device booted alright, but again it just rebooted into system.
>> Is there really no way to get into bootloader?
Trying to find out what has to be done in order to flash a custom ROM (rooted or not): from what I get, and unlike my other devices, I do not have to unlock the device / bootloader to begin with. It looks as if it was sufficient to boot into what they call "download mode", then hook up the device to my PC where ODIN is waiting already. Following this thread (and others) it then is sufficient to just flash TWRP from ODIN, boot to recovery and then do what is usually done here (like flash custom ROM, flash Gapps and possibly Magisk etc.). Is there something else / important I should know / observe?
Speaking about TWRP and Custom ROMs: TWRP.me lists that device on their site. So has anyone here flashed latest TWRP (3.6.2_x)? Or should I rather start with an older version like the one listed here, then possibly upgrade from there?
In regards to Custom ROMs I basically just found this LOS 16 thread (which is the same linked in the previous "TWRP" bullet). I assume that's it, or does anyone know about a newer android version (which I didn't find so far)? There seems to be lots of activity around "matisse" and "millet", but apparently those aren't the right devices, right?
Back to recovery: I see that in stock recovery there is an option to "wipe data/factory reset": should I do that before flashing TWRP from ODIN, or is it sufficient to wipe everything once I booted into TWRP?
I'm aware that I'll lose "Knox" as soon as I flash a different ROM / Recovery. As I don't want to use the tab 4 in some critical "BYOD" area I don't care (neither do I care about warranty, that's long gone anyways). But just to be sure: is it true that I'll lose "Knox" access?
In case I would decide to "go back" to stock ROM one day, how would I proceed then? Would ODIN still work so that I can flash latest stock ROM? Would Knox then be restored, or is that a thing of the past once I leave the stock ROM path?
Again: if you think I've done a bad job searching for answers don't hesitate to let me know but please be so kind then to hint the phrases I should look for ("SM-T235" really doesn't bring up that much valuable info)
Thanks and cheers
Update 2022-08-03: meanwhile I realized that the device is connected to my PC through generic drivers. Would it help to install specific Samsung drivers although both ADB and ODIN are acknowledging the device? Or can I just neglect that?
Since no answers came in I dared to just try. Meanwhile I'm running the device on LOS 16 with TWRP 3.5.2_9. Then flashed MindTheGapps (arm/Android 9 flavour)The switch wasn't as easy as I expected for some reason not obvious to me (somehow I couldn't get into TWRP after flashing it through ODIN. Then after the ~25th attempt it suddenly worked). Meanwhile I installed the official Samsung drivers, and maybe that helped, in combination with other adjustments I lost trace of...
I'll answer some of the above questions, for anyone who's interested:
#3: while in recovery (TWRP 3.5.2, as it is now) I still cannot access the device through adb. But I have access from windows' file explorer, so at least I can exchange files while being in recovery. Strange thing, this is the only one of my devices that behaves this way. The other day I'll try again from a Linux machine. maybe that works...
#4/5/6: boot to bootloader still doesn't work no matter what I try - devices always boots back into system
#7: Once I managed to get into TWRP the rest was a breeze
#8: I tried TWRP 3.6.0_9-0 which worked but on every boot into recovery it shows first a red notice that recovery was not enforcing SEAndroid. The notice then turns into blue and a second later TWRP logo shows up. This dowsn't happen with TWRP 3.5.2_9, so I stay there for the time being. Then I felt lucky and installed TWRP 3.6.2_9 image from running TWRP recovery, then rebooted. That again showed the red "not enforcing" message - and got stuck there. Solution was to get back into "Download mode" then re-flash TWRP 3.5.2 through ODIN.
Conclusion TWRP 3.6.2 is not fit to be used on that device (no, I didn't try 3.6.1...)
#9: since there aren't any more security updates released by google for A9 ROMs it would really be great to be able to upgrade to an A10 or even A11 ROM... anyone ever tried to use a "matisse" or "millet" ROM?
#10: I decided to use that - wiping everything that was on the device then doing a factory reset as well before flashing LOS 16. Then after first boot into LOS 16 a strange thing happened: when I made a basic setting (in regards to location services" the device told me that in a previous version I had decided to NOT allow google to use those services: after all that wiping and factory resetting: how could the device know that? By that time I had not yet logged myself into Google. Very mysterious!
#11/12: I guess I know the answer: I'm out of "Knox" now once and forever. And apparently ODIN is still working and recognizing the device.
Cheers!