Hi,
as the title states I am looking for an Eclair ROM for the Nexus One with SLCD support.
I tested official ROMs, though couldnt find any which supports the SLCD, which means:
I know how to flash it and the process itself worked, but the display was just off when the mobile booted up. Buttons worked but the touch display didnt.
It needs to be an Android 2.1 or 2.0 and the Hardware is also fixed: Nexus One with SLCD.
I was looking for a week now and couldnt find a suitable ROM.
Any help is welcome, thx in advance.
Cheers, stas
There is none in existence. Nexus didn't come in SLCD variant until Froyo was released.
Would it be possible to get Eclair running on the Nexus One with a homebrew linux kernel? I mean: Is the slcd driver just some kernel issue or do I need something more?
Anyone knows a way of how to make it work?
Cheers, stas
Have you seen this post?
http://blog.akisaarinen.fi/booting-android-21-in-nexus-one-with-slcd
It seems this guy was able to boot his slcd nexus one with eclair.
Sent from my Nexus One using XDA
I have seen this post and tried to use a stock eclair rom and unpack the boot.img to replace the kernel with an own one. I took the kernel config off a froyo image and build a kernel. though after repacking and flashing the device didnt boot. I could try to use a froyo kernel with slcd support in an eclair boot.img, would do it tomorrow.
Thanks, stas
I actually managed to boot up android 2.1 but couldnt get the wifi working.
Steps I did:
flash boot.img from froyo
flash system.img from eclair
that way the display was working and the phone booted up. But the wifi didnt work. After some reading I encountered that the kernel modules are located in the system.img and the kernel is as expected in boot.img. Since both are from different branches the module for the wifi didnt match the kernel. So I extracted the appropriate kernel module from froyos system.img and pushed it on the mobile. That way the wifi could be activated but still could not connect to the AP. How ever I leave it for now and try a different approach.
Thanks for your time.
You can try to take any custom kernel for Froyo, look at the files being flashed besides boot.img, grab all those files from Eclair ROM and flash them on Froyo ROM. This way you'll get most of the functionality in the kernel.
Related
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
thoughtlesskyle said:
so i have a custom build over in the vogue forums but i would love to get it working on the hero, it is basically just a heavily customized version of AOSP so i took asop mod as a base and added my custom changes to it (that part i got) i then signed it and attempted to flash it to my hero, it got about half way through the installation and said i was missing and update script so if anybody can give me advice that would be awesome i would really love to get this build running on my daily phone.
Click to expand...
Click to collapse
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
unCoRrUpTeD said:
When you unzipped the ROM you should have seen some folders and a boot.img. There are some folders in the boot.img that need to be replaced along with the kernel for our phone. So just using a boot.img from another ROM might be the easiest. Otherwise you will have to unpack it, switch out files and repack with a kernel for our phone.
The update script is found in /META-INF/com/google/android/. You should be able to pull it from another ROM.
Click to expand...
Click to collapse
ah i deleted the meta-inf folder thats probably what cause the problem
also am i able to have a folder that keeps things in /data like i am on the vogue or does it all have to be in the system?
I am using a rooted nook color happily except for one detail. Does anyone out there know how to get the VPN support to function?
I tried upgrading to 1.1 and re-rooting, and i tried installing the updated kernel. Neither seems to affect the VPN settings. I also installed wi-fi buddy and in that app I see all of the advanced VPN related settings but they are grayed out.
Dies anyone have any suggestions, I am new to the tablet, but familiar with embedded linux.
Sent from my LogicPD Zoom2 using XDA App
Sorry, that's stock v1.1 firmware. Used autonooter to root, installed Dalingren's overclock kernel with MPPE support.
Forgot all the details.
Sent from my LogicPD Zoom2 using XDA App
I have the same question. Thanks. Does the overclock kernel keep the rest stock? Do you have the link to the post, I have only seen the other overclock.
I used the latest eclair kernel Dalingrin had at the time. It looks like he just released another one with von related changes. I will try that tomorrow and see if it helps..
The kernels can be found on xda search for dalingrin kernel and it should come up
Warning, installing kernels could brick the device requiring a factory reset. I don't recommend it until the von issue is really fixed. I ran into a number of problems doing this. One to be very aware of is that CWR rom recovery does not seem to be compatible with the nookcolor at this time. If you install RomManager Do Not flash CWR or you will end up with a boot loop.
That issue made me so leery of that package that I actually used the terminal emulator and command line to mount the boot volume and manually update the kernel image and its modules.. That is the only method I can directly confirm, I did not use RomManager to flash the kernel..
If you are really intersted in keeping everything stock but the kernel, the closest way I can think of to do that would be to use an sdcard image including car/rommanager. I believe you can put the flashable kernel on the sdcard and then flash the kernel onto the stock firmware that way.
I have not tried that, but I see no reason why it wouldn't work.
That would avoid the terminal and the jiggery-pokery with mkimage and remounting volumes manually. It's actually not very hard, but it is certainly more error prone, and it's all linux command line work.
Can anyone confirm that flashing the eclair kernel on stock rom is 'safe' ??
no eclair 3-8-2011 available yet
I was hoping to test the new kernel today, but there is no eclair build yet. From the traffic on that thread it looks like they are struggling with a wi-fi issue at the moment.
I think I remember reading somewhere that you can dual-boot gingerbread and froyo (I could be totally wrong so please forgive me if I am) My understanding was once both where installed you could just change kernels to change the OS. Is this possible?
I am running CM7 but I still would love to play around with the other froyo builds people are putting out. However because it is not as simple as just simply booting into recovery flashing a new ROM I am less prone to doing so. (I usually download and flash the ROM's while i'm on the go. Don't usually have a computer near me to use ODIN and such)
Thanks in advance
There was a CM7 build a ways back that was psuedo-dual boot. Once you flashed the ROM and were on 2.3, if you ODIN'd over a 2.2 Kernel, it would boot back into Froyo. If you ODIN'd over the 2.3 kernel, it would boot back into Ginger. Pretty sure it's not possible to do that with the current CM7 build that's being worked on.
Thanks for responding. Its too bad, I don't want to go backwards but they do amazing work on these forums
geokhentix said:
There was a CM7 build a ways back that was psuedo-dual boot. Once you flashed the ROM and were on 2.3, if you ODIN'd over a 2.2 Kernel, it would boot back into Froyo. If you ODIN'd over the 2.3 kernel, it would boot back into Ginger. Pretty sure it's not possible to do that with the current CM7 build that's being worked on.
Click to expand...
Click to collapse
CM, DG, Team Phoenix, Supercurio (and everyone else) thank you all for the freedom
I have searched thoroughly through the various CWM and OC Kernel threads but it's not clear to me if I can achieve having ClockworkMod Recovery and an Overclocked Kernel running on a Sprint (CDMA) Tab without any issues with the GPS or Camera.
I am perfectly fine running the stock Samsung ROM, but want to be able to overclock to 1.4GHz and be able to run CWM so that I can at least be able to do nandroid backups. From what I gather some of these CWM solutions and OC kernels (which may be really designed for Verizon Tabs and not Sprint Tabs) may cause issues with the GPS and/or Camera. I cannot afford to lose those two functions of the Tab.
So for those Sprint owners out there, what has worked for you to get a working CWM and OC kernel without sacrificing the GPS and Camera? Thanks!
apparently this isn't possible? it's a shame...as if a CDMA Tab were bad enough, it looks like the Sprint one is the true ugly stepchild of the bunch.
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
ad720 said:
The VooDoo CDMA Kernel that I just flashed appears to have a working FF and RF camera as well as working GPS.
I'm pretty new to the SGS scene so I may not be talking about the same thing you are.
Click to expand...
Click to collapse
Awesome! So you are using a Sprint Tab? And you can run Google Maps or Navigation and it locks your location using GPS? I just want to be sure before I proceed down this path, since I've read about some users not being able to get their GPS to operate once they've borked it.
And if you don't mind me asking, how did you get the VooDoo CDMA Kernel on there? Did you first install v4 through SGS Kernel Flasher or perhaps Heimdall? And then you installed v5 through CWM?
Thanks!
Yes, Sprint Tab (I just got it from the most recent woot sale).
Google Maps locked to my location within 20 meters inside of my office, and then dead on my front door just now. I turned my WIFI off to make sure it was really the GPS. I started up Navagation and it showed waiting for GPS for a about 2 seconds before starting with the turn by turn.
I have taken pictures with the RF and FF camera but I haven't tried a video chat so that might not work. When I take a picture the preview does glitch out on the screen a bit but the picture is just fine.
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
The issue that I had was my auto-rotation wasn't working. I found the file to replace in the thread but root explorer wasn't recognizing my SD card until I turned off the VooDoo enhancements in CWM and then turned them back on as specified by the troubleshooting section of the OP. At that time I was able to replace the file to restore auto-rotate.
Please keep in mind that while I am not new to Android I am quite new to the SGS so do plenty of reading and keep in mind that this is just my experience (or inexperience) with it and I may just have gotten lucky.
Also, I do NOT have data services through Sprint, I am using WIFI only so I can't speak to the effects of the Kernel on that.
Good luck!
Thats pretty awesome, atleast we have an alternative until Samsung hopefully release the 3.34 for all G tab owners.
ad720 said:
I flashed the latest version directly through SGS Kernal Flasher. I don't have the files in front of me but I just followed the directions in the OP.
Click to expand...
Click to collapse
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
onlinespending said:
Thanks again. This is really helpful. But from what I understand the latest version (v5) is only updatable through CWM. v4 can be flashed through SGS Kernel Flasher. Is it possible you're not running v5?
Click to expand...
Click to collapse
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
ad720 said:
Correct. I'm looking at the files now and I used SGS Flasher to do the v4 (step 1) and then CWM to do the v5.zip (step 2). If there is a way to verify which Kernel, let me know and I'll double check.
Click to expand...
Click to collapse
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
onlinespending said:
Hmm, for some reason I cannot get v4 flashed using either SGS Flasher or Heimdall. I first got the latest OTA update (build EB28) before doing this however, so I'm not sure if that is an issue. Can you confirm you were or are on build EB28 (under Settings -> About My Galaxy Tab)?
Click to expand...
Click to collapse
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
ad720 said:
I can confirm that I am currently on EB28. Not sure if it was different before the Kernel flash. I got two OTAs before I even really started to play with the Tab...
Where are you running into a problem? Does SGS not run?
Click to expand...
Click to collapse
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
The first OTA on my device is downloaded, but not installed, and I'm curious if I should even take them at all?
I currently have the following:
Hardware version: SPH-P100.08
Model number: SPH-P100
Firmware version: 2.2
Baseband version: S100.08 S.DJ29
Kernel version: 2.6.32.9
Build number: SPH-P100.DJ30
I'd like some type of recovery and eventually HC... boy these Sprint tabs, and tabs in general, are funky compared to my Incredible.
onlinespending said:
Sounds like you had EB28 even before you did the flash. SGS runs fine. It says the kernel flashed successfully, but upon reboot the Tab is just stuck at the Samsung boot screen. I cannot even enter Recovery (using Vol Up + Power).
I've reverted to stock and have tried a few times all with the same result (even tried Heimdall and Odin).
There has to be something different between our Tabs that would cause the issue I'm seeing.
After the EB28 update, I have the following:
Hardware version: P100.08
Firmware version: 2.2.1
Baseband version: S100.08 S.EB28
Kernel version: 2.6.32.9
Build number: SPH-P100.EB28
Unless you have something different in one of the above, I'm at a bit of a loss. I may need to go some alternative route.
Click to expand...
Click to collapse
That is identical to mine.
I wish I knew more about the tab so I could be a help.
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
onlinespending said:
Well seems like I solved my problem. Not entirely sure why, but when I swapped in a small 1GB sdcard I was able to flash this Kernel without issue. Using the 16GB card that came with the Sprint Tab didn't work.
Click to expand...
Click to collapse
Maybe a format issue? That's interesting...
I had a similar issue with the 16gb card. put a 2gb card in, and was able to flash the kernel and then get into CWM. sadly once I got that far it didn't seem to matter what rom/kernel i tried it wouldn't boot past the samsung logo anymore. So back to stock rooted for now I guess.. Really want to play with the HC port, but not sure why it won't work. Also can't seem to get Heimdall to recognize my Tab, Odin works fine however.
another new Sprint SGT owner from Woot sale here. Also just flashed the Voodoo OC kernel last night, all seems well camera and GPS etc, I have no idea if 3g works as there is no Sprint in my state.
I flash the V5 using a guide I found over on the unlocker site. took several tries before I got it to go, lots of command line stuff and I think I had a few typos along the way.
Another woot sprint tab user here... I also have "KhasMek Voodoo Plus v5" installed on my tab but GPS does not work for me. Well, it has never worked for me even with stock kernel and EA24 ROM.
Any other woot user with a none working GPS straight out of box?
Update: GPS will not lock if Sprint tab is in airplane mode. Even though by the window works for my HTC hero phone but not the tab. It needs to be outdoor in order to get proper GPS signal.
I can't seem to find the answer - I've purchased the VZW Tab Bootstrapper, which at this point only seems to brick my tab - after Heimdalling, I installed Oldmacnut's Rooted Gingerbread Rom - ROM Manager says that CWR 3.0 is installed - if I push flash new recovery, the only devices i can select from are Galaxy i900 - assuming that the rom was built from this device - so, what do i need to do to get clockwork properly installed? If i volume up/power up, I get stock recovery - if I use ROM Manager, it gives me the triangle with a progress bar for a second or two, then reboots - don't want to reboot with the bootstrapper program again, as i don't want to re-brick my tab - unless I'm crazy, there doesn't seem to be an easy solution - am I crazy and/or blind? There seems to be a possible kernal solution, but I have to flash it, and I can't flash it if i can't get clockwork recovery going - i think. help....
yeah, all the bootstrappers only work for Froyo.
I released a CWM + EXT4 kernel with V1 of my Gingerbread roms, only the kernel doesnt have 3G.
I also started on a new kernel for both, 3G being an issue when i ran head first into CM7 for the tabs.
I then decided to hold off on the kernels as i was building a kernel for CM7, I thought I could release a new one.
Now, last night I thought about making a thread with all forms of "recovery" from Froyo to GB for people who need to reflash a tab back to stock, and offer a bone stock version, and a rooted version. I just need to finish uploading the remaining roms to my server for hosting before i can post it all.
I thought of this as alot of people ask where they can find X rom or X kernel, which is why i started on that mirror.
No reason to flame, the issue of CWM for GB and the bootstrappers have never been addressed publicly
Is there a way to stay on rfs with your cwm kernal you posted?
oldmacnut said:
yeah, all the bootstrappers only work for Froyo.
I released a CWM + EXT4 kernel with V1 of my Gingerbread roms, only the kernel doesnt have 3G.
I also started on a new kernel for both, 3G being an issue when i ran head first into CM7 for the tabs.
I then decided to hold off on the kernels as i was building a kernel for CM7, I thought I could release a new one.
Now, last night I thought about making a thread with all forms of "recovery" from Froyo to GB for people who need to reflash a tab back to stock, and offer a bone stock version, and a rooted version. I just need to finish uploading the remaining roms to my server for hosting before i can post it all.
I thought of this as alot of people ask where they can find X rom or X kernel, which is why i started on that mirror.
No reason to flame, the issue of CWM for GB and the bootstrappers have never been addressed publicly
Click to expand...
Click to collapse
Thanks - at least I know I'm not nuts - I honestly don't know that it's necessary to mess with the kernal that's in the GB rom you compiled - it works great as is - I'm just so used to flashing stuff through Clockwork from all the android phones I've had - new to the samsung/tab world, trying to get myself up to speed -
Thanks again for getting back to me, and please, PLEASE take care of yourself and family - this android world is supposed to be fun, not just for us that take advantage of the work that devs like yourself put in, but fun for the devs too - now put your feet up, pour yourself something cold, and watch some football.
Just make sure to have all the ROM's you started finished by morning...
My name is Jack, and I'm a romaholic.
Here is the thread you need to read first..
http://forum.xda-developers.com/showthread.php?t=1099036
TheATHEiST said:
Here is the thread you need to read first..
http://forum.xda-developers.com/showthread.php?t=1099036
Click to expand...
Click to collapse
Oops - copy that - thanks for the heads up.
Thread moved to Galaxy Tab Q&A.
Oldmacmnut,
I can't seem to get Heimdall working (or USB at all, for that matter) on my Tab. I have root, and I can reboot into recovery, although it isn't CWM recovery. I tend to believe that the problem is in a corrupt ROM install of some sort, and would like to either flash a stock ROM to get back to square 1 or a rooted ROM. Problem is, I think I need to figure out a way to do that through recovery as USB doesn't seem to work at all on any computer that I have tried. If you have a CWM Recovery that works, is it flashable in the stock recovery?
Thanks,
Seth