Hello. This is my first ever post on XDA, so please excuse any mistakes. Recently, I have been wanting to install TWRP on my Samsung Galaxy Tab S7 (Model Codename: SM-T870), however, I haven't found any .img files available, either official or unofficial. I have been able to root it using Magisk and Odin, however. My tablet is currently running Android 11 with a build number of RP1A.200720.012.T870XXU2BUC6. From what I've read online, the "2" in the "T870XXU2BUC6" section of the build number means that the Bootloader is on Version 2, meaning that I can't downgrade to software versions with a 1 in the software name (i.e. with a Bootloader version of 1). This includes Android 10, and some older versions of Android 11, even if I use the latest version of Odin and if I'm rooted. I know how to install different distros and versions of Linux for creating TWRP from scratch if need be. If someone would be willing to either guide me through the process of creating TWRP for this device, or include a link to an already existing version of TWRP for this device (remember, Android 11, Build Number: "RP1A.200720.012.T870XXU2BUC"), I would greatly appreciate it. All I ask is that the guide(s)/tutorial(s) be in layman's terms, and be step-by-step. I am not very familiar with Linux Commands, so I would appreciate some grace when replying to this post, as I may not be able to understand some terms. Thanks!
Siegemus said:
Hello. This is my first ever post on XDA, so please excuse any mistakes. Recently, I have been wanting to install TWRP on my Samsung Galaxy Tab S7 (Model Codename: SM-T870), however, I haven't found any .img files available, either official or unofficial. I have been able to root it using Magisk and Odin, however. My tablet is currently running Android 11 with a build number of RP1A.200720.012.T870XXU2BUC6. From what I've read online, the "2" in the "T870XXU2BUC6" section of the build number means that the Bootloader is on Version 2, meaning that I can't downgrade to software versions with a 1 in the software name (i.e. with a Bootloader version of 1). This includes Android 10, and some older versions of Android 11, even if I use the latest version of Odin and if I'm rooted. I know how to install different distros and versions of Linux for creating TWRP from scratch if need be. If someone would be willing to either guide me through the process of creating TWRP for this device, or include a link to an already existing version of TWRP for this device (remember, Android 11, Build Number: "RP1A.200720.012.T870XXU2BUC"), I would greatly appreciate it. All I ask is that the guide(s)/tutorial(s) be in layman's terms, and be step-by-step. I am not very familiar with Linux Commands, so I would appreciate some grace when replying to this post, as I may not be able to understand some terms. Thanks!
Click to expand...
Click to collapse
Any luck? I've yet to find any TWRP for the SM-T870
No, not yet. I've been looking as well. I've found a tool by Hovatek that can supposedly make one, and it does flash via ODIN successfully, but I can't figure out how to remove dm-verity on my SM-T870, since mine is a USER build.
I have posted a test build for the T870 here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
Please let me know if it works for you.
I tried it on my rooted stock ROM, and on ODIN, it got stuck on "file analysis". If there's a way for me to customize the stock ROM to disable vbmeta and dm-verity, please let me know, so I can hopefully try that, and then flash it again.
Siegemus said:
I tried it on my rooted stock ROM, and on ODIN, it got stuck on "file analysis". If there's a way for me to customize the stock ROM to disable vbmeta and dm-verity, please let me know, so I can hopefully try that, and then flash it again.
Click to expand...
Click to collapse
If you take a look here:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S7/S7+ Series (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
There is a vbmeta_disabled.tar that worked for me on my T870. Also, in response to your May post about a guide to building TWRP for the device, I wrote one while I was doing my build. It is posted as a response to my TWRP thread here:
[UNOFFICIAL][EXPERIMENT] TWRP for Galaxy Tab S7 Wifi
This is my first thread of this kind, so bear with me if I'm not formatting it quite right. I've run a test build of TWRP 3 for the Galaxy Tab S7 Wifi (T870) against a customized version of the kernel that shipped with the T870OXM2BUC6 firmware...
forum.xda-developers.com
I tried to make it as step-by-step as possible, but I don't know if I'd say that it's all in layman's terms. I basically only know Linux/Unix (I have not done any development on Windows for 10+ years), so it's hard for me to know what could be/needs to be simplified.
Please feel free to ask me any questions you might have and I'll be glad to help out.
OK. Thank you for linking that. I'll try my best. Wish me luck!
@bxlentpartyon Hi. I'm currently following the guide you linked earlier, and so far only a couple things haven't been working. 1) The "git checkout master" command returns "Already on 'master'". 2) The "git merge stock-11" command returns "merge: stock-11 - not something we can merge". 3) The "./run_menuconfig" command returns "bash: ./run_menuconfig: No such file or directory". I'm currently stuck on this, and so far everything else has been working perfectly. Please help!
Siegemus said:
@bxlentpartyon Hi. I'm currently following the guide you linked earlier, and so far only a couple things haven't been working. 1) The "git checkout master" command returns "Already on 'master'". 2) The "git merge stock-11" command returns "merge: stock-11 - not something we can merge". 3) The "./run_menuconfig" command returns "bash: ./run_menuconfig: No such file or directory". I'm currently stuck on this, and so far everything else has been working perfectly. Please help!
Click to expand...
Click to collapse
The issue here is partially that my write-up details everything that I did to run the build, but you won't need to do some of that, since I already pushed my kernel source tree (with the git merge bit of things already done) up to github.
What you can do is replace the:
Code:
git clone https://github.com/ianmacd/gts7xl
Step with:
Code:
git clone https://github.com/bxlentpartyon/gts7lwifi
And then skip down to the Build the Kernel step.
Honestly, though, the more I'm looking at it, I'm realizing that I should probably create a stripped down version of this whole write-up where I explain _just_ how to reproduce my TWRP build, and skip over the stuff about building the kernel and hacking up the device tree. That won't take me long to do, but it might be a day or two before I get to it. I unfortunately have to spend my week hacking on kernels for profit in order to pay for the things that I need to hack on them for fun lol.
Thank you so much!
I'm on the "building the kernel" step, and when I run "./build_t870", I get this message: "Makefile:128: *** main directory cannot contain spaces nor colons. Stop.", along with a large section of text before that. Is this an error message? what should I do?
Siegemus said:
"Makefile:128: *** main directory cannot contain spaces nor colons. Stop."
Click to expand...
Click to collapse
If you run pwd in your build directory, are there any spaces in that full path? My guess would be that's your issue.
I renamed my main foldr from "Making TWRP" to "Making_TWRP", and that did the trick. However, when I ran "./build_t870", I came across this error:
"YACC scripts/kconfig/zconf.tab.c
/bin/sh: 1: bison: not found
make[2]: *** [scripts/Makefile.lib:207: scripts/kconfig/zconf.tab.c] Error 127
make[2]: *** Waiting for unfinished jobs....
LEX scripts/kconfig/zconf.lex.c
make[1]: *** [Makefile:545: syncconfig] Error 2
make: *** [Makefile:654: include/config/auto.conf.cmd] Error 2" How do I solve this? Sorry for bothering you with all these replies, btw.
Siegemus said:
when I ran "./build_t870", I came across this error:
"YACC scripts/kconfig/zconf.tab.c
/bin/sh: 1: bison: not found
make[2]: *** [scripts/Makefile.lib:207: scripts/kconfig/zconf.tab.c] Error 127
make[2]: *** Waiting for unfinished jobs....
LEX scripts/kconfig/zconf.lex.c
make[1]: *** [Makefile:545: syncconfig] Error 2
make: *** [Makefile:654: include/config/auto.conf.cmd] Error 2" How do I solve this? Sorry for bothering you with all these replies, btw.
Click to expand...
Click to collapse
No worries. That's just because you're missing the bison package. What linux distro are you using? Most have some kind of "build essentials" package set you can install that would probably include everything you need to build a kernel. In any case, to fix that, you just need to install bison with zypper/dnf/yum/apt or whatever package manager your distro uses. In general if you see a <something>: not found error, it just means you're missing a program.
OK. Thank you! I'm currently using Ubuntu 20.04.
Hi again. For some reason, I'm now getting THIS error message after installing the bison and Ubuntu 20.04 LTS build-essential packages, like you said:
"make[2]: *** [scripts/kconfig/Makefile:69: syncconfig] Error 1
make[1]: *** [Makefile:545: syncconfig] Error 2
make: *** [Makefile:654: include/config/auto.conf.cmd] Error 2"
Ah, that's probably because of more differences between what I did and what you'll have to do with my final tree. Try:
Code:
cp arch/arm64/configs/vendor/gts7lwifi_eur_open_klugman_defconfig ./.config
In your kernel tree. I think the problem is just the missing config. I'm probably gonna have to bail for the night after this. Our air is all smoky from the Canadian wildfires and I'm real dizzy from breathing it.
OK. If you want, I can talk tommorow if anything happens. See you!
bxlentpartyon said:
Honestly, though, the more I'm looking at it, I'm realizing that I should probably create a stripped down version of this whole write-up where I explain _just_ how to reproduce my TWRP build, and skip over the stuff about building the kernel and hacking up the device tree. That won't take me long to do, but it might be a day or two before I get to it. I unfortunately have to spend my week hacking on kernels for profit in order to pay for the things that I need to hack on them for fun lol.
Click to expand...
Click to collapse
Hello. It's me again. I hope you are doing well. In hopes to prevent future error messages, and subsequent troubleshoots, would you be willing to let me know if and/or when you have created the stripped-down version of this guide on how to reproduce your TWRP build?
Yeah, I'll get that written up this weekend and let you know when it's up. I meant to do it yesterday, but I've been busy with work.
Related
As Modaco's boot image "Superboot (for Nexus One)" got no more updates after Android build version GRI40 and we're on GRK39F for some time now; and even though the Superboot GRI40 version gave you root as desired (https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/), that Superboot version also caused some problems with wifi connection and had an outdated su binary, as well as an outdated Superuser.apk.
To cut a long story short, i did it on my own: Bexboot. A boot image - especially for Android GRK39F on passion devices. I compiled it (based on a guide by Modaco himself) from the stock GRK39F source of my own Nexus One. Also it includes the lates Superuser.apk (v3.0.5) and the latest su binary (v3.0).
Here you go: https://bexton.net/2011/10/12/bexboot-root-nexus-one-passion-grk39f/
Any feedback highly appreciated.
[UPDATE#1 08.11.2011]:
Please don't use v1 (link above) any longer. Instead use the Bexboot v2.0 (link below). It was rebuilt from a completely clean stock rom, what solves the compatibilty issues, some reported for v1. (Also it includes the latest Superuser.apk (3.0.6), as well as the latest su binary (3.0.3).)
https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
[UPDATE#2 11.12.2011]:
As i forgot to pay the invoice for the server where my blog is running on, it is offline since yesterday. :/ Anyway, i uploaded a copy of the zip archive containing all files you need to root your device to http://www.nahklick.de/user/stephan/bexboot.v2.GRK39F_OTA.zip. To get the instructions, follow this link http://www.google.com/search?q="bexboot"+version+2 and use the Google cache to view the original site. Thx
[UPDATE#3 20.02.2012]:
Files and instructions mirrored at request: http://code.google.com/p/bexboot/
i've posted this on my blog aswell. Nice work
http://patrick.oberdorf.net/2011/10/12/nexus-one-root-rechte-mit-stock-rom/
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
zc2 said:
I've tried that, it does not work.
The fastboot utility says:
downloading 'boot.img'... OKAY
booting... OKAY
Then the phone reboots still not rooted.
Click to expand...
Click to collapse
Hi zc2,
sorry for the long response time, i was on a business trip and didn't had the time to check in. I received a bunch of similar issue reports so i did a factory reset and rebuilt the bootloader from a completely clean stock rom.
First comments confirm that it now also works for persons, that had the same issue like you with v1. So if you're still interested in it, check out the updated release version: https://bexton.net/2011/11/07/bexboot-for-passion-version-2-root-for-nexus-one-with-android-grk39f/
Hi Bexton, thank you for the response. I actually was able to root my phone using the instructions from the following post:
http://forum.xda-developers.com/showpost.php?p=18527514&postcount=1853
V2 Failed for me
Bexton said:
...use the Bexboot v2.0 (link below)....
Click to expand...
Click to collapse
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Thanks for such a fast reply. I bought the phone in Bangkok. It was a "grey market" item from the Hong Kong market. I am not sure whether my Thai carrier even bothers with such things.
I looked at the link but unfortunately for me, I have only the most primitive understanding of how to deal with the bootloader, etc. So I can't even grasp what aspects of that thread apply to me. I really need step-by-step instructions. So unless I can find someone with more mastery, I guess I will only dream of Cyanogen Mod on my phone.
goattee said:
Hi there. Thanks for your efforts. I have build GRK39F and ran your version 2 on Windows 7 (64 bit).
During step 6 of your procedure, the write proceudre failed with this error:
FAILED (remote: signature verify fail)
Any ideas? Diagnostic questions for me?
Click to expand...
Click to collapse
Bexton said:
Have you seen this comment / my answer: https://bexton.net/2011/11/07/bexbo...or-nexus-one-with-android-grk39f/#comment-179 ?
It is much likely due to an issue with your hboot version. Your provider probably pushed a locked SPL in an update that renders fastboot unusable. Maybe the link in my comment can help!? Let me know..
Greetz
Click to expand...
Click to collapse
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
efrant said:
You will get that error if you are trying to use fastboot commands without first having unlocked your bootloader.
That error has nothing to do with the HBOOT version on Nexus One's. You cannot "push" a locked SPL to an N1 if you've already unlocked your bootloader. The bootloader unlock flag is set in the radio NV memory, so once you have unlocked the bootloader, you cannot relock it (unless you have S-OFF), even if you reflash another stock hboot.
Click to expand...
Click to collapse
I realize you're trying to clarify. But I don't understand any of the terminology. The only thing I am capable of is following a prescribed procedure. I thought this procedure was going to unlock and root the phone. I guess I was wrong.
I don't have the diagnostic skills to change direction if things don't go in a predictable fashion-- I've only used stock devices up until now and this was my first attempt. I guess the best I can hope for is to make contact with someone more experienced when I am next in the US and have that person assist me. It makes it more difficult because most of what I am finding online is either old (pre-Gingerbread) or it assumes the user has hacked their Nexus One in the past and just needs to bring it up to date.
My goal is to get past the memory problems I am having by installing a custom ROM with a minimal set of apps in phone memory-- and more customizability.
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
davelis828 said:
nice man! It worked on the first go! Top job!
I have one question though! Is it safe to flash Clockword Mod recovery and then flash custom ROMs, or will it end in not finding the recovery image as is the case with other efforts to root 2.3.6?
Thanks!
Click to expand...
Click to collapse
No prob. You can use: https://bexton.net/android/n1/recoveries/recovery-clockwork-5.0.2.0-passion.img
If needed, here's the full stock GRK39F: https://bexton.net/android/n1/sys/grk39f/ota.zip and here the update: https://bexton.net/android/n1/sys/grk39f/d323ca384aaa.signed-passion-GRK39F-from-GRJ22.d323ca38.zip
o thanx ma! i appreciate your feedback, you did it on both sites aswell
Respect!
Mirror created at request: http://code.google.com/p/bexboot/
I gave superoneclick a go before trying this method. It worked flawlessly.
Sent from my Nexus One using Vodka
Source code availability?
Hi Bexton,
first of all, thanks for your work!
Next, I'd like to replace the Superuser app by Koush' one (https://github.com/koush/Superuser/).
Would it be possible to get the source code of bexboot?
None is available at http://code.google.com/p/bexboot/source/checkout...
Regards,
Patrick.
Development on the phone I have has gotten as far as rooting stock (SCH-I110, Samsung Illusion). As I've toyed around with my Nook, I like the idea of cutting edge software still running on older hardware. Yes, yes, I realize that this is a "cheap phone" and not "in demand" and "why don't you just go and get a S2 or S3", but isn't the whole idea of open source the ability for people to learn? I've loved reaping the benefits of others' hard work, but it's time to get my own hands dirty...
Basically it comes down to this: I need to be pointed in the right place to learn how to build recovery for my device (ie CWM).
It's currently rooted, running stock and busybox, but that's as far as I have gotten. The source code HAS been released already, so it's out there. I've tried to read up about Odin in order to figure out how to pull a recovery image and start building, but just about every tutorial I've come across teaches people how to cook their own ROMs after CWM or TWRP is already installed. I'm not quite there yet.
So if anyone has a good place that contains information on building recovery, thank you for your help in advance. I just need a little direction.
Ok, so I pulled a boot.img off the phone as well as a system.tar. I used the boot.img on builder.cyanogenmod.com and have the following output files:
android_device_unknown_unknown.zip
inputrecovery.img
manifest.xml
recovery.img
The recovery image can be found here: http://builder.clockworkmod.com/redirect/5dbb87a058d1bb5fcd0bcbeca347c45b.img
I did see on the console output that it was building for CM10.1. Is this going to be an issue?
Thanks for helping an Android Noobie.
Would this be any help: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
XyanumX said:
Would this be any help: http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
Yeah, that was one source I was reading. I saw his note about initramfs, though. I believe the Illusion uses it as opposed to the standard boot image format, so his guide doesn't work. Thanks for suggesting it, though!
Hello, i wannt to Dev the Samsung Galaxy XCover by XDA so i start with a Singl Thread,
How to Root GT-S5690?
Flash this File in recovery!
http://forum.xda-developers.com/attachment.php?attachmentid=2252551&stc=1&d=1378997325
How to get CWM Recovery for GT-S5690?
Flash this File throut ODIN in PDA Section and its working!
http://forum.xda-developers.com/attachment.php?attachmentid=2252549&stc=1&d=1378997296
Some Custom Roms and CWM coming soooooon,....im working at that! :laugh::highfive::laugh::highfive::laugh:
MFG Marion808
it´s working! how did you build that? is there a possibility of ics or jb?
Thanks
marion808 said:
Hello, i wannt to Dev the Samsung Galaxy XCover by XDA so i start with a Singl Thread,
How to Root GT-S5690?
Flash this File in recovery!
http://forum.xda-developers.com/attachment.php?attachmentid=2252551&stc=1&d=1378997325
How to get CWM Recovery for GT-S5690?
Flash this File throut ODIN in PDA Section and its working!
http://forum.xda-developers.com/attachment.php?attachmentid=2252549&stc=1&d=1378997296
Some Custom Roms and CWM coming soooooon,....im working at that! :laugh::highfive::laugh::highfive::laugh:
MFG Marion808
Click to expand...
Click to collapse
Hi,
Your rooting method doesn't seem to work on my phone. I get no error during flash of the zip file but when I reboot, the phone isn't rooted.
FYI I'm using a fresh install of the S5690XXLL1_S5690LUXLL1 Rom.
Am I missing something here ?
Using another method found on a French forum, I can get root to work.
ClockworkMod Recovery installation worked flawlessly and that's great news :good:
Your work is much appreciated and it would be nice of you if you could give us a heads-up on what you're up to.
Thanks a bunch anyway.
Thanks
Thanks. Confirmed this is a working root and CWM recovery method.
Looking forward for custom roms, preferable CM based.
I got my phone rooted but no cvm.. they all gives me error msg..
how's this project doing? I would love to see custom roms for this device
My try with ICS for xcover:
https://github.com/manakeri/android_device_samsung_xcover
manakeri said:
My try with ICS for xcover:
//github.com/manakeri/android_device_samsung_xcover
Click to expand...
Click to collapse
hello to every one!
so how's the work on ICs going for this old phone?
I hope you still active!
maybe i can beta test your ROM?
keep it up!
gt-s5690 cwm test result
root zip is not working, what worked is
http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
SuperSU from chainfire.
Backup is not working with default settings , you must choose 'tar' format .
Restore is halt on /system restore.
manakeri said:
My try with ICS for xcover:
https://github.com/manakeri/android_device_samsung_xcover
Click to expand...
Click to collapse
Can I BETA test your rom
There isn't that much to test yet, struggling to get the RIL working.
Haven't found any info about marvell's RIL.
And the development has been on a break for couple months now, because I'm so busy with "real life".
Sent from my GT-S5690 using Tapatalk 2
good phone, low memory
Naturely real life is more important.
I have been checking your post about this regularly in the hope of unbloating my xcover because of the little memory the phone has.
I wish i could help. I know computers and some php and stuff, but phones, not a clue.
So we'll wait patiently for you to make our day :victory:
How to build?
manakeri said:
And the development has been on a break for couple months now, because I'm so busy with "real life".
Click to expand...
Click to collapse
Hi manakeri,
thanks for your efforts!
I would like to help doing some low-level (RIL, camerca, GPS etc.) stuff, but I don't really know how to start. There is no build/envsetup.sh, which I could source into my shell. I am used to do Linux development on and for Debian and similar Linux distributions, so working with the Android framework is quite new to me. Could you point me to some howto or give some hints?
Regards,
Benedikt
Are you still working on it?
I would like to participate. My brother has a XCover, but he needs it for daily use, so i am not really able to flash anything right now.
Could you point out how you start everything, and which sources you use?
1+
bwildenhain said:
Hi manakeri,
thanks for your efforts!
I would like to help doing some low-level (RIL, camerca, GPS etc.) stuff, but I don't really know how to start. There is no build/envsetup.sh, which I could source into my shell. I am used to do Linux development on and for Debian and similar Linux distributions, so working with the Android framework is quite new to me. Could you point me to some howto or give some hints?
Regards,
Benedikt
Click to expand...
Click to collapse
dehein said:
Are you still working on it?
I would like to participate. My brother has a XCover, but he needs it for daily use, so i am not really able to flash anything right now.
Could you point out how you start everything, and which sources you use?
Click to expand...
Click to collapse
First you'll need the tools:
http://forum.xda-developers.com/showthread.php?t=2464683
And then something like that:
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync
git clone git://github.com/manakeri/android_device_samsung_xcover.git device/samsung/xcover
cd device/samsung/xcover/ && ./extract-files.sh && cd ../../..
cp device/samsung/xcover/armv7-a.mk build/core/combo/arch/arm/
cp device/samsung/xcover/overlay/bootable/recovery/ui.c bootable/recovery/ui.c
cp device/samsung/xcover/overlay/bootable/recovery/ui.c bootable/recovery/ui.c
cp device/samsung/xcover/overlay/development/build/sdk.atree development/build/sdk.atree
rm -rf development/samples
. build/envsetup.h
cd vendor/cm && ./get-prebuilts && cd ../..
brunch cm_xcover-eng
Could be I forgot something, but if you get problems, ask.
I'll try to answer in at least couple of days.
compiling cm9 for s5690
manakeri said:
1+
Could be I forgot something, but if you get problems, ask.
I'll try to answer in at least couple of days.
Click to expand...
Click to collapse
Hi manakeri,
thanks for you instructions
Now I got some zip file:
out/target/product/xcover/cm-9-20140225-UNOFFICIAL-xcover.zip, 134M
I installed CWM, told it to install that file, cleared dalvik cache and even did a factory reset, but always got nothing more than a black screen (with backlight on) when trying to boot and couldn't use logcat as some executable within /system/bin... was missing.
If I had a development board I would simply put my computer onto the serial port and probably see what's going on, but I would like to avoid opening the phones case as I don't believe it would stay waterproof in that case. So how could I get some useful debugging info by using software?
Regards,
Benedikt
If I remember right, you need to format both data and system partition using the CWM.
Sent from my GT-S5690 using Tapatalk 2
bwildenhain said:
Hi manakeri,
thanks for you instructions
Now I got some zip file:
out/target/product/xcover/cm-9-20140225-UNOFFICIAL-xcover.zip, 134M
I installed CWM, told it to install that file, cleared dalvik cache and even did a factory reset, but always got nothing more than a black screen (with backlight on) when trying to boot and couldn't use logcat as some executable within /system/bin... was missing.
If I had a development board I would simply put my computer onto the serial port and probably see what's going on, but I would like to avoid opening the phones case as I don't believe it would stay waterproof in that case. So how could I get some useful debugging info by using software?
Regards,
Benedikt
Click to expand...
Click to collapse
Hello bwildenhain,
Please share with us your xperience, regarding the CM9 ROM built by you.
Thank you.
Have a nice day !
PS Sorry for my English
Hello cbacsro,
cbacsro said:
Please share with us your xperience, regarding the CM9 ROM built by you.
Click to expand...
Click to collapse
unfortunately I wasn't able to get it running yet. I tried to install both cm-9-20140225-UNOFFICIAL-xcover.zip and cm_xcover-ota-eng.$USER.zip, both after doing a factory reset, but could not boot CM.
@manakeri
I installed the new CWM by using device/samsung/xcover/scripts/recovery.sh (and manually executing the last uncommented lines), pushed the cm-zip file to the sdcard and then booted to CWM and there did a factory reset and applied one of the cm-zipfiles. Is there anything I forgot?
Regards,
Benedikt
Are those uart pins?
Hello,
I hope not to be disturbing by bumping such an old thread - also hope this is the right thread since it does not seem that the s5690 has its own subforum. What for an insignificant little device. Anyways we've been active and I am currently trying to find the UART pins of the S5690. I have taken a scan of the circuit board and cropped it a bit to show which pins I think might be UART. However, I'm quite in a bind right now: My BusPirate is not here yet. Just had to order one, and now it's going once around the world. Interestingly enough, it seems the mainboard can be run without having the other modules (like touch or camera) connected.
If anybody has experiance with UART (and has a xcover of which one does not fear to void the warranty or brick it or whatever), it would be nice if it got verified.
These four pins seem to be perfect canidates however: Next to processor, four in a group, and one seems to be GND.
Link to photo file (add together yourself, I'm not gonna spam to get rid of that damn 10 post cap. I'd also advise to visit the image hoster with an adblocker):
i7. imgchili .net/47012/47012110_s5690_uart_info.png
(I created that Image by scanning the circuit board with a common flatbed scanner in high resolution, just if you're wondering - makes it way easier to find stuff. Then found those pins, tested them for GND, cropped the original image and included the info you see in it with GIMP).
ppps: I assume it would be too much to ask somebody to write a pxa95x framebuffer driver for the last linux kernel that supported pxa95x devices...
Edit: Oh, the thread is still active. I should *really* get some sleep.
Edit2: @bwildenhain
This is taken from an Email conversation I had with manakeri:
otezun said:
Hey, just wanted to inform you. I just reflashed the phone to 2.3.6. Then rooted it with KERUK, from k0k0s download stuff. Anyways, after I rooted the phone, I installed CWM as you said, with your recovery image. I made factory reset, wiped cache, wiped dalvik cache, formatted /system and /data. Then installed my compiled Cyanogenmod 9.
Click to expand...
Click to collapse
Hehe, documentation is everything...the fat text are the steps I think where absolutely crucial to get cyanogenmod to work. Not sure though. Also @ getting infos from phone without opening it - I think that is possible if you have the right resistance cable. Like USB Jig cable with other resistor, put it onto power and it boots into UART mode, usually giving some kinda shell if I understand it correctly. However, I think you also need special hardware for that too.
However, do not take usual infos in "Fun with resistors", it does not seem to work with the s5690. Or do and tell us how it worked out. Depends on how far you want to go.
Edit 3:
I allowed myself to add some wiki pages to the github wiki.
The wiki now should contain most relevant information on getting started. Also got a bit of structure into it. However, I cannot guarantee that all of the information is correct. Be wise and use your brain.
Check it out at: https ://github. com/manakeri/android_device_samsung_xcover/wiki
Installing CM
Yesterday I installed CWM and rooted my Xcover. Last night I compiled the Xcover branch of CM9 made by manakeri using Builduntu made by sylentprofet.
I just managed to successfully install CyanogenMod by installing cm_xcover-ota-eng.android.zip (aka cm_xcover-ota-eng.$USER.zip). Before installing I performed a factory reset, wiped cache, formatted /system and formatted /data.
It boots fine, and I will experiment with the coming days! Hopefully development will restart soon!
Hello,
This is my first post here. I hope this is the right forum - new users are not allowed to post everywhere so I didn't have much choice.
I have LK bootloader source code which I need to build and flash to a Nexus 5 device.
* I got the source code from the Code Aurora website
* I made a guess which branch is the stable branch I need, because I found no mention of it anywhere (I took "kk_2.7-stable", where kk means kitkat)
* On a Debian 7 stable machine, I installed a GCC cross compiler from Deb packages built using Emdebian tools
* I made a guess which target to compile, because the exact chip name didn't have its own: I use msm8960
* I created some symlinks to the cross-building tools because the makefile and the debian cross-building tool names are different
* I ran 'make msm8960' and the build was successful (I also tried earlier with NDK prebuilt GCC but it failed)
* I got a bunch of files with no idea what to do with them
* I attached the device to the computer and re-flashed the stock bootloader to make sure it works
* I checked the fastboot screen: Bootloader unlocked, secure boot is on
* I tried flashing the 'lk' binary file I got from the build process, but fastboot says:
sending 'bootloader' (1702 KB)...
OKAY [ 0.239s]
writing 'bootloader'...
FAILED (remote: invalid bootloader image
)
The size of the file is much smaller than the size of the stock bootloader, but I don't know if it matters or what exactly I need to flash. I did a lot of web search, including here on XDA, but found no evidence of anyone struggling with flashing the bootloader.
What am I missing? How do I flash the bootloader after I build it?
qwertius said:
Hello,
This is my first post here. I hope this is the right forum - new users are not allowed to post everywhere so I didn't have much choice.
I have LK bootloader source code which I need to build and flash to a Nexus 5 device.
* I got the source code from the Code Aurora website
* I made a guess which branch is the stable branch I need, because I found no mention of it anywhere (I took "kk_2.7-stable", where kk means kitkat)
* On a Debian 7 stable machine, I installed a GCC cross compiler from Deb packages built using Emdebian tools
* I made a guess which target to compile, because the exact chip name didn't have its own: I use msm8960
* I created some symlinks to the cross-building tools because the makefile and the debian cross-building tool names are different
* I ran 'make msm8960' and the build was successful (I also tried earlier with NDK prebuilt GCC but it failed)
* I got a bunch of files with no idea what to do with them
* I attached the device to the computer and re-flashed the stock bootloader to make sure it works
* I checked the fastboot screen: Bootloader unlocked, secure boot is on
* I tried flashing the 'lk' binary file I got from the build process, but fastboot says:
sending 'bootloader' (1702 KB)...
OKAY [ 0.239s]
writing 'bootloader'...
FAILED (remote: invalid bootloader image
)
The size of the file is much smaller than the size of the stock bootloader, but I don't know if it matters or what exactly I need to flash. I did a lot of web search, including here on XDA, but found no evidence of anyone struggling with flashing the bootloader.
What am I missing? How do I flash the bootloader after I build it?
Click to expand...
Click to collapse
https://www.codeaurora.org/blogs/little-kernel-based-android-bootloader
I don't see any evidence of support for the Nexus 5 here. Playing with your bootloader like that is potentially very dangerous and could easily result in bricking your device, possibly beyond normal repair. What do you hope to accomplish with this? It seems like it would only be useful for older devices. I don't believe our devices have any bootloader weaknesses that really need to be addressed.
What about flashing the well-known bootloader for hammerhead??? HHZ11k
Primokorn said:
What about flashing the well-known bootloader for hammerhead??? HHZ11k
Click to expand...
Click to collapse
Isn't that just the newest stock one?
Off-Topic: I rock the Reborn theme too often.
es0tericcha0s said:
Isn't that just the newest stock one?
Click to expand...
Click to collapse
Yes it is, so I don't understand why someone would like to flash something else.
es0tericcha0s said:
Off-Topic: I rock the Reborn theme too often.
Click to expand...
Click to collapse
LoL Thought so. Seems like he knows just enough to get himself into trouble.
es0tericcha0s said:
LoL Thought so. Seems like he knows just enough to get himself into trouble.
Click to expand...
Click to collapse
LMAO
****************
FYI here is a link to download the flashable zip of the above version: http://forum.xda-developers.com/showpost.php?p=51593422&postcount=5
I'm trying to flash a modified bootloader, so I needed something I can edit on source code level, compile and flash. But it seems people use the freedom given by the MIT license to take away other people's freedoms: The source code of the Nexus 5 bootloader (although probably LK based, judging by the output of `strings`) is not available online.
I guess I'll need an older device which does have a bootloader with source code available, which I can modify. Somehow I got the impression Nexus 5 had such a bootloader. My mistake.
qwertius said:
I'm trying to flash a modified bootloader, so I needed something I can edit on source code level, compile and flash. But it seems people use the freedom given by the MIT license to take away other people's freedoms: The source code of the Nexus 5 bootloader (although probably LK based, judging by the output of `strings`) is not available online.
I guess I'll need an older device which does have a bootloader with source code available, which I can modify. Somehow I got the impression Nexus 5 had such a bootloader. My mistake.
Click to expand...
Click to collapse
Hi qwertius,
Did you end up getting far with this? It looks like the only way to modify the LK Bootloader is to load it into IDA / a debugging and patch your way.
I have a OnePlus One that I'm trying to patch, I doubt any vendor would release their bootloader source.
UPDATED 2/19/2018
Almost enough here to start attempting debug builds... any other builders/devs out there working on this device? Hopefully some of this will be useful.
Minimal Omni device tree for TWRP (full lineage branch in progress as of 2/19/2018)
https://github.com/mightysween/android_device_motorola_payton
Proprietary blobs/vendor (initial push 2/19/2018):
https://github.com/mightysween/android_vendor_motorola_payton
Partition names/locations/mounts...maybe a few missing still:
https://docs.google.com/document/d/1EkPOkc8uUStKIjRGC2-4jkcXpxmj8v3piGPqZi9ctQM/edit?usp=drivesdk
7.1 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/7.1.1-nougat-release-payton
8.0 KERNEL SOURCE:
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OPW27.57-40
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
gee one said:
So what's the deal with the A/B partitions? I've seen that there are some lineage OS commits to handle the A/B partitions. Would it be possible to load an OS to the A partition and put the recovery on the B partition. I'm not familiar enough to know how much control of the boot process we can have with boot time commands. Does the bootloader have a boot to recovery option?
There doesn't seem to be a recovery partition in the list that you provided. I wonder what the fastboot commands look like... just thinking out loud on the internet. I don't have the phone yet, but I did have a look at Best Buy, so that practically makes me an expert. I have a N5X, so I'm lining up the successor for after its sudden, but inevitable betrayal.
Click to expand...
Click to collapse
There is no traditional recovery partition...handled by boot. A/B is mainly to allow 'seamless' updates (as in OTA that downloads to the other partition for instant reboot). Bit more to it... if you want to read more, check out the Pixel forums.
Well... progress is being made. Wish there were others (there must be!) working on this.
I have the stock kernel, a VERY basic device tree, and cobbled-together vendor... syncing repos and will try to compile TWRP over the weekend. I do not expect it to work
Dealing with this right now on brunch...runs fine up until this point, appreciate any thoughts:
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfs_hw_intermediates/export_includes', needed by '/home/mightysween/android/omni/out/target/product/payton/obj/SHARED_LIBRARIES/libcryptfslollipop_intermediates/import_includes', missing and no known rule to make it
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
Click to expand...
Click to collapse
Do I really need the lollipop libs???? Especially if I just want to compile TWRP and not full omni. Ahhhhhhh....so much fun
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
UPDATE: oops, totally compiled it with the wrong kernel. Haha... working through some defconfig issues, but hopefully nothing too crazy.
mightysween said:
OK, got TWRP to compile
Need to do some testing in the emulator and double and triple check all sources and configs before even thinking about trying to boot it on the actual device.
But just troubleshooting at this point, so looking good for TWRP in coming days!
Click to expand...
Click to collapse
I hope you can do it! Is the first step to get backups and ROMs. I don´t have the phone yet, but later the normal version that is sell in México and want to flash the Android One version (previously anyone get it working).
I'm returning my Amazon version of this phone and getting Project Fi version. I am willing to help in testing.
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
mightysween said:
Well, my boot.img compiles fine... but will not boot to recovery. Given the fact that it is mostly guesswork on the device tree, I am not shocked.
Pushed my working tree to GitHub and will keep working on it...
https://github.com/mightysween/android_device_motorola_payton
Been looking at Pixel 2 TWRP Alpha... holy cow. So much more to it with this partitioning scheme.
Click to expand...
Click to collapse
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
SR3TLAW said:
Have not even peeked into the Pixel 2 forums. I'm afraid this seems to be another ballgame entirely. Do the new Pixel owners even have root passing safety net while allowing these security updates new android phones now get? Gah this is a mess
Click to expand...
Click to collapse
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
mightysween said:
TWRP has been worked on for Pixel2 by several people, including expert Dees Troy, and is still a heavy alpha. I feel pretty good about booting compiled boot images and not bricking on x4 (as far as I have gotten)
I have been compiling my own stuff for many years, and yes -- this new stuff is foreign. But, we will all learn and in a few weeks/months, there will be plenty of action on this device
Click to expand...
Click to collapse
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
i.snehal.kiran said:
try using fixes from https://github.com/TeamWin/android_device_xiaomi_tissot tree. similar android one device!!
Click to expand...
Click to collapse
Thanks, picked up 3 changes from here already... will test them out soon!
So, I have checked out several XDA threads on this Xiaomi device (tissot) and I think it is going to help quite a bit with the A/B issues.
I am still, unfortunately stuck on getting TWRP to boot. Boot.img compiles fine and I can extract it and see TWRP has replaced stock recovery in the ramdisk, but it will not boot into recovery.
Ideally, we need a way to boot a TWRP image without flashing anything... easier said than done with devices that have recovery baked into the boot image. But once that works, we can extract just the ramdisk from my build and write a script to patch it into the stock boot image from the temporary TWRP running on the device.
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Incredible! Looking forward to having a custom recovery!
mightysween said:
Progress! New TWRP thread coming soon...
BTW, there is still a long way to go here... this was just a rudimentary test to get TWRP to boot. Need to start totally fresh with partitions before there is any attempt to actually use it!
Also -- my build environment is a total cluster after weeks of messing around. I need to wipe it and start over. That alone will take me a few days, and TWRP might take a few weeks more.
Click to expand...
Click to collapse
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
f3r.and0 said:
I hope later we can flash the Android One firmware on the retail Moto X4, I supose that OTA update will not work but at least we will have the lastest updates if someone make a flashable version
Click to expand...
Click to collapse
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
mightysween said:
At the very least, we have the ability to create "nandroid" style backup from A1 device. Theoretically, that could allow anyone to install it...
But yes, in the long run, hopefully the actual firmware is released
Click to expand...
Click to collapse
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
DiDGR8 said:
Doesn't the nandroid (or for that matter Flashfire) backup contain personally unique identifiers?
Click to expand...
Click to collapse
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
mightysween said:
Yes, technically... obviously would need to start with a fresh system and limit to non-data partitions.
No one needs to restore someone else's apps... just their boot/oem/system_image
Click to expand...
Click to collapse
This just came to my mind, since this phone has 2 partitions for boot etc. --
Code:
mmcblk0p44: boot_a SIZE:65536 blocks
mmcblk0p45: boot_b
can't we make backup of boot_b ? it will be same as boot_a but unmodified i think ? i mean, use magisk/cf-autoroot/whatever to gain root on boot_a. and make backup of boot_b. so in case if we want to receive update, just restore back boot_b.img to boot_a slot and update through ota ? that way we can practically make full backup which is unmodified. ofc this is until we have fastboot image available and working TWRP.
also it seems all x4's are having same kernel according to this thread. although their build time is different.