I really need to get the right drivers for the Iconia A100 and i need um soon. I searched alot and there all dead links or ads now.
I just attempted to port a 4.1.2 rom from another tab, I get past the install and sit at the boot animation, no damn adb cause i did a reinstall on the computer and they got lost in the hundreds of zip files in my downloads.. And I cant get a logcat, I know I can get this booting and its freaking sweet. Its based on pio_masaki's Jellytime Final, and a mixture of ParanoidAndroid Roms. If i get it going its getting posted. Anyone wanna help on the testing just ask here or pm me.
Thanks in Advance.
I do need an xml person, I hate them ....:silly:
Try the Acer support site?
Sent from my Galaxy Nexus using Tapatalk 2
Sure did...
The ones I got from them didn't work for some reason. I found a thread on here that's got a naked usb driver that worked just fine. I am waiting for cygwin to install to unpack and compare boot.img from your SoseiB3 Final to the rom I ported from, Then its off to recovery and some logcating to see if I can get it to boot. did this once today and I failed. I went about this build from another angle and I think this should boot. I'm not to good at logcat reading but I hope I dont need to read to much. I'm about 30 minutes from a signed update to test. Then hopefully I can post my rom. If i can find a mirror to use that is lol. I'm new can you tell?
I have successfully ported roms before without building from source. If you post some logcats I might be able to help with what might be causing to boot to fail.
Most of the things I had to do to make it work were transferring lib files and doing some modifications to framework.jar
hardslog said:
I have successfully ported roms before without building from source. If you post some logcats I might be able to help with what might be causing to boot to fail.
Most of the things I had to do to make it work were transferring lib files and doing some modifications to framework.jar
Click to expand...
Click to collapse
Its uploaded to dev host, the links below. if you would like to download it and see what you think then feel free. Just be aware I have not even tried this build out yet. Nothing to worry about really but it may be way far from booting. Its fresh out the winrar folders lol.
link d-h.st/i5U
I have built and slightly tweeked CM 10.1 but to be honest, it does drain that battery quite a bit and sometimes it freezes in landscape mode.
So I sync'ed up the source for the AOSP and then I realized that I needed binaries and I don't have the stock ROM to extract them from.
Are these "Galaxy Nexus (Sprint) binaries for Android master (20130603)" the right binaries for SPH-l710 ?
Under the Toroplus section at the very bottom of this page https://developers.google.com/android/nexus/drivers
Basically I just want try moding from stock because of the battery thing, I need to add Arduino support and maybe tweek USB or write an app, so that my phone can hook up over usb to an Arduino board and chit chat. I want the Arduino to control motors while Android gathers sensor data and decides where to go, Arduido will just follow orders. Anyways, battery consumption is huge in this project.
EDIT-1: Also, what version of Android are the 20130603 binaries for?
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
CNexus said:
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
Click to expand...
Click to collapse
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Edge-Case said:
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Click to expand...
Click to collapse
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
CNexus said:
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
Click to expand...
Click to collapse
Makes Sense.
So if I am learning anything... I would need binaries ("blobs"), I am sure Sprint, Google, and Samsung proprietary apps, and the nessiccary make (Android.mk) files, maybe some kernel patches and/or kernel object files, and hopeful to all hell I don't have to do too much XML modification I need to go find a trust-worth factory zip for the sph-l710 and rip everything I need out of that, and the bootloader I need to get it all back to stock eventually in case kit-kat does get updated by the Samsung (I am guessing thats whose hands it is in, I think they have a counter), who knows maybe the open source community will get there first.
Thanks for your help, saved me a ton of hassle.
Hello all, I haven't been here for about 2 years, got busy with some things. I'm currently running a home compiled JSS15Q that has a touchscreen hack to load in the firmware that works best with my tablet. I'd like to build 5.1.1 LMY48I from source and give it a try. Do I need to upgrade any bootloaders or other stuff before attempting to push the new OS on there?
It's been 2 years since I did any of this stuff so I'm a bit foggy about it all. I had a good handle on it back then, but I've slept a lot since then. I might go with sfhub's locked in firmware this time since I was accomplishing pretty much the same thing just a different way. That's, of course, assuming that the old firmware is compatible with the newer releases of Android OS.
I built the older release in a VirtualBox VM running Ubuntu 12.04. I think I need to upgrade some things to be sure that the compile of 5.1.1 works as it should. I was about out of space on the 12.04 VM and I was going to grow the partition, but I'm thinking it might be smarter to just follow the build-from-source instructions from scratch in a new VM install. It takes a huge amount of space to do a build. AOSP took 20GB and JSS15Q took about 40GB of drive space. I "only" set up a 100GB VM which means I likely don't have enough room to download the newer release source.
If anyone that's done this has any advice, I'd sure appreciate hearing it. Thanks for reading.
Sounds like you already have it figured out.
There is a new bootloader so don't forget that. Sfhubs firmwares work fine.
I forget how big it was when I synced 5.1.1 but if you delete the jellybean code you should be fine.
LOL You're giving me wayyyy too much credit. I'm pretty much stumbling around in the dark here. I went with the new VM using Ubuntu 14.04. I struggled through all the apt-get commands especially the one with libgl1-mesa-glx:i386. It just didn't want to install because of some dependency quirk of some sort with something called cheese. I finally found a solution by doing this:
sudo apt-get install libglew-dev libcheese7 libcheese-gtk23 libclutter-gst-2.0-0 libcogl15 libclutter-gtk-1.0-0 libclutter-1.0-0 xserver-xorg-input-all
God only knows why I had to do all that to get the libgl-mesa-glx installed, but it finally let me do the get for libgl-mesa-glx:i386. Then I could finally create the symlink for the mesa library. After that, I successfully repo synced the source tree; it took up 35GB of disk space. I did the lunch command, picked flo user (11) and started my make command to build. That's running right now.
I was concerned about the proprietary binaries for the broadcomm stuff, but I found a directory under ./device/asus/flo called self-extractors. I'm guessing that stuff takes care of itself now and you don't have to do the steps of finding, downloading and extracting it into the tree. That's my guess anyway. I'm following this "howto":
http://source.android.com/source/requirements.html
I had been looking at an older one on blogspot, but it was for a different device and I figured it would be better to follow the one I'm using instead since it seems more current. I hope this build works okay and doesn't drag badly from bloat. I like my tablet's responsiveness on jellybean. I'm wondering now if I shouldn't have just gone to kitkat instead of all the way to lollipop. Oh well, live and learn. Thanks again for you input and for reading this. Let me know if I'm messing up.
I got it compiled. It took about 2.5 hours. I tried to find the program that I modified before, but I can't find it anywhere in the source tree. They've apparently moved everything around real good. If anyone knows where the touchscreen firmware update takes place, I'd appreciate knowing. It used to be in a program named ektf3k.c That program no longer exists in the build. I can use sfhub's utility to lock in the firmware I need, but I'd still like to know how where they moved the firmware update stuff.
afremont said:
I got it compiled. It took about 2.5 hours. I tried to find the program that I modified before, but I can't find it anywhere in the source tree. They've apparently moved everything around real good. If anyone knows where the touchscreen firmware update takes place, I'd appreciate knowing. It used to be in a program named ektf3k.c That program no longer exists in the build. I can use sfhub's utility to lock in the firmware I need, but I'd still like to know how where they moved the firmware update stuff.
Click to expand...
Click to collapse
I built the whole thing without the proprietary binaries installed. I'm guessing that my build is basically useless. I'm kinda disappointed that they don't bring up the binaries until after they walk you through the lengthy compile process. I guess I have to do a make clobber, unpack the binaries and then do the whole build over again. The build went fine as far as I can tell.
Can anyone verify if I have to do it all over with the binaries unpacked? I'm afraid to try flashing the stuff I built just to see what happens. Would there be any harm in that?
I was wondering if someone could help me. I've been playing around with flashing roms and basic stuff for a long time, but I figured I'd like to play around with kernel building, and just generally trying to learn about android/linux/java more. So far the only kernels I've successfully built were for the 6P just because I tried it following google's source website. I've been trying to just see if I could build a stock kernel for the 10, so I could see if I could actually flash it. My builds always fail at the same places, so I tried cloning the repositories of flar2 and tbalden just to see if I could make their kernels and my build fails on the same. Looking at source codes from other devices such as the OnePlus3 I see that it's basically the same, and so I tried building that and it fails exactly for me at the same areas as well.
I'm using an older 2012? Core-i5 laptop that I had laying around, installed Ubuntu 16.04 LTS. I got the newest android NDK, put the path into .bashrc so I could just use CROSS_COMPILE=aarch64-linux-android- without having to type out the full path every time. I'm wondering if there's just something wrong with my build environment and I need to start over? I see all these tutorials, but they're all old and usually covering older 32-bit kernels. They mention all the variations of using sudo apt-get install, followed by a bunch of various packages. So I'm wondering if these are older packages conflicting with something? Does anyone happen to have any guidance on this. I just want to get setup and be able to build a single HTC 10 kernel and then go from there.
duowing said:
I was wondering if someone could help me. I've been playing around with flashing roms and basic stuff for a long time, but I figured I'd like to play around with kernel building, and just generally trying to learn about android/linux/java more. So far the only kernels I've successfully built were for the 6P just because I tried it following google's source website. I've been trying to just see if I could build a stock kernel for the 10, so I could see if I could actually flash it. My builds always fail at the same places, so I tried cloning the repositories of flar2 and tbalden just to see if I could make their kernels and my build fails on the same. Looking at source codes from other devices such as the OnePlus3 I see that it's basically the same, and so I tried building that and it fails exactly for me at the same areas as well.
I'm using an older 2012? Core-i5 laptop that I had laying around, installed Ubuntu 16.04 LTS. I got the newest android NDK, put the path into .bashrc so I could just use CROSS_COMPILE=aarch64-linux-android- without having to type out the full path every time. I'm wondering if there's just something wrong with my build environment and I need to start over? I see all these tutorials, but they're all old and usually covering older 32-bit kernels. They mention all the variations of using sudo apt-get install, followed by a bunch of various packages. So I'm wondering if these are older packages conflicting with something? Does anyone happen to have any guidance on this. I just want to get setup and be able to build a single HTC 10 kernel and then go from there.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1748297
Here you go
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
So, building asteroids and syncing with latest sources and also trying to fix bluetooth is my main goal here.
First test build is complete! Link: [urlhttp://www.mediafire.com/?0c0xusva0z5e0[/url]
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/asteroid-image-tetra.ext4 /sdcard/linux/rootfs.ext4 (pushes the file to the virtual sdcard)
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/zImage-dtb-tetra.fastboot
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
amunarjoh said:
Hi
I'm always open for some beta testing. In what direction of development where you thinking? A themed stock, or something radical?
Click to expand...
Click to collapse
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
RAZERZDAHACKER said:
I have this device, but right now I am unable to root and twrp it because of warranty but I really want to build a ROM for it and we have the sources so I really want to do it. Any beta testers would be frickin amazing.
Please, either send me a pm or write here on this thread and I'll try to release a flashable zip asap
Click to expand...
Click to collapse
I am willing to be a beta tester
Alright, stay tuned. Building rom right now, also getting instructions for how to flash it (I don't think it is a simple twrp flash, not sure, we need some tester to confirm that).
RAZERZDAHACKER said:
Not themed stock, sure they're great for some people but I am not a huge fan of them so I will obviously not make one. Right now I am compiling resurrection remix for my phone but I might try later on and get a compiled version
Click to expand...
Click to collapse
That sounds interesting. Looking forward to further development
Build finished after a couple of hours. Since I am new to this whole android wear thing, I am a bit confused as to which files to flash, but I assume it is the one that is the largest and has the correct file format, right? So here is where the beta tester thingy comes into place. I am still experimenting on flashing the rom (the flashing method can be a bit confusing for new people) so I am planning on coding a toolkit that does all of that for ya, but the main thing is that I use linux and I don't really have a windows machine available to test this and quickly be able to change some things in the code (or either the rom files and then pack em up) so if someone is willing to perhaps skype or something similar where they can test such things that would be amazing, since I don't believe that a lot of people are running linux and want to flash this particular rom for this particular device etc.
Enough ranting! Here comes the rom link! http://www.mediafire.com/?0c0xusva0z5e0
That is the link to a folder containing 2 files, an ext4 file and a fastboot file.
To flash it, make sure your bootloader is unlocked
This will only dual boot the software, because it is just a test and in case it'd mess anything up, it won't affect the watch.
Once you've downloaded the files and put them into your adb and fastboot folder, enable adb debugging (obviously huehuehue).
Once that is all done, don't switch off your watch, leave it in android wear and make sure that adb detects it (adb devices and it should say authorized next to it).
Run adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext4
Once that is done, reboot to bootloader by running adb reboot bootloader.
Then, once you've sure made that fastboot recognizes it (fastboot devices), do fastboot boot /location/to/file.fastboot.
If you want to try and overwrite your current android wear installation, do fastboot flash, however I don't recommend this.
Good luck! Oh, and as a sidenote, since this isn't android wear, the android wear app won't work and I am surprised that bluetooth even works (if it does, report it here!).
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
niai_mack said:
Doesn't boot for me get stuck at the Smartwatch 3 screen then reboots in to wear.
Click to expand...
Click to collapse
Thanks for trying, and you followed the instructions here I assume. I'll try to compile a new one today (I got some interesting warnings when compiling)
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
niai_mack said:
Aye I followed to the tea, put it in /sdcard/linux/ with the name rootfs.ext4 then booted with the supplied fastboot file.
Click to expand...
Click to collapse
Can you perhaps try "adb push -p /location/to/file/rootfs.ext4 /sdcard/linux/rootfs.ext2" ? Thanks.
I can test as well
d_crossfader said:
I can test as well
Click to expand...
Click to collapse
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
drakonizer said:
You do know there's the official release from the dev of Asteroid OS that works without any issues (meaning it boots and functions as expected, minus the bugs), right? In case you didn't, here it is: https://asteroidos.org/install/
I get that you're trying to do something new, and I'm all for it. I'm just posting this here, in case anyone else was curious. It's been out for quite a while now, almost a year by my reckoning.
Bluetooth does not work though, blame Broadcom.
Some extra info. When you fastboot boot the kernel from Asteroid OS, it loads the system that you earlier pushed to your internal memory using adb. You can run the (barebones) OS till your next reboot. Once you reboot, you'll be taken back to Android Wear itself, and you have to reflash the kernel to go back to Asteroid.
Click to expand...
Click to collapse
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
RAZERZDAHACKER said:
Missed your reply. Correct, and I am aware of that. Just that I want to get into android wear development so I decided to build this from source and perhaps eliminate the bluetooth thing and maybe even have it as a permanent rom instead of android wear, just saying. It'd be pretty cool, though not the most practical thing ever.
Click to expand...
Click to collapse
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
drakonizer said:
Having it permanent is easy. All you'd have to do is fastboot flash the kernel as opposed to fastboot boot.
The Bluetooth thing is almost impossible to fix, it's due to the blobs from bcm. Unless you're proficient at reverse engineering complex code, it's pretty hard.
Click to expand...
Click to collapse
I can always try :/
RAZERZDAHACKER said:
Sweet, I assume you pretty much know what to do. Can you also test the above mentioned flashing method? So you're replacing the vritual sdcard with ext2 instead of 4.
Click to expand...
Click to collapse
I can do the steps on the first page, not sure about replacing the virtual sd though
d_crossfader said:
I can do the steps on the first page, not sure about replacing the virtual sd though
Click to expand...
Click to collapse
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
RAZERZDAHACKER said:
What you're doing on the first page is basically moving the files and flashing them from the virtual sd card so all I ask is if it doesn't work to change the last number in the adb command from a 4 to a 2
Click to expand...
Click to collapse
cool, will try in a few