I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for p900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/RVXpEgc6c4GKo - this is modded recovery. flash via odin
2. https://yadi.sk/d/CHl8wTYYc4GMZ - patched kernel. (patched my 1.3 pro kernel)
https://yadi.sk/d/D2riVhEgc4GPP - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/jc4uxZeCc4GRb - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.
reserved
more reserved
bonuzzz said:
this is beta release. for p900 only.
I'll wrote full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
Click to expand...
Click to collapse
I saw earlier that you had plans for this, but I didn't expect it to happen this quickly.
Anyway, great initiative.
WOW
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
m_carleone82 said:
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
Click to expand...
Click to collapse
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers. I thought about ubuntu, but now I'm not going to have a deal with it. I advice you to look linux deploy
Great job
bonuzzz said:
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers.
Click to expand...
Click to collapse
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
ESmazter said:
Great job
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
Click to expand...
Click to collapse
If you could get it working it would be great.
arcadia2uk said:
If you could get it working it would be great.
Click to expand...
Click to collapse
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
bonuzzz said:
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
Click to expand...
Click to collapse
My appreciation was actually meant for ESmazter saying: I will look into it
oops, i haven't noticed esmazter's phrase
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
bonuzzz said:
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
Click to expand...
Click to collapse
I was still hoping to get the minor issues resolved, notably the issue with Rom's installer are not shown in the installed ROM's section.
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
hhairplane said:
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
Click to expand...
Click to collapse
I dont have any plans to port to other devices. It doesnt fully working and I dont have any progress with it...
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
brock28 said:
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
Click to expand...
Click to collapse
I dont recommend to use this multirom because it has the bug with sharing kernel. So you need to use similar roms as primary and as additional. I dont have an idea how to solve it at this moment.
Related
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
--WiFi (Partially: Signal strength indicator broken. Disable avoiding poor networks in advanced menu)
--GPS
--Internal sdcard
Doesn't work:
--Camera
--3G
--Sound
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
==Boot image gzip for flashing with system image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part07.20120724.img.gz
==System image gzip for flashing with boot image using nvflash or dd from recovery==
http://dl.dropbox.com/u/1737679/part08.20120724.img.gz
Remember to always do a backup copy of your device images before flashing new ones.
Great work mate! I assume that if we want to test this later on our tablets, we need to be rooted?
suntechnic said:
Hello!
I've spend some days to compile JB for TPT ROW 32Gb. And there are the following results:
Works:
--Display. Interface is _very_ smooth
--Pen
--Automatic brightness
--External SD
--USB host
--Bluetooth
Doesn't work:
--Camera
--WiFi
--3G
--GPS
--sdcard fuse mounting
I also had to repack boot image to include configuration changes (init* files).
See attached logcat.
next step I will try to add proprietary source files for Wifi and camera and compile JB again.
Click to expand...
Click to collapse
Woohoo! Look forward to trying this!
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Great work, thanks! I'm glad that there is work going on!
Great news! As I installed ota3 before rooting my device, I hope that there will be some way to get cwm and root working...
Sent from my GT-I9300 using xda premium
Very happy that you're working on a new ROM for our device!!!
And I really hope that someone finds a way to root OTA3 since I was also too dumb to do that before updating.
Cheers!
Wow!! Keep up the good work!!!
can't wait, great work!
Great!
I thought I will be first
According to full_indigo device ID, it is AOSP, not CM? Wow..
I think together we could at last make 3G work as other hw are relatively easy to fix(may be not true for camera as sources again changed). I familiar with Qualcomm RIL framework and can't wait to see how it works with tablet and more opensource hardware module..
I also had to repack boot image to include configuration changes (init* files).
Click to expand...
Click to collapse
lenovo haven't packed init scripts? Oo how it works then? ;/
PS: hello from Russia
obscure.detour said:
This is amazing work! Thank you.
I see Lenovo finally released the ICS source code. Maybe this will help you get some other stuff working.
Also, how were you able to flash your build? Have you not upgraded to OTA3? I'm assuming you still have CWR working.
Thanks again.
Click to expand...
Click to collapse
Lenovo released ICS open source code but they forgot to release new kernel sources. This prevents me from building bcmdhd driver instead of bcm4329. It looks like JB is oriented for NL80211 wireless interface and not WEXT.
this isnt for the K1 is it
It's for tpt only
When can we see this in a flashable version? Not to sound pushy, I know we have all see the development slow down.
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
What is TPT
Not to sound stupid but what is TPT? I have a K1 as well and am wondering if this will work?
TPT= ThinkPad Tablet
Lenovo released ICS open source code but they forgot to release new kernel sources
Click to expand...
Click to collapse
yes I also tried to get more info but for now no response. At last they released external folder of their custom build, which also contains alsa-audio, as I seen in cm9 device tree, it should fix audio with ease(maybe after patch as sources again changed in JB).
It looks like JB is oriented for NL80211 wireless interface and not WEXT.
Click to expand...
Click to collapse
but WEXT is there isn't it?
Anyway, congrats on working wifi.
Has anyone else got this up and running? I tried uninstalling CWM and reflashing part 7 and 8 but still no luck.
mr toasty said:
Are there any other tricks we need to get this up and running? I flashed partition 7 and 8 using NVflash but my tablet is stuck in a boot loop at "lenovo"
EDIT: Is this incompatible with CWM recovery?
Click to expand...
Click to collapse
Some of existing software probably blocks normal startup. It is always advised to clean dalvik-cache and user data (backup first). It's up to you.
Right after Lenovo logo you should see 'Android: Optimizing applications' or something similar.
Hi,
I have just bought a new Xperia Pro and Here is My first Contribution.Hope you guys like it.
I have tested it personally on the Unoffical MIUI port for PRO.But it should work on other Kernels and Xperia Devices as well.
I am posting a few Screens for you guys and as you can see lxde is already pre-installed for you guys.
Feel Free to comment
Disclaimer:-
I am Not responsible if anything Happens to your Phone.You do it at your own Risk and Responsibilty,
If you Screw Up then dont Blame Me.
I am not responsible for Anything.
What is chroot?
A chroot image is like a Virtual Machine where you are running an O.S within an O.S.The point of this is that you have a whole Linux System running on a phone where you can ofcourse access all the utilities available in Linux.and as it runs inside of android you dont need to flash anything and can use both the chrooted O.S and Android together.
Things required:-
1)Terminal
2)Root
3)Sdcard with atleast 2GB of free space
4)A Brain
Please Consider Donating to add to my late night coffee and Books Fund.
Link:-
https://www.dropbox.com/s/4k1f5l9jxy2nr9n/debian.7z
Mirror:-
http://www.4shared.com/archive/uNEXsuNS/debian.html?refurl=d1url
Note:
Please read the ReadMe.txt file attached to this post first for instructions.
A special request to all those who are donatinglease send me a P.M so that i know who you guys are.
Donators:-
None So Far
Thank you.
Posting Ubuntu over Here
Remember to Read the Read Me File First.
Link:-
https://www.dropbox.com/s/z7ekya7u7zo19p8/ubuntu.7z
Mirror:
http://www.4shared.com/archive/Qv0u_lWN/ubuntu.html
Mirror:
http://min.us/mZVpflpS5
Posting Back Track 5 Linux
Remember to Read the Read Me
Back Track linux Temp mirror(From My O2x Thread)
https://www.dropbox.com/s/ccf7lhfazl7li7u/btl.7z
Mirror:-
http://www.4shared.com/archive/EoGkvPD9/btl.html?refurl=d1url
NOTElease Download the file btl attached to this post and extract it on your computer and copy the btl file within and paste it in the btl directory downloaded from the above hosts replacing the old one.Now the chroot should run.
added a new Script and deleted the old one.Please use that now.I tested it personally on Stock and it is working perfectly.
As soon as it boots it asks if you wanna start VNC server?Press N and then follow the readme file.
Incase of any probs please let me know
and another
One More
Final Reserve
Nice Run..! First..
Nice work:good:
And im gonna donate [if you make mods I need]
But what is so usefull to have this??
xperiap said:
Nice work:good:
And im gonna donate [if you make mods I need]
But what is so usefull to have this??
Click to expand...
Click to collapse
A chroot image is like a Virtual Machine where you are running an O.S within an O.S.The point of this is that you have a whole Linux System running on a phone where you can ofcourse access all the utilities available in Linux.and as it runs inside of android you dont need to flash anything and can use both the chrooted O.S and Android together.check the Screenshots.
GO ahead:Try Ubuntu...it will give you a better Idea.
Hi! Have you tried this on stock kernel? I believe stock kernel doesn't have loop devices enabled and MIUI is a rebase of CM? Not sure though that's why I'm asking.
Riyal said:
Hi! Have you tried this on stock kernel? I believe stock kernel doesn't have loop devices enabled and MIUI is a rebase of CM? Not sure though that's why I'm asking.
Click to expand...
Click to collapse
The Miui i used was on Stock Kernel.The Kernel Does Support Loop devices.Miui is a Rebase of CM but the loop functionality is related to Kernel.So,Yes it Works on Stock Kernel on Locked/Unlocked Bootloaders Both as we are not flashing anything.
Anyway Give Ubuntu a go.
manasgirdhar said:
The Miui i used was on Stock Kernel.The Kernel Does Support Loop devices.Miui is a Rebase of CM but the loop functionality is related to Kernel.So,Yes it Works on Stock Kernel on Locked/Unlocked Bootloaders Both as we are not flashing anything.
Anyway Give Ubuntu a go.
Click to expand...
Click to collapse
Thanks! Just clarifying things out I haven't meddled with stock kernel that much that's why I am asking. Well the kernel sources sony provided has loop devices disabled by default glad that it's enabled on the official precompiled one.
Anyways! Try packing backtrack that should be alot useful than debian w/ lxde or a classic ubuntu image.
I got backtrack to run on Pro sometime ago when I was still using gingerbread.
Riyal said:
Thanks! Just clarifying things out I haven't meddled with stock kernel that much that's why I am asking. Well the kernel sources sony provided has loop devices disabled by default glad that it's enabled on the official precompiled one.
Anyways! Try packing backtrack that should be alot useful than debian w/ lxde or a classic ubuntu image.
I got backtrack to run on Pro sometime ago when I was still using gingerbread.
Click to expand...
Click to collapse
Already Did.Will upload it sometime Later today or tomorrow.
Debian and Ubuntu both have lxde pre-installed.
Edit:-BT5 UP.
Hi! seeing that you're a fanatic of these perhaps it would be useful if I give you these.
http://50.56.186.177/filez/
Those are packed and reduced sizes of debian & fedora arm images made to fit for chrooting on mobile devices. I made those for my previous device and is very stable already with 256mb RAM
the debian image is a squeeze version. Plus included is the fix for pulse audio. I'm not sure if it would work out of the box for android but with just a little bit knowledge with basic linux stuffs you could get it running perfectly
Riyal said:
Hi! seeing that you're a fanatic of these perhaps it would be useful if I give you these.
http://50.56.186.177/filez/
Those are packed and reduced sizes of debian & fedora arm images made to fit for chrooting on mobile devices. I made those for my previous device and is very stable already with 256mb RAM
the debian image is a squeeze version. Plus included is the fix for pulse audio. I'm not sure if it would work out of the box for android but with just a little bit knowledge with basic linux stuffs you could get it running perfectly
Click to expand...
Click to collapse
THANKS for the link...Meego wont chroot..tried it on the optimus a few months ago and failed..problem with zephyr..will give it a go later.fedora I had as well..but the thing is ...Does anyone except me even use these here????
I do but not that much. Like I said I just only tried backtrack and obviously I use it only when needed
Say do you think it would be possible to include a custom kernel on a chrooted image? It would be cool if we have backtrack here with monitor mode enabled. I think the wlan drivers/hardware of Xperia devices have the capability.
Or also try posting this thread to some other Xperia Sub forums. Arc/Pro users seem to be not very open to these kind of works. They just care on custom ROMs
In short they aren't geeky enough They aren't even that interested in dual booting.
Riyal said:
I do but not that much. Like I said I just only tried backtrack and obviously I use it only when needed
Say do you think it would be possible to include a custom kernel on a chrooted image? It would be cool if we have backtrack here with monitor mode enabled. I think the wlan drivers/hardware of Xperia devices have the capability.
Or also try posting this thread to some other Xperia Sub forums. Arc/Pro users seem to be not very open to these kind of works. They just care on custom ROMs
In short they aren't geeky enough They aren't even that interested in dual booting.
Click to expand...
Click to collapse
In theory yes its possible.but changes will have to be made to the arm kernel to chroot.when u type uname in terminal the output inside the chroot is different than the android kernel.but I think native booting will be better than chrooting..not being interested is just odd....its so much fun having linux on the go
manasgirdhar said:
A chroot image is like a Virtual Machine where you are running an O.S within an O.S.The point of this is that you have a whole Linux System running on a phone where you can ofcourse access all the utilities available in Linux.and as it runs inside of android you dont need to flash anything and can use both the chrooted O.S and Android together.check the Screenshots.
GO ahead:Try Ubuntu...it will give you a better Idea.
Click to expand...
Click to collapse
It would help a lot of people if you would put this description in the first post, or even a better description. Great work!
ameer1234567890 said:
It would help a lot of people if you would put this description in the first post, or even a better description. Great work!
Click to expand...
Click to collapse
Thanks for the advice.added to first post...not good with explanations
Riyal said:
I do but not that much. Like I said I just only tried backtrack and obviously I use it only when needed
Say do you think it would be possible to include a custom kernel on a chrooted image? It would be cool if we have backtrack here with monitor mode enabled. I think the wlan drivers/hardware of Xperia devices have the capability.
Or also try posting this thread to some other Xperia Sub forums. Arc/Pro users seem to be not very open to these kind of works. They just care on custom ROMs
In short they aren't geeky enough They aren't even that interested in dual booting.
Click to expand...
Click to collapse
Actually I know I am going to say something Off-Topic
1) People on XDA are now the people who have got a smartphone just because they can afford one and wanna make their phone look "kewl" than the others with the same device
2) People do dumb things like cross flashing kernels.. They dont even read carefully what the OP says..
3) Running linux on a phone would be the best thing.. specially on an xperia pro where you get a harware keyboard..
I would like all noobs to see this - http://forum.xda-developers.com/showpost.php?p=16682226&postcount=2441
and this - http://forum.xda-developers.com/showpost.php?p=15826094&postcount=45
Hello,
Developers, I really need help to get the ubuntu-touch port working again!
After the first release of Ubuntu-Touh I tried to port it again to our devices, but I don't get them booting. I only get a black screen. I have updated all sources on github and made the appropriate changes. You can find all relevant sources and information on my new website http://danwin.github.io/ubuntu-touch.html where I have uploaded the non-bootng builds for developers.
I still have the old builds available for those, who want a booting ubuntu-touch, but without any functionality: http://danwin.github.io/ubuntu-touch.html
it is so laggy on mini Dude :/
screenshot please
rod555 said:
screenshot please
Click to expand...
Click to collapse
there is already a video available, but I have made some Photos of my Neo V, sorry for bad quality: http://ubuntuone.com/6keWFpFBG0kEsVF7mBF54D
Can you add the screenshots in the op as pic
slimmer2 said:
Can you add the screenshots in the op as pic
Click to expand...
Click to collapse
I don't think this is really necessary, as I have a video from kakalko4 embedded there, which has a lot better quality than my screenshots. You can download the zip provided above and unzip the pictures inside, if you really want to see them.
can you make a more understandable guide how to install it because i try to follow your guide and my phone boots to kernel logo and for couple of second phone turns off
MarioJerkovic said:
can you make a more understandable guide how to install it because i try to follow your guide and my phone boots to kernel logo and for couple of second phone turns off
Click to expand...
Click to collapse
ok, updated.
You have to created an ext4 partition with CWM of another kernel or Linux and flashed then my kernel to use the ext4 partition on your SD-Card as /data, because ubuntu is to big for the internal storage. Have you really done that step?
DanWin1210 said:
ok, updated.
You have to created an ext4 partition with CWM of another kernel or Linux and flashed then my kernel to use the ext4 partition on your SD-Card as /data, because ubuntu is to big for the internal storage. Have you really done that step?
Click to expand...
Click to collapse
Yep done it and working ubuntu is working it lags a lot :/ but i dont care i am happy that we got Ubuntu on our old devices
I take it this a the same one as we already have? (crappy demo with no gsm)
replicant101 said:
I take it this a the same one as we already have? (crappy demo with no gsm)
Click to expand...
Click to collapse
For now yes, but hopefully officiallysonyrebel can make the kernel patches in one or two days available, so I can rebuild all images to make the daily builds of ubuntu booting, which have a lot of improvements.
Kernel patches related to what? I can help out. And I remember officiallysontrebel saying that he doesnt know much about kernels on the ray thread that was removed.
emwno said:
Kernel patches related to what? I can help out. And I remember officiallysontrebel saying that he doesnt know much about kernels on the ray thread that was removed.
Click to expand...
Click to collapse
The daily images of ubuntu aren't booting and officiallysonyrebel said that this is related to some kernel patches that have to be made, you can PM him and ask if you can help him with patching, so we can make the daily images also booting, which have a lot improvements in stability and usability.
DanWin1210 said:
The daily images of ubuntu aren't booting and officiallysonyrebel said that this is related to some kernel patches that have to be made, you can PM him and ask if you can help him with patching, so we can make the daily images also booting, which have a lot improvements in stability and usability.
Click to expand...
Click to collapse
thats strange.... It cant be kernel related, if you had added the new configs to the source code. It could be with the lastest CM10.1 changes for the 2011 devices. Take a look at http://github.com/cm42semc , here you will find the latest commits. I say this because if there was a problem with the Ubuntu Images, i.e something new needed to be added to get the build to boot, then it wouldn't boot on my n7100 either (as i made the same changes as prescribed on the guide). Either way its just a hunch. Give it a go.
With kernel patches, can performance be addressed?
emwno said:
thats strange.... It cant be kernel related, if you had added the new configs to the source code. It could be with the lastest CM10.1 changes for the 2011 devices. Take a look at http://github.com/cm42semc , here you will find the latest commits. I say this because if there was a problem with the Ubuntu Images, i.e something new needed to be added to get the build to boot, then it wouldn't boot on my n7100 either (as i made the same changes as prescribed on the guide). Either way its just a hunch. Give it a go.
Click to expand...
Click to collapse
I'm already using these sources and the daily images only get a black screen. A lot of other people report the same issue for their devices (not Xperia), too. You can have a lock at my changes on https://github.com/DanWin and maybe you find the mistake I made, if I made any.
replicant101 said:
With kernel patches, can performance be addressed?
Click to expand...
Click to collapse
Maybe, but the daily builds of ubuntu have a lot better performance and stability than the mwc-demo image, which is currently the only booting version.
DanWin1210 said:
I'm already using these sources and the daily images only get a black screen. A lot of other people report the same issue for their devices (not Xperia), too. You can have a lock at my changes on https://github.com/DanWin and maybe you find the mistake I made, if I made any.
Click to expand...
Click to collapse
Yes, others did have a blackscreen, even the n7100 users did. But some, including myself got it to boot.
This is what I did:
1. Wipe system / data / dalvik
2. install device part
3. install ubuntu image
NOTE: You made a new partition on the sdcard where ubuntu was to be installed. I recommend you to WIpe your sdcard, create a new partition and try again. Also try with try flashing with a different recovery / kernel then flashing the ubuntu kenrel in the end. Sometimes recoveries mess up.
Thx for the job but i had some problemes with the ARc S when i flash the Ubuntu systeme it's abortes whith the statu 0 what i have to do ?
d4k-pho3nix said:
Thx for the job but i had some problemes with the ARc S when i flash the Ubuntu systeme it's abortes whith the statu 0 what i have to do ?
Click to expand...
Click to collapse
Normally status 0 means success, can you go in CWM to advanced -> show log and enter the output of this here, maybe I can help you.
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
androiddev - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
CessnaBroon said:
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
klimtwifi - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
Click to expand...
Click to collapse
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
prkfsz said:
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
Click to expand...
Click to collapse
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
CessnaBroon said:
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
Click to expand...
Click to collapse
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
prkfsz said:
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
Click to expand...
Click to collapse
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
CessnaBroon said:
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
Click to expand...
Click to collapse
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
prkfsz said:
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
Click to expand...
Click to collapse
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
CessnaBroon said:
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
Click to expand...
Click to collapse
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
prkfsz said:
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
Click to expand...
Click to collapse
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
CessnaBroon said:
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
Click to expand...
Click to collapse
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
prkfsz said:
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
Click to expand...
Click to collapse
This should work on stock marshmallow too. I will give it a go and get back to you.
Thank you kindly!
lafinjack said:
Thank you kindly!
Click to expand...
Click to collapse
You're very welcome!
CessnaBroon said:
This should work on stock marshmallow too. I will give it a go and get back to you.
Click to expand...
Click to collapse
Sorry for delay in answering..
Unfortunatelly the error is still present. Like i said, probably a software issue.
Bit thanx anuway!
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey there! I'll take a closer look once I'm home. Speak to you then
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
CessnaBroon said:
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
Click to expand...
Click to collapse
Just an FYI...I was reluctant to start everything over again with Odin and latest Samsung firmware, so I opted to take a chance and merely 'adb push' the LineageOS and GApps that you have on your Google drive (along with some cache erasures as you suggested) and everything seemed to upgrade properly from Resurrection Remix to LineageOS 17.1
A few minor problems so far: camera doesn't work, and initial signon to the tablet with a PIN doesn't work so well (seems to take multiple attempts). In any case, now running Android 10!
These were issues that I faced too - I never found a way to fix them. Neither did the original Dev, but apparently updating to the latest webview fixes chrome crashes. PIN you need to wait 30seconds after boot. Camera works only with clean install and even then sometimes doesn't work.
Hope this helps,
Cessna
I was trying to install TWRP but after reboot when I go to the Recovery mode there is no TWRP. I installed the LOS on my Tab Pro 8.4 and wanted to install LOS on Tab S 8.4 but can't flash the TWRP. Any ideas what I'm doing wrong?
Thanks