{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project Official
For SM-T210(R)/SM-T211 (lt02)
USE AT YOUR OWN RISK!
Please make sure to this thread if you like the port!
ISSUES
Temperature is not available because the kernel does not support it.
Google apps install does not work (Fixed in latest nightly release!)
DOWNLOADS
All nightly releases are on our build repository. DOWNLOAD
All standard releases are on the TWRP website. DOWNLOAD
LINKS
Source Code
Discord Server
CREDITS
@Jespert
@TriDiscord
@gr8nole
@ketut.kumajaya
@paziusss
@ruben15prd
Reserved -
Thanks for maintaining TWRP for this almost 9 year old tablet! It's about time it gets official support. Works perfectly on my SM-T2105.
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
gr8nole said:
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
Click to expand...
Click to collapse
We'll probably never get a custom ROM except for modified stock ones anyways lol.
throwaway019299292 said:
We'll probably never get a custom ROM except for modified stock ones anyways lol.
Click to expand...
Click to collapse
CM11 exist, there are plans to fix bugs.
throwaway019299292 said:
We'll probably never get a custom ROM except for modified stock ones anyways lol.
Click to expand...
Click to collapse
uhh, cyanogenmod 11 recieved its last update for this tablet 7 years ago, so it's been around for a damn long time
gr8nole said:
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
Click to expand...
Click to collapse
ROMs should support the `TARGET_OTA_ASSERT_DEVICE` flag if they're building for multiple devices. Will remove the `lt02` from that, though. Let me know if you have any other codenames for the Tab 3 7.0
TriDiscord said:
ROMs should support the `TARGET_OTA_ASSERT_DEVICE` flag if they're building for multiple devices. Will remove the `lt02` from that, though. Let me know if you have any other codenames for the Tab 3 7.0
Click to expand...
Click to collapse
SM-T2105 shows up as lt02kidswifi in the device field and lt02kidswifiue in the product field on the Device Info HW app.
throwaway019299292 said:
SM-T2105 shows up as lt02kidswifi in the device field and lt02kidswifiue in the product field on the Device Info HW app.
Click to expand...
Click to collapse
This is the line as the final result:
TARGET_OTA_ASSERT_DEVICE := lt02wifi,lt02wifijpn,lt02wifizc,lt02wifizs,lt02wifiue,lt02kidswifi,lt02kidswifiub,lt02kidswifiue,lt02kidswifiww,lt02kidswifixw,lt02kidswifizc,lt02kidswifizh
Will merge when other changes are completed. Thanks!
This has inspired me to TRY to create a custom rom for the T210R.
I'm trying diligently to make one based on CM 14.1.
Anyone have any ideas, I'm more than happy to collaborate.
Thanks for the recovery!
CaptainBenSisko said:
This has inspired me to TRY to create a custom rom for the T210R.
I'm trying diligently to make one based on CM 14.1.
Anyone have any ideas, I'm more than happy to collaborate.
Thanks for the recovery!
Click to expand...
Click to collapse
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
CaptainBenSisko said:
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
Click to expand...
Click to collapse
Hehe, I understand. It takes so much time.
CaptainBenSisko said:
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
Click to expand...
Click to collapse
Any GitHub sources? We can maybe try to help?
TriDiscord said:
Any GitHub sources? We can maybe try to help?
Click to expand...
Click to collapse
These are what I was working with, all credit to the OP's. (Especially gr8nole, he seems to have his hand in all things T210R)
GitHub - lt02-dev/android_device_samsung_lt02wifi: Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi)
Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi). Contribute to lt02-dev/android_device_samsung_lt02wifi development by creating an account on GitHub.
github.com
GitHub - gr8nole/android_vendor_samsung_lt02wifi: Proprietary files for lt02wifi
Proprietary files for lt02wifi. Contribute to gr8nole/android_vendor_samsung_lt02wifi development by creating an account on GitHub.
github.com
sm-t210r / android_kernel_samsung_lt02 · GitLab
GitLab.com
gitlab.com
Don't fall down the rabbit hole, but if you wanna give it a go, I'm more than happy to collab.
CaptainBenSisko said:
These are what I was working with, all credit to the OP's. (Especially gr8nole, he seems to have his hand in all things T210R)
GitHub - lt02-dev/android_device_samsung_lt02wifi: Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi)
Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi). Contribute to lt02-dev/android_device_samsung_lt02wifi development by creating an account on GitHub.
github.com
GitHub - gr8nole/android_vendor_samsung_lt02wifi: Proprietary files for lt02wifi
Proprietary files for lt02wifi. Contribute to gr8nole/android_vendor_samsung_lt02wifi development by creating an account on GitHub.
github.com
sm-t210r / android_kernel_samsung_lt02 · GitLab
GitLab.com
gitlab.com
Don't fall down the rabbit hole, but if you wanna give it a go, I'm more than happy to collab.
Click to expand...
Click to collapse
Those are very buggy sources for CyanogenMod 11. I doubt that 14.1 will work on this.
@CaptainBenSisko, @TriDiscord, I tried building 14.1 for T210R this month using
https://github.com/SamsungGalaxyTab3
but ran into the exact same problem and error messages that the previous person @sscsps was getting in this thread
https://forum.xda-developers.com/t/abandoned-not-working-lineageos-14-1-for-t211.3621818/
There's no boot animation and my last_kmsg shows the same problem.
retiredtab said:
@CaptainBenSisko, @TriDiscord, I tried building 14.1 for T210R this month using
https://github.com/SamsungGalaxyTab3
but ran into the exact same problem and error messages that the previous person @sscsps was getting in this thread
https://forum.xda-developers.com/t/abandoned-not-working-lineageos-14-1-for-t211.3621818/
There's no boot animation and my last_kmsg shows the same problem.
Click to expand...
Click to collapse
I'm just curious, has anyone tried MM yet?
I think I found a guy who got lollipop to work on the t210r but it was canceled
HackerMan195 said:
I think I found a guy who got lollipop to work on the t210r but it was canceled
Click to expand...
Click to collapse
Ooh! Could you share a link?
Related
Hi everyone.
As you all know, Samsung distributes source code as tarballs which isn't the best way to redistribute kernel source code
git is the best modern way to work with Linux Kernel sources, designed by Linus himself in this purpose.
So, i made an organization on github for that.
https://github.com/sgs3
And yea, that means source code has been released, head on to http://opensource.samsung.com/
Kernel Sources :
https://github.com/sgs3/GT-I9300_Kernel
Branches :
master :- branch you should use(for developers), will contain fixes and more in the future (currently identical to stock_update4)
stock :- Kernel sources from GT-I9300_ICS_Opensource.zip, unmodified
stock_update1 :- Kernel sources from GT-I9300_ICS_Opensource_Update1.zip, unmodified
stock_update4 :- Kernel sources from GT-I9300_ICS_Opensource_Update4.zip, unmodified
If anyone wants to commit any fixes / anything else, fork and shoot a pull request
How to Build :
Get teh sauce:
Code:
git clone git://github.com/sgs3/GT-I9300_Kernel.git
cd GT-I9300_Kernel
git checkout master
Tell it to use our config:
Code:
make ARCH=arm CROSS_COMPILE=/path/to/toolchain m0_00_defconfig
Teh real build:
Code:
make CROSS_COMPILE=/path/to/toolchain
or
Code:
make -j `cat /proc/cpuinfo | grep "^processor" | wc -l` CROSS_COMPILE=/path/to/toolchain
The compiled kernel is arch/arm/boot/zImage
Was about to post this
Will start compiling and have a kernel up and running soon I hope. This time in contrast to the S2, it's time for serious developing.
Here's a direct link to the S3 files: http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-i9300
This is great news guys,
lets hope that we will also have a proper CWM recovery soon.
stickied
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
EDIT: this is the patch in question: http://git.kernel.org/?p=linux/kern...it;h=371a689f64b0da140c3bcd3f55305ffa1c3a58ef. Apparently Sammy took this out again in their sources (according to somebody else, I haven't had time to confirm yet, but I can see the boot partitions do *not* appear on my device), they may have bastardized it further ...
Chainfire said:
stickied
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
Click to expand...
Click to collapse
No CF-Root Kernels for the i9300?
Toss3 said:
No CF-Root Kernels for the i9300?
Click to expand...
Click to collapse
Well it's not needed as much due to the separate recovery, but if there's demand, I'll build CF-Root's... but those are based on Samsung binaries, not source.
Great! I'll go through this when I get the time.
Chainfire said:
Well it's not needed as much due to the separate recovery, but if there's demand, I'll build CF-Root's... but those are based on Samsung binaries, not source.
Click to expand...
Click to collapse
Of course I want a CF kernel
pglmro said:
Of course I want a CF kernel
Click to expand...
Click to collapse
I think everyone of us want a CF-Root-Kernel
Roughnecks said:
I think everyone of us want a CF-Root-Kernel
Click to expand...
Click to collapse
I don't really see the point why we should make that. I have flashed cwm with Odin and then the SuperSu cwm flashable zip available here on xda. Then installed busybox installer from the play store. Much easier to do as letting Cainfire always compile a cf-root kernel for us.
L
great seeing some a class developers here!!
thanks for opening this thread..
and good to know ya'll have a s3 aswell..
grtz!
Great news , hope to see some nice custom kernels soon!
Kernel dev's:
Please share your github if you start then
what?update#1 is already out?
Hope Samsung release a cleaner source this time
sakindia123 said:
what?update#1 is already out?
Hope Samsung release a cleaner source this time
Click to expand...
Click to collapse
Looks like they messed up the first zip, so the quick update
Only change i can see from stock to stock_update1 is the changing of file mode from 0755 to 0644
Samsung releases source code for the Galaxy S III
UPDATE 1 is out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Chainfire said:
@whomever is building from source, please include the MMC driver patch that enables boot partition visibility. Maybe I'll even do it myself... this'll let TriangleAway work, so we can reset the flash counters
Click to expand...
Click to collapse
They seem to have hacked it out pretty crudely (certainly the korg patch won't apply cleanly). No device here, can't really test this, but the attached patch should properly allocate any mmc boot partitions.
A couple more patches before I rm
No device here and no idea if I'll ever get one, but I thought I would post couple more cosmetic (yet instrumental) patches for your tree so that my last 15 minutes wouldn't be in vain.
#1: m0_00_defconfig: Run through menuconfig;disable GCC strict checking. Otherwise I get a lot of noise with codesourcery toolchains
#2: Add .gitignore files from korg trees.
Take care
Anyone else get compilation error due to SVN_REV variables in these Makefiles:
drivers/media/video/samsung/mali/Makefile
drivers/media/video/samsung/ump/Makefile
I comment out the lines and replaced them with
Code:
SVN_REV=:0000
I used 0000 because of the comment in the Makefile.
Now, it compiles without error (though untested since I don't own S III)
Nope ... didn't get those errors!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We desperately need a custom ROM for this model as well, since it's taking over for the i9505, at least here in Norway and Germany. But i guess many other countries as well. My idea is to port a CM10.2/CM11 ROM for this, as the Samsung source files probably will be more compatible with that, than CM11 at the moment.
LATEST NEWS
- Samsung released the open source files for KK: http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=e330S_KK
- dridri85's CM11 testing - https://github.com/dridri/android_device_samsung_ks01lte
- dridri85's CWM 6.0.4.6 - http://forum.xda-developers.com/showthread.php?t=2613466
Big applause for him!!
ROOTING PROCEDURE:
http://forum.xda-developers.com/showthread.php?t=2529064
USEFUL INFORMATION:
Extracted from build.prop via ADB:
ro.product.manufacturer=samsung
ro.product.device=ks01lte
Porting CyanogenMod to your own Device: http://wiki.cyanogenmod.org/w/Doc:_porting_intro#Some_tips_on_porting_CyanogenMod_to_your_own_device
GSM Arena Phone Specs: http://www.gsmarena.com/samsung_i9506_galaxy_s4-5542.php
Samsung Open Source: http://opensource.samsung.com/ (search for i9506)
Placeholder for etc.
Sounds great - I was already thinking of selling I9506 and going for I9505. Hopefully this phone gets more attention soon!
ig000r said:
Sounds great - I was already thinking of selling I9506 and going for I9505. Hopefully this phone gets more attention soon!
Click to expand...
Click to collapse
Yeah, i was thinking the same, but here in Norway the i9505 is actually more expensive, even though it is older/slower! When i saw the CM Guide + that i have been building LX Optimus 4X HD ROM's lately using Github source, i thought i'd give it a try!
Hopefully more people will help!
I suggest to look into Note 3 (SD800 version) forum for CM availability and port it to I9506 if it exists. Basically, Note 3 and i9506 are the same devices.
You will save a lot of time if you port CM from Note 3.
P.S.: I'm happy with TouchWiz custom ROM and "hand-made" kernel. Never looked into CM possibility.
i assume the note3 kernel would probably work with some modifications
i9506 doesnt have many devs so it would take a while
bluefa1con said:
i assume the note3 kernel would probably work with some modifications
i9506 doesnt have many devs so it would take a while
Click to expand...
Click to collapse
But what else do we have to modify than the Kernel? I found a Note 3 repository in CyanogenMod @ Github and forked it..
https://github.com/faabak/android_device_samsung_ks01lte
But i think it's missing some files.. Have changed the codename in the files to "ks01lte", but i guess it's more we have to do. Downloading CyanogenMod CM11 sources now on my Ubuntu machine..
faabak said:
But what else do we have to modify than the Kernel? I found a Note 3 repository in CyanogenMod @ Github and forked it..
https://github.com/faabak/android_device_samsung_ks01lte
But i think it's missing some files.. Have changed the codename in the files to "ks01lte", but i guess it's more we have to do. Downloading CyanogenMod CM11 sources now on my Ubuntu machine..
Click to expand...
Click to collapse
You got a PM from me ... hope it helps you
Sent from my GT-I9506 using XDA Premium 4 mobile app
Hi o/
I'm on it too, I've downloaded the kernel sources from Samsung's open source website so it should at least boot (even without modules like camera, bt, ..)
Currently the problem is that there are misconfigurations in their kernel resulting in undeclared/undefined errors, so it will take a bit longer than I expected to get a fully compiled ROM. Or maybe it's only because I'm trying to build CM11
btw, I have a ks01lteskt device, is it the "mainstream" one or do I have a special model ? Can you check too guys ? ^^
Edit : does removing TARGET_OTA_ASSERT_DEVICE is enough to let the recovery install it with a different device id ?
Keep on men! really we want CM for that great device!
Envoyé de mon GT-I9506 en utilisant Tapatalk
Compiled ! But I can't get it to work...
The Samsung logo show up, then it says that it is a custom kernel, then freezes a few seconds and reboot...
Any clue ?
I think you better ask on cyanogen dev thread
Envoyé de mon GT-I9506 en utilisant Tapatalk
I don't find the CM thread :laugh: There's too much things on xda
EDIT : I got CWM 6.0.4.6 working !! But system still won't boot...
dridri85 said:
I don't find the CM thread :laugh: There's too much things on xda
EDIT : I got CWM 6.0.4.6 working !! But system still won't boot...
Click to expand...
Click to collapse
Wow, this is awesome.. If we can make this running, i hope it's OK for you if we use this thread for it, and i will add all the information, screenshots, version history, updates etc in the first post!
This is a big step anyway.. Have you been into github at all? Cause then you could perhaps make a repository there and more people can compile (including me, since i've compiled a lot lately)!
Also, perhaps it would be clever to post a topic here regarding the boot problems!
http://forum.cyanogenmod.com/forum/23-unofficial-ports/
Ok, everything should be here now : https://github.com/dridri/android_device_samsung_ks01lte
Here is the pre-compiled recovery :
Odin tar - https://dl.dropboxusercontent.com/u/81758777/CWM_6.0.4.6_Non-Touch_GT-I9506.tar
Flashable zip - https://dl.dropboxusercontent.com/u/81758777/CWM_6.0.4.6_Non-Touch_GT-I9506.zip
Some news !
I finally got the kernel booting and working, the cyanogenMod loading logo now shows up but enters in bootloop. The new problem is that adb is detected as 'offline' and I can't debug anything
dridri85 said:
Some news !
I finally got the kernel booting and working, the cyanogenMod loading logo now shows up but enters in bootloop. The new problem is that adb is detected as 'offline' and I can't debug anything
Click to expand...
Click to collapse
Try a later version of adb? I had this offline with stock rom and older adb.
JohnnyInBriz said:
Try a later version of adb? I had this offline with stock rom and older adb.
Click to expand...
Click to collapse
Yeah, i remember i hade some problems with older versions of ADB on my LG P880 as well! So let's just cross our fingers that's the problem..
Thank you guys I can now access adb and see the loading errors !! (And the only things I see is missing lib files, hope that adding them will be enough :3 )
Okay guys, got it working, I can boot CM 11 !!!
But there are still major problems : everything lag, the baseband is unkown, SIM card not recognized, wifi and bluetooth doesn't work, no audio at all xD
EDIT: baseband, RIL, SIM card and LTE network now works correctly !
</> Developpers Only </>
As you may know it, GALAXY Grand Prime is powered by a 64Bit Entry-Level Quad Core CPU, that makes developpment on this device VERY HARD It's like Intel Atom Processors
Anyway, I tried to make a repo for building TWRP GALAXY Grand Prime by refering to Huawei G620S' Repo by GitHub member "EloYGomeZ" BIG thanks to him.
If you're interested in building TWRP, you can use this repo. Feel free to use it, but please remember to give credits when done.
The Repo isn't yet done, it may contains many bugs and errors; plus I can't test it or test a TWRP build since I don't have my hand on that device (should have one in 2 weeks).
Update as of 18/6/2015: TWRP has been compiled for Grand Prime
TWRP ==> http://forum.xda-developers.com/grand-prime/development/share-twrp-2-8-4-0-galaxy-prime-t3064506
Philz Touch :
Download ==> https://mega.co.nz/#!SQ8XkIiI!Kj_9rhfVY8bz0nRjZGDGra4Bs3Nen-87O4vhWGHlVzc
Thread ==> http://forum.xda-developers.com/gra...share-galaxy-grand-prime-sm-g530h-f0-t3057571
Source ==> http://www.phonandroid.com/forum/ph...d-galaxy-grand-prime-sm-g530f-fz-t116883.html
Current CM12 ETA:- Compiled successfully
- Bootable
- CanNOT get to home launcher!
GitHub an sources:
@K_TECH 's device tree and all sources needed to compile cm12 ==> https://github.com/fortunave3gxx
fortuna3g TWRP Repo ==> https://github.com/Nonta72/fortuna3g-twrp (mine)
Huawei G620S TWRP Repo (used as a reference): https://github.com/Nonta72/android_device_huawei_g620s-twrp (EloYGomeZ)
Device Tree (WIP): https://github.com/Nonta72/fortuna3g-tree (mine)
Source Code for KK: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-G530
Wow great,
IMO, its not about 64bit chipset, as we know, lenovo a6000/k30 have the same chipset 64bit.
But have development, we have CWM, Phillz recovery, cm11, MIUI rom
The main problem to devevelop grand prime is qualcomm secure bootloader that protect the device. We need to disable the secure bootloader first. CMIIW
Shinkumara said:
Wow great,
IMO, its not about 64bit chipset, as we know, lenovo a6000/k30 have the same chipset 64bit.
But have development, we have CWM, Phillz recovery, cm11, MIUI rom
The main problem to devevelop grand prime is qualcomm secure bootloader that protect the device. We need to disable the secure bootloader first. CMIIW
Click to expand...
Click to collapse
I didn't see Lenovo a6000 CWM/TWRP and Custom ROMs yet.
About Bootloader on Grand Prime, I never heard about this
Maybe we should start unlocking this 1st
I can't do anything as of now, since I don't have the decice yet.
i hope i can learn somewhere how to build twrp. Anyway i will support u guys.
Samir96 said:
i hope i can learn somewhere how to build twrp. Anyway i will support u guys.
Click to expand...
Click to collapse
If you think you can be tester and don't care about flashing your phone at least twice a day, then you can help!
can you please fix it. recently i don't have the device. building cm 11
nilimahona said:
can you please fix it. recently i don't have the device. building cm 11
Click to expand...
Click to collapse
What's the problem with the BoardConfig ?
PS: I also don't own the device yet.
The board config should be in KK Kernel source.
I'll test extensively I have 8 sm-g530az (cricket USA)
All rooted with cwm philz recovery
Nonta72 said:
If you think you can be tester and don't care about flashing your phone at least twice a day, then you can help!
Click to expand...
Click to collapse
krazy_smokezalot said:
I'll test extensively I have 8 sm-g530az (cricket USA)
All rooted with cwm philz recovery
Click to expand...
Click to collapse
The device already have CWM.
All you need now is CyanogenMod.
Nonta72 said:
The device already have CWM.
All you need now is CyanogenMod.
Click to expand...
Click to collapse
Would you know if anyone has started on that project?
krazy_smokezalot said:
Would you know if anyone has started on that project?
Click to expand...
Click to collapse
I already started, currently getting the device tree ready.
Lets start ^_^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm getting stuck in this error :3
source: http://github.com/fortunave3gxx
Try "apt-cache search audio_defs.h" to find the dev package that is missing. Sometimes it work
Sent from my SM-G530FZ using XDA Free mobile app
kentone said:
Try "apt-cache search audio_defs.h" to find the dev package that is missing. Sometimes it work
Sent from my SM-G530FZ using XDA Free mobile app
Click to expand...
Click to collapse
Nevermind, i solved that errors in an hour ago ^_^
The build progress has been done, but i get an error when i try to flash it"binnary error". And it's come from recovery
If it ready, i'll upload my device configuration, Stay tuned
my own source: http://github.com/fortunave3gxx
K_TECH said:
The build progress has been done, but i get an error when i try to flash it"binnary error". And it's come from recovery
If it ready, i'll upload my device configuration, Stay tuned
my own source: http://github.com/fortunave3gxx
Click to expand...
Click to collapse
try to replace the update-binary in META-INF folder
The you can building kernel from source code boeffla working with grand prime ... kernel boeffla is 1 of the famous kernel. if you are building is too good. I very much hope into you. Thx you
Nonta72 said:
try to replace the update-binary in META-INF folder
Click to expand...
Click to collapse
Can you share your update-binary?
recoman said:
The you can building kernel from source code boeffla working with grand prime ... kernel boeffla is 1 of the famous kernel. if you are building is too good. I very much hope into you. Thx you
Click to expand...
Click to collapse
I don't think Lord Boeffla does support the Grand Prime.
K_TECH said:
Can you share your update-binary?
Click to expand...
Click to collapse
I'd love to, but I don't have the device yet. That's why I even stopped the project.
Suggestion: try to find a similar device (same chipset) that have CM or a CWM ROM, download that ROM and replace your binary with the one in that ROM. I heard the Huawei G620S (with MSM8916) have a working CyanogenMod, you may want to check that out.
Suggestion 2: make sure your updater-script is well formed, I can help you with that if needed, just upload that file.
Hello all,
I'm trying to port an AOSP ROM to the osprey, I already made some steps but would need some help from much better skilled devs.
Here is the code: https://github.com/motogaosp
The manifest: https://github.com/motogaosp/android_manifest
At the moment the ROM starts without big problems but there are some errors while booting up.
Feel free to participate, fork the code, send pull request or whatever you think can help the project, the goal would be to have a clean AOSP ROM for our osprey.
Working:
WiFi
Bluetooth
Back camera
Front Camera
Touchscreen
Sensors:
Accelerometer
Light
Magnetic field
Orientation
Proximity
NOT working:
Sound
RIL
Mobile data (LTE/3G)
GPS
XDA:DevDB Information
MotoG 3 AOSP, ROM for the Moto G 2015
Contributors
udK
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2016-03-15
Last Updated 2016-03-15
What's the diff btw CAF and AOSP?? btw thank u for yo efforts!
I hope to see link soon.
Forever Alone said:
What's the diff btw CAF and AOSP?? btw thank u for yo efforts!
Click to expand...
Click to collapse
@Forever Alone: http://forum.xda-developers.com/showpost.php?p=63433600&postcount=2
is it 100% aosp without any cm patches?
Yes, from CM I use (for the moment) the build scripts part as it has all the stuff needed to include qcom repositories but this does not affect on Android itself.
udK said:
Yes, from CM I use (for the moment) the build scripts part as it has all the stuff needed to include qcom repositories but this does not affect on Android itself.
Click to expand...
Click to collapse
Any idea when will we have download link?
As you as a moderator knows already xda doesn't accept place holder.
Yousvel said:
Any idea when will we have download link?
As you as a moderator knows already xda doesn't accept place holder.
Click to expand...
Click to collapse
I don't think it's particularly considered a place holder when the source code and manifest has been posted in search for assistance to get to a user capable produce. Works In Progress are allowed and maybe the current developer finds it moot to release a link publicly that's just going to flood his thread with endless.... ("WTF, Why this no work? U said unfished product, but it have problems, I no approve") ..... yeah stuff like that.
..and the most stupid question is:
Yousvel said:
Any idea when will we have download link?
Click to expand...
Click to collapse
If you can help the project ok, otherwise go away from this thread please.
Thanks.
udK said:
..and the most stupid question is:
If you can help the project ok, otherwise go away from this thread please.
Thanks.
Click to expand...
Click to collapse
No problem brother. And thanks for answering. It's was a real pleasure to know of this project. Good luck!
Count me in, this is essentially what I've been working on with my build.
With the addition of all RRO commits but for now I'd like clean as well, I'll start forking this weekend. Thanks for this! Big help having other devs bring aosp for our device.
man , count me in ,im happy to help . I can configure the aroma installer for it ?
christopherrrg said:
Count me in, this is essentially what I've been working on with my build.
With the addition of all RRO commits but for now I'd like clean as well, I'll start forking this weekend. Thanks for this! Big help having other devs bring aosp for our device.
Click to expand...
Click to collapse
Awesome thanks!
therealduff1 said:
man , count me in ,im happy to help . I can configure the aroma installer for it ?
Click to expand...
Click to collapse
Honestly I don't think that Aroma installer would be so useful on AOSP ROM btw, feel free to work on it.
If someone wants to give me some more in depth instructions on initiating a build and where to find the proper Dev tree and vendor files for Marshmallow I'd be more than willing to help with development. Since Xenon HD is AOSP base we at least know it's doable. The only bugs with that ROM are that WiFi refuses to turn back on after a soft reboot, and the GPS is damn near inoperable.
I don't know much about building Android per se, but it's something I've been thinking about getting into. I may not be able to be much of a help but I'm certainly willing to learn.
@l3ones: https://github.com/motogaosp/android_manifest
yee! Finally got a fully booting ROM! :good: :good:
Today/tomorrow will try fix BT, WiFi and other stuff.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
l3ones said:
If someone wants to give me some more in depth instructions on initiating a build and where to find the proper Dev tree and vendor files for Marshmallow I'd be more than willing to help with development. Since Xenon HD is AOSP base we at least know it's doable. The only bugs with that ROM are that WiFi refuses to turn back on after a soft reboot, and the GPS is damn near inoperable.
I don't know much about building Android per se, but it's something I've been thinking about getting into. I may not be able to be much of a help but I'm certainly willing to learn.
Click to expand...
Click to collapse
yeah i would happily join you on learning how to compile build etc
udK said:
@l3ones: https://github.com/motogaosp/android_manifest
yee! Finally got a fully booting ROM! :good: :good:
Today/tomorrow will try fix BT, WiFi and other stuff.
Click to expand...
Click to collapse
Good to see
therealduff1 said:
yeah i would happily join you on learning how to compile build etc
Click to expand...
Click to collapse
l3ones said:
If someone wants to give me some more in depth instructions on initiating a build and where to find the proper Dev tree and vendor files for Marshmallow I'd be more than willing to help with development. Since Xenon HD is AOSP base we at least know it's doable. The only bugs with that ROM are that WiFi refuses to turn back on after a soft reboot, and the GPS is damn near inoperable.
I don't know much about building Android per se, but it's something I've been thinking about getting into. I may not be able to be much of a help but I'm certainly willing to learn.
Click to expand...
Click to collapse
Here's a push to start guys, take your time to read read read. Once you're done these just rifle ROM build questions at Google and check out other devices for an idea on how the structure works.
( Senior member but am still extremely new at building, no public builds just small CM stuff but these guides helped me put a lot together. )
http://forum.xda-developers.com/showthread.php?t=2364970
https://source.android.com/source/initializing.html
http://xda-university.com/as-a-developer/getting-started-building-android-from-source
---------- Post added at 01:23 PM ---------- Previous post was at 01:19 PM ----------
udK said:
@l3ones: https://github.com/motogaosp/android_manifest
yee! Finally got a fully booting ROM! :good: :good:
Today/tomorrow will try fix BT, WiFi and other stuff.
Click to expand...
Click to collapse
Is this using msm8916 kernel source?
(I can see the screen, just unsure if custom built.)
christopherrrg said:
Is this using msm8916 kernel source?
(I can see the screen, just unsure if custom built.)
Click to expand...
Click to collapse
I started from Motorola sources (https://github.com/MotorolaMobilityLLC/kernel-msm/tree/marshmallow-6.0.0-release-osprey) and then picked some patches from https://github.com/moto8916/android_kernel_motorola_msm8916 to get the kernel booting.
Dude, you are making really quick progress. Yesterday all I saw working was the touchscreen & cameras, now we have WiFi and Bluetooth up and running? At this rate we may have a fully working AOSP ROM in no time, thanks to you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
THIS DEVICE IS CURRENTLY A TESTING KERNEL AND MAY NOT WORK. BACKUP YOUR BOOT.IMG BEFOREHAND.
Click to expand...
Click to collapse
Features
Built on UBERnaro toolchain
High tickrate to avoid jitter
Lib optimisations
F2FS support
Click to expand...
Click to collapse
Installation instructions
* Flash via TWRP, or Franco Kernel Manager (needs testing for this device)
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is available at ftp://ftp.lasterhub.me.
Click to expand...
Click to collapse
FAQ
Tag me in XDA's Amazon.. oh wait. There's no group (yet?). Just PM me for now.
Click to expand...
Click to collapse
Special Thanks To
Code:
* MTK for being retarded
XDA:DevDB Information
Zest Kernel Projecc, Kernel for the Amazon Fire
Contributors
LazerL0rd, ggow, k4y0z
Source Code: https://gitlab.com/ZKP/ford
Kernel Special Features:
Version Information
Status: Testing
Created 2019-05-28
Last Updated 2019-05-29
LazerL0rd said:
Last Updated 2019-05-28
Click to expand...
Click to collapse
Nice.
May I ask for a little safety step to be added. Someone here is gonna not read and try to flash this on 'Austin'
And your anykernel.sh has device check set at NO. (do.devicecheck=0). Maybe better to make it (do.devicecheck=1)
Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?
newinnov said:
Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?
Click to expand...
Click to collapse
Austin or ford?
Rortiz2 said:
Austin or ford?
Click to expand...
Click to collapse
Ford 2015 it is
mrmazak said:
Nice.
May I ask for a little safety step to be added. Someone here is gonna not read and try to flash this on 'Austin'
And your anykernel.sh has device check set at NO. (do.devicecheck=0). Maybe better to make it (do.devicecheck=1)
Click to expand...
Click to collapse
Ah, yes. Weirdly some TWRPs react funnily to this command so on-release I always leave it off. Seems there's only one TWRP here tho. Thanks, will do :highfive:.
newinnov said:
Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?
Click to expand...
Click to collapse
The kernel seems to be pretty much correct, it's the flashing procedure that I'm uncertain of. It's the same base kernel @ggow uses with some building fixes and my additions. But yes, this is a development kernel until anyone can actually get it working with the patch.
LazerL0rd said:
The kernel seems to be pretty much correct, it's the flashing procedure that I'm uncertain of. It's the same base kernel @ggow uses with some building fixes and my additions. But yes, this is a development kernel until anyone can actually get it working with the patch.
Click to expand...
Click to collapse
I had a stock built kernel from unmodified Amazon source, and installed it with anykernel, before I discontinued the project. @ggow showed me up. Way up, by making his kernel free from that Amazon log feature.
Anyway anykernel flashes this device with the exploit no problem.
Think I had used anykernel 2 though. You have used 3.
I will look again, and see if I see any difference in the scripts.
EDIT:
I just tried to flash with the anykernel2 script i had used before. And result was bootlooping on the Amazon logo.
mrmazak said:
I had a stock built kernel from unmodified Amazon source, and installed it with anykernel, before I discontinued the project. @ggow showed me up. Way up, by making his kernel free from that Amazon log feature.
Anyway anykernel flashes this device with the exploit no problem.
Think I had used anykernel 2 though. You have used 3.
I will look again, and see if I see any difference in the scripts.
EDIT:
I just tried to flash with the anykernel2 script i had used before. And result was bootlooping on the Amazon logo.
Click to expand...
Click to collapse
I tried both AK2 and AK3 with osm0sis seeing no issues in my AK configuration, so it’s not that.
Yah, I think something was changed and some sort of check was added in. I think I tried dm-verity disabling too but I may be wrong. My kernel is available at https://lasterhub.me/zk.html for anyone to try though ( click menu then BETA before selecting as no release version was released yet ).
I can't get the link to work? This ded?
beynolds.rurt said:
I can't get the link to work? This ded?
Click to expand...
Click to collapse
Yes. This is dead. OP never followed up after he was told this did not work as claimed.
mrmazak said:
Yes. This is dead. OP never followed up after he was told this did not work as claimed.
Click to expand...
Click to collapse
Knew it was too good to be true