SD Card/USB wont mount.. - Android Q&A, Help & Troubleshooting

I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?

TDJ512 said:
I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?
Click to expand...
Click to collapse
I think it might be the kernel because i know certain issues from older versions of the skyhigh kernel for the sgs+ wich occured the errors u are stating in here....
so take into consideration to check the kernel
thats all i know about this topic

Thanks for responding, but what aspect of the kernel. I'm not so kernel savy so lame terms if you will, thanks.

TDJ512 said:
Thanks for responding, but what aspect of the kernel. I'm not so kernel savy so lame terms if you will, thanks.
Click to expand...
Click to collapse
yea...im not a kernel pro too but i think i know a method to find out..
go to this thread and check the kernel sources on github
the kernel has one version wich is called 1.4 and one called 1.4d check the changelog in the thread cus the author stated that he fixed the issues in the 1.4d version so i think if you compare the sources of the 2 kernel u might find out whats wrong with yours
http://forum.xda-developers.com/showthread.php?t=1555431
heres the thread

TDJ512 said:
I've looked around and haven't found anything that comes close to the answers I'm searching for so I figured this would be a good place as any to ask, sorry in advance if this isn't the proper place.
I ported 2 ROM's from a device (Desire Z to the EVO Shift) I got the ROM'S nearly fully functional. However, on both ROM's which one is a Sense 3.5 ROM and the others a Sense 4.0 ROM, both ROM's using different kernels come back with the same USB/SD Card mount issues. I'm not sure if its kernel related or what, anybody have any suggestions to fix these issues?
Click to expand...
Click to collapse
A little more information would be helpful. What does the logs tell you? Either udev does not recognise the sdcard device, or vold does not like it. Do you get the device nodes? Does vold log anything? Is the sdcard properly initialised? Does it mount in a unmodified phone? Can you mount it manually? Does it contain more the four partitions (vold handles no more by default)?

The SD Card mounts fine on builds originally intended for the Shift. Its just with cross ports from Desire Z/G2 these issues are arising. When I attempt to initialize the USB the charge feature activates, but the PCSC.apk (I believe) doesn't pop up with the options to charge/mount, it couldn't mount the SD Card anyhow if that feature would initialize because its not reading that there's anything to mount. I'm thinking this issue is more along the lines of file issues then a kernel issue. Give or take I follow the principles of this guide http://forum.xda-developers.com/showthread.php?t=1222746 with a bit of common sense there after. What could I be missing? See, I also thought maybe it was a kernel issue initially. So I ported a few more ROM's from the Desire Z/G2, builds ranging from Gingerbread 2.3.5 (CM7/Sense 3.5) to 4.0.4 (CM9/Sense 4.0), of course while using proper kernel's intended to boot the builds that are proven to function accurately on the Shift & all of them came back with a usb/sd card mount issue.

Related

[MOD] I9100 ROM Hellraiser for I777 (Alpha 0.3.1, 12/3/2011) [BUGS/DEV ONLY]

This thread is now for bug reports/development only. Do not post in this thread any more until you have fully read the first four posts of this thread, and the first two posts of the Q&A Thread. If you post in this thread and it is clear that you have not read the posts indicated above, your post will be reported. For other discussion and "Is this a bug?" type questions, go to the Q&A Thread
Heeeeere we go! As LinuxBozo, one of the most talented developers in the Infuse community said, "Welcome to a new and sick, twisted world!"
Over in the Infuse community, we had an oddball device that had little in common with anything else. As a result, it was not easy to port ROMs from the I9000/Captivate. However, after LOTS of work, LinuxBozo pulled it off and came up with an automatic porting package that could get most I9000/Captivate ROMs running on the Infuse. As a result, it opened the Infuse community up to a massive variety of ROMs.
For the month since the I777 came out, people keep asking about I9100 ROMs. In general, the answer has been, "It should be possible, but no one other than designgears has done it yet." - I didn't have the time as I had too much kernel work to do. However, as the kernel is at a fairly mature and stable state, when someone asked for SensatioN to be ported, I figured it was time for a challenge.
I was successful, but encountered a few glitches. Tethering was broken, fortunately the Infuse community had the same issue and the same fix worked. Mic in calls was broken, just like CM7 - I finally got atinm's list of the blobs to swap out. As a result, nearly all of the challenges in porting an I9100 ROM to the I777 have been identified.
This is a package that should automatically port most I9100 ROMs to the I777. It has been tested by myself as follows:
SensatioN 1.8 by Crysis21 has been manually "Hellraised", and was the basis on which this package was developed. Do note that the author of this ROM tends to be unresponsive to porters. I asked for permission to release a ported ROM but never heard back.
VillainROM 3.0 was the first ROM to be tested with the attached package - it seems to work, if there are any problems, it is likely because I missed something in the permissions settings of the updater script. - Also, I have tested JKay's Deluxe Themes on VillainROM successfully - his thread is at http://forum.xda-developers.com/showthread.php?t=1154278 - You need to use the XXKI3 theme packages.
In general, XXKI3-based ROMs work. XXKI4-based ROMs may have issues with WiFi (see Known Issues below). I am working on compiling a more complete list in the Q&A Thread.
Please don't report bugs with ROMs to the upstream author of the ROM in the event that the bug was caused by Hellraising - unfortunately, it is going to be very difficult to identify when Hellraising caused a bug and when the ROM itself has a bug.
Instructions for the package:
Download an I9100 ROM to be Hellraised - must be CWM-flashable Gingerbread (ICS will NOT happen until after kernel source code becomes available, and if you spam me with 10000 "did you see this" links when it does I'll just go watch some TV. You have been warned.), and must be Samsung-derived (not CM7/MIUI/AOSP-based), ROMs distributed as Odin .tar files like Litening won't work. (I've tried...)
Download the package above
Unzip the ROM, check to make sure it does not have bootloaders. If it has Sbl.bin or param.lfs in it, RUN AWAY. No ROM developer should EVER include a bootloader without explicit warnings of this, if a ROM includes a bootloader it's a sign that it'll be **** in almost all cases. Similarly, param.lfs corruption can lead to a device that won't boot and I believe it can even break download mode. ROMs shouldn't be messing with this either without warning users.
Once you've done your safety check, put the ROM zip and the Hellraiser zip onto your SD card
Enter CWM
You should probably do a Nandroid backup here...
Wipe Data/Factory Reset - Some ROMs write apps to /data and you'll lose these if you wipe afterwards
Flash the ROM, DO NOT REBOOT, STAY IN CWM
Flash the Hellraiser package
Reboot and enjoy!
Known issues:
NFC files are included, but enabling NFC requires smali modifications to Settings.apk on some ROMs. (Starting to look like this is only for I777 stock-derived ROMs - VillainROM doesn't actually need any smali.)
Touching an NFC tag containing NDEF data will cause the NFC service to crash due to being unable to obtain STOP_APP_SWITCH permissions
Wifi tethering settings are not persistent and keep resetting themselves (At least on SensatioN and VillainROM) - Workaround for now: Enable tethering, THEN set the SSID and password, OR see http://forum.xda-developers.com/showthread.php?t=1335377&page=24
When initially setting up the ROM, it claims that network time is not available, and takes you to Settings - where you can check it to enable it and it works fine... Infuse Hellraiser had the same issue. Happens only once per flash so it's a very low priority.
When flashing other ROMs that do device compatibility checks (such as CM7), they will think you have an I9100 instead of I777. You need to flash an I777 ROM first.
Download links have been moved to the ChangeLog post (Post #2 below)!
Alpha 0.3.1 Release, 12/3/2011:
Download: http://www.multiupload.com/NUV8KDF9OZ or http://dev-host.org/4up if MultiUpload never comes back
Changes:
Only one - actually include Daily Driver 12/1/2011. People who flashed 0.3.0 only need to reflash Daily Driver from my kernel thread, no need for a full flash of Hellraiser.
Alpha 0.3.0 Release, 12/1/2011:
Download: PULLED, BAD RELEASE: Use 0.3.1 instead. If you already flashed 0.3.0, flash the 12/1 release of Daily Driver
Changes:
Update to some random kernel pulled from the wrong location on my hard drive
Overwrite /system/etc/apns-conf.xml with a "known good" one
Overwrite the CSC with a "known good" one
Home button haptic fix, courtesy of LinuxBozo of Infuse Hellraiser. Thanks to amtrakcn for pointing out that LinuxBozo's fix works on our device
Alpha 0.2.2 Release, 11/10/2011:
Download: http://www.multiupload.com/C1W5S6XW0R
Changes: Update to Daily Driver 11/10/2011 kernel (disables autoroot which broke root for a bunch of people), tiny installer script cleanups.
If root is working well for you, it is not worth flashing this
If root is broken for you, I recommend installing Daily Driver 11/10 and flashing ChainsDD's latest su package (linked from the DD thread's first post now). If you flash this it will remain broken, this only fixes new installs
Alpha 0.2.1 Release, 11/08/2011:
Download http://www.multiupload.com/ORQESFHVBT
Changes: Only one, replace Nfc.apk with the correct one. Fixes NFC service force closes.
Alpha 0.2 Release, 11/07/2011:
Download - PULLED due to excessive fail. Use 0.2.1 instead!
Changes:
Should now flash without the mount workaround trick after ROMs that unmount /system
Added NFC files from the I777 and one permissions XML - These combined with a small mod to Settings.apk will allow NFC to work. Will post details for ROM devs on making these mods soon. NOTE: Right now this only supports reading tags! Google Wallet support requires a LOT more work, if even possible! (Edit: I'm fairly certain it'll only be possible in CM7 - but I think I also know what's needed for the CM7 guys to get the rest of the way there.
Initial release, 11/06/2011:
Version - Alpha 0.1
Download - http://www.multiupload.com/9RJKKSBFZ0
How it works
Here's the details of how this package works.
1) This package replaces the modem with a known good I777 modem
2) It also replaces the kernel with an I777 kernel (Right now, Daily Driver 11/03 release) - This is half of the keymap fix. Also, DD 11/3 contains a fix that allows wifi tethering to work on both I777-derived ROMs and I9100-derived ROMs
3) It replaces two of the keymap files in /system/usr/keylayout/ - see http://forum.xda-developers.com/showthread.php?t=1313050&page=56 for details - thanks to MikeyMike01 and Dungeon47 for this one
4) It replaces most of the audio library files to fix the issue with outgoing mic audio in calls - this is the same fix used by Cyanogenmod 7 - see https://github.com/koush/proprietar...12f711197665edeb28522386a77a62da24bab#diff-28 for details, thank atinm for this one
Attached:
Hacked settings APK for VillainROM 3.0 - This, along with Alpha 0.2.1, should allow you to turn on NFC. May work on other XXKI3-based ROMs
For ROM Authors:
To get NFC to show in Settings, baksmali the Settings APK and open WirelessSettings.smali
Look for the line below:
Code:
invoke-static {p0}, Landroid/nfc/NfcAdapter;->getDefaultAdapter(Landroid/content/Context;)Landroid/nfc/NfcAdapter;
Delete the next two instances of lines that contain the word removePreference
NFC should then show in Wireless settings
Great work! I can't wait to try this out when I have some free time.
well aren't you awesome bro. Thanks a lot. This opens the door to a lot of good things.
this looks awesome i have to find a rom i want to try from their forums though since lite'ening doesnt work
Dude you freaking rock! Thanks so much for this! What is your donate link?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
What is your donate link?
Click to expand...
Click to collapse
Under his Thanks Meter.
THANKS!!!
about to test it out with the sensation rom! Really appreciate the effort you have been putting in lately!
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Awesome, just awesome entropy
Let the flashing and testing begin! You are a genius sir.
Sent from my SAMSUNG-SGH-I777 using XDA App
jgrimberg1979 said:
Entropy
What about Roms that have a different version of cwm recovery, for ex some of them have 4.x cmwr. Does your kernal that you including relash cwr 5.x?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
CWM is in the kernel, and this replaces the kernel.
Entropy512 said:
CWM is in the kernel, and this replaces the kernel.
Click to expand...
Click to collapse
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
jgrimberg1979 said:
Awesome, what would be some of the reason why this would not work with some roms, since the package addresses most of the differences between the two phones? Is there something we should look for besides bootloader, that may stick out as a possible incompatibility?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Thank you Entropy, can I use this with i9100 MIUI rom as well?
Sent from my SGH-I777 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Home button is not working. I've went and flashed sensation twice, following your steps of course. Did you have the same issue?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
You need to map the keys correctly...
Sent from my GT-I9100 using xda premium
Entropy512 said:
Unsure yet - most likely any remaining issues will be common.
The one thing might be if the ROM has a special unusual kernel dependency. I'm not too far from Ninphetamine, but there might be some wacky kernels out there that have wacky ROMs paired with them. Such ROMs would even have problems with other I9100 kernels on the I9100.
I don't expect anything to be blatantly obvious at this point... My biggest worry is that I botched the permissions in the updater script.
Click to expand...
Click to collapse
Still not workin
Edit; to clarify audio issue on the sensation rom is still there
Sent from my GT-I9100 using xda premium

Porting or compiling MIUI for unsupported device?

I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Silentbtdeadly said:
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Click to expand...
Click to collapse
They steal the code from CM source. Then they wrap it up in a closed source OS. So you won't find any source for it.
zelendel said:
They steal the code from CM source. Then they wrap it up in a closed source OS. So you won't find any source for it.
Click to expand...
Click to collapse
I figured it might be something like that, would explain why I haven't found anything really helpful.. but then the question becomes how do people port it to other devices? I'm personally a fan of the functionality it has over CM, and it would give the users of my device something to play with(and me something to learn/experiment with) while we wait for ICS to get built. Hell, if I can find some good resources, maybe I could contribute to the ICS build before it is done..
But while the resources I've been finding here are good, I learn best by tinkering, just figuring things out, so the resources between what is offered here and the finished product would do me the most good.
Silentbtdeadly said:
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Click to expand...
Click to collapse
So what we (miui porters) do is take the kernel from cm7 and some lib files from cm7 and add to an existing miui rom until it boots. It helps if you use a similar device as the base (I use the nexus s 4g as a base for my epic 4g ports b/c epic is pretty much a keyboarded version of the nexus s 4g).
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
So what we (miui porters) do is take the kernel from cm7 and some lib files from cm7 and add to an existing miui rom until it boots. It helps if you use a similar device as the base (I use the nexus s 4g as a base for my epic 4g ports b/c epic is pretty much a keyboarded version of the nexus s 4g).
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Where do you guys get the weekly build of miui from, I know it is updated every friday, but I haven't seen where they are getting it from..
The phone I want to develop for is the Amaze 4g, the Sensation is pretty much the same with just a underclocked cpu. The amaze is new enough that everything I've found says they are working on a cm9 build and skipping cm7 all together, so the best I can think of is grabbing some files from the sensation cm7(like you do the nexus) and stock files from the official gingerbread releases for the amaze.
The question is what files can I use from the sensation, will the files from stock ginger work, and which files need to be ported at all. The best I've found is this http://www.madteam.co/forum/support-65/how-to-port-miui/ which I've read the feedback on, and results seem to vary quite a bit.
Silentbtdeadly said:
Where do you guys get the weekly build of miui from, I know it is updated every friday, but I haven't seen where they are getting it from..
The phone I want to develop for is the Amaze 4g, the Sensation is pretty much the same with just a underclocked cpu. The amaze is new enough that everything I've found says they are working on a cm9 build and skipping cm7 all together, so the best I can think of is grabbing some files from the sensation cm7(like you do the nexus) and stock files from the official gingerbread releases for the amaze.
The question is what files can I use from the sensation, will the files from stock ginger work, and which files need to be ported at all. The best I've found is this http://www.madteam.co/forum/support-65/how-to-port-miui/ which I've read the feedback on, and results seem to vary quite a bit.
Click to expand...
Click to collapse
Since your devices are so close, try just copying system/lib/egl and system/lib/hw from stock to Sensation MIUI and also IDK if Amaze and Sensation kernels are compatible, but I'll assume not because that could lead to a brick. So copy boot.img from stock to MIUI. Then Logcat and see what the errors are and replace whatever files error (If it says libcamera failed, replace it with one from stock). It may never boot from a stockbased kernel, it does on some devices and not on others. You may also be able to unpack the boot.img from stock and Sensation MIUI and copy the Sensations intramfs/ramdisk from Sensations folder to Amaze's. Then repack the Amaze folder, which has the Sensation's intramfs in it and then try.
xboxfanj said:
Since your devices are so close, try just copying system/lib/egl and system/lib/hw from stock to Sensation MIUI and also IDK if Amaze and Sensation kernels are compatible, but I'll assume not because that could lead to a brick. So copy boot.img from stock to MIUI. Then Logcat and see what the errors are and replace whatever files error (If it says libcamera failed, replace it with one from stock). It may never boot from a stockbased kernel, it does on some devices and not on others. You may also be able to unpack the boot.img from stock and Sensation MIUI and copy the Sensations intramfs/ramdisk from Sensations folder to Amaze's. Then repack the Amaze folder, which has the Sensation's intramfs in it and then try.
Click to expand...
Click to collapse
Awesome, a place to start. My buy for the Amaze got screwed up, so I'm going to likely get one from tmobile.. but I've already put together a rom to spec that you have described, and I have a few kernels to try too. I hope that checking the logcat and making some tweaks based on the output I get a working rom, the next questions would be what a script looks like(on a pc or mac) I could just apply to pull the files from the different sources to apply to weekly released-- I am pretty sure that is what successful ports do.. and what I could do to be more of a developer rather than just porting or kang'ing. I just figured this would be a good way to get some working experience in the meantime.. but I am guessing that once a good build of an OS is out there, people aren't compiling from source. Seems like many are just learning aspects of the OS and tweaking stock roms with things they have found..
Thanks again for the advice, as soon as I have the phone to test it with, I am gonna give this a try
Silentbtdeadly said:
Awesome, a place to start. My buy for the Amaze got screwed up, so I'm going to likely get one from tmobile.. but I've already put together a rom to spec that you have described, and I have a few kernels to try too. I hope that checking the logcat and making some tweaks based on the output I get a working rom, the next questions would be what a script looks like(on a pc or mac) I could just apply to pull the files from the different sources to apply to weekly released-- I am pretty sure that is what successful ports do.. and what I could do to be more of a developer rather than just porting or kang'ing. I just figured this would be a good way to get some working experience in the meantime.. but I am guessing that once a good build of an OS is out there, people aren't compiling from source. Seems like many are just learning aspects of the OS and tweaking stock roms with things they have found..
Thanks again for the advice, as soon as I have the phone to test it with, I am gonna give this a try
Click to expand...
Click to collapse
Actually, one more suggestion on the kernel. Using dsixdas kitchen, extract the boot.Img from amaze stock and sensation miui and go to boot.img-ramdisk folder and go to init.RC on both devices using notepad++ and find the line that says bootclasspath and copy it from miui to amaze stock. Then recompile using dsixdas kitchen and then test
Sent from my GT-P7510 using Tapatalk

[ROM][Guide][4.0 US+INTL]GT-I9000 rom ports

WANTED: Users to port SGS roms to the 4.0. You will need to know how to complete a full restore if something goes wrong, but that's it. I cannot go through the forums searching for good SGS roms, as I have several threads to manage, and a rom to work on. The steps are easy for you though, and if you port a rom I will add it in the OP.
First of all, I want to say that I take NO credit on any of these roms. All I did was port them over and add speed tweaks, or added ones that users have ported. If the rom creators or mods have any issue whatsoever with this thread, I will happily take it down, even though I think it would be a large contribution to the 4.0 community. I will continue to update this forum with info as I go along.
I, after a fortunate afternoon of boredom, have managed to successfully begin porting I9000 roms to our devices! Fortunately, they are similar enough that it boots without any modifications. I will put up here any ports that I make, and any that the users create. Note that these WILL NOT BE UPDATED! These are one-time ports, to be used and improved upon by the community. Anything that is broken now will stay broken, unless a user decides to fix/update it, then I will include it in the OP.
What *should* work in all ported roms:
wifi
GPS
home buttons
everything else
What will probably *not* work on ported roms:
Bluetooth
Camera
backlight on buttons
Ported roms:
~GamerzRom odexed V11-~
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1656081
Added:
V6 supercharger, and build.prop tweaks from it.
init.d tweaks from my rom
ext4 filesystem
Advanced mount options
Auto zipalign and Database optimize
Removed apps that do not work on our Player (such as the Dialer)
Download:http://www.mediafire.com/download.php?ctuu2w295w2xlk6
~Saurom~
Original thread:http://forum.xda-developers.com/showthread.php?t=1388342
Ported download link:http://www.mediafire.com/download.php?csua40hkg1r3m86
~JellyBeanRom~
Original thread: http://forum.xda-developers.com/showthread.php?t=1260709&highlight=gb
Ported download link:http://www.mediafire.com/download.php?mgec81f3ifck221
~Ario Rom (ported by ChaosChris)~
Ported thread link : http://forum.xda-developers.com/showthread.php?p=29950015#post29950015
Original thread: http://forum.xda-developers.com/showthread.php?t=1536558
To use these Roms:
You MUST use a Gplayer kernel! GT-I9000 kernels will not boot!
A full wipe may be necessary with some roms if you encounter issues.
Converting (for porters)
Steps:
1. Download wanted rom (must be GB)
2.Move the zip to the internal sdcard
3.Reboot into recovery
4.Flash zip, then boot into download mode
5.Flash a SGP kernel
6. apply my mod pack to the rom, by either copying/pasting the system directory over the SGS rom's system directory, or by pushing it via adb, (eg. adb push /path/to/modpack /system).
7. Profit!
NOTE: after applying this, porters may want to remove non-working packages such as the dialer and mms, as they may cause issues with the end result if they are kept in. Do not delete phone.apk though!! This is required for the camera and some other things, and breaks stuff on certain roms. You have been warned.
NOTE: If you use this modpack, please give me credit, and link back to this thread so that more people can use it. Also, you should probably link back to the ported rom's thread as well, to avoid "ripping off" those devs.
Modpack:
Changelog
V1-
Preliminary release
Fixes wifi and GPS
Includes v6 supercharger and init.d tweaks
V2-
fixed vold.fstab so sdcard is mounted properly.
Download:
ModpackV1:
http://www.mediafire.com/download.php?diaq6im4i18ktf7
NOTE:Note that this is preliminary. It fixes everything listed, and attempts to fix some broken things. Your mileage may vary. This is not a cwm flashable zip! you much extract and adb push this over the existing system directory. This is mainly intended for porters, so users apply at your own risk. This will work, but is a very early release.
Modpack V2 (thanks to ChaosChris):
https://docs.google.com/open?id=0B9OVlH2Pl76DZk5Pa3lJVXlrYzA
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
iJimaniac said:
Looking good! Does the gamerz port have the 388mb of ram, I thought that was kernal related?
Sent using Tapatalk
Click to expand...
Click to collapse
Yeah, it says that because it includes semaphore's kernel, which raises the max rom to 380, which we could do on our kernel's, but apparently that breaks a lot of stuff if you go much further then 350 (according to klin).
is the wifi fixed in your port or do we have to do your fix after flashing?
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
check over in the operation: ics for the 4.0 thread I believe they are already attemping to use the cm7 kernel to boot a cm9.
daniel644 said:
is the wifi fixed in your port or do we have to do your fix after flashing?
Click to expand...
Click to collapse
Yeah, it is fixed before you flash. Once I manage to iron out a few more bugs, I will probably release a "conversion pack" that fixes all the issues. I already have one that fixes wifi and gps, but bluetooth and camera have me stumped, and I do not want to replace the entire hw/lib folder, because some of these roms have lib optimizations, but I may have to.
Sent from my GT-I9000 using xda app-developers app
Supermaster34 said:
Just a word of advice, make sure you get permission from the devs! Also surely this will work with ICS roms right? Just swap out the SGS kernel with the SGP CM7 kernel and it should work (I think)
Sent by my Robot Butler
Click to expand...
Click to collapse
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that zaclimon has tried it, and he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable. I also believe that he said the issues may have been rom based, so here it goes, and wish me luck.
Sent from my GT-I9000 using xda app-developers app
hanthesolo said:
Since I am merely redistributing their work, not incorporaring it into anything I have made, or taking any credit for it, I don't asking permission is necessary. I may be completely off base, but I think that as long as you give devs 100% credit, and link to their original work, it is okay. It may not be the best option, but neither is asking EVERY dev if I can port their rom, or ask permission for user-ported roms.
Youay have an idea there, althouh I think that daniel has tried it, abd he said it wouldn't boot. I have 2 efs backups, so I guess I can try, although even if the kernel boots, I bet I will have to do a LOT more work before it is usable.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
zaclimon said:
I've already tried with a cm7 kernel and I got an error of looping (netd1.0 starting) that's why I'm trying to do something. Now I need to backport 3.0.8 usb gadget drivers.
Click to expand...
Click to collapse
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course . A lot farther out there, but maybe I can use a SGP5.0 kernel to get it booting. A LOT less likely, but hey, i'm experimenting .
EDIT: I cannot try ICS, since I need to reboot into recovery a second time, and I cannot do that, as I have the intl bootloader on my US device, and it would require it to be booting first.
hanthesolo said:
Whoops, I meant you . I will try with a official cm9 build from the SGS forums, and see if that fares any better. Probably will not, but it doesn't hurt to try.
EDIT: well, nevermind about that. He seems to have pulled all of his download links, and I cannot get to the CM7 build. Oh well...
I am going to try anyway with the I9000 package since it seems to have EXT4 support, and I *think* that was what was bootlooping me earlier. This as all just my hopeful rationalization, of course .
Click to expand...
Click to collapse
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
zaclimon said:
I think we should do like entrophy's because I get bored from mtd. Also just tried the gamerz rom port. As I see the camera works, don't know about bluetooth (it can turn on). Vibration works too. I was able to connect to wifi pretty fast and I have one word for this rom. FAST!!!!
Good job!!
Click to expand...
Click to collapse
Well, thet camera shows a preview, but fails when a pic is taken, for some reason. Bluetooth does turn on, but is not seen by any other devices, and cannot scan for others either. I did do a little tweaking with Gamerz, so it will be even faster than it was already, which is pretty blazing! I have 2 more that I can put up (I have a preliminary package that I just adb push over the system files that works for now). I have also gotten the camera apk onto my rom, and it works really well! It doesn't take 5 MP pics, or record 720p video (which may be because I am using Terrasilent, which reduces the amount of Vram the system can have), but tap to autofocus and everything else works pretty well. I have a sneaking suspicion that the camera is soft limited, not hard-limited.
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
zaclimon said:
I also noted that the external sd card isn't working too (a problem with vold.fstab I'll correct it right now)
Click to expand...
Click to collapse
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
hanthesolo said:
I don't use an externel sdcard, so thanks for pointing that out! I will include a fixed version in my mod pack.
Click to expand...
Click to collapse
Here's the vold.fstab if you need it
Okay, it seems that the zip hosed my partitions (converted them to yaffs2 and mtd), so I am going to perform a full restore, and just keep porting GB roms. As soon as you can get the usb gadget driver working, zaclimon, I guess I can keep working on it, but for now I will just keep to GB.
Two more roms up! I will probably not port any other unless I see an especially good one, but I will put up my mod pack tomorrow.
has anyone found out if the ported roms enable tv out or has someone found out if tv out support is in the i9000 kernal?
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
iJimaniac said:
TV out has to have hardware, or your not going anywhere. I think the galaxy player lacks the hardware unfortunately. If it does have the hardware, it was very dumb of Samsung not to enable it.
Sent using Tapatalk
Click to expand...
Click to collapse
what hardware does the galaxy s i9000 have that allows for tv out? I thought the galaxy s i9000 and the galaxy player 4.0 had the same gpu?

[KERNEL] The SickKernel

Welcome One X+ users, this is the SickKernel. What you can expect over time is more and more features.
Changelog:
Code:
11-20-12
Removed userspace govenor
set ondemand govenor default
used newer toolchain
Directions to flash
Code:
Go to fastboot, from android type adb reboot bootloader
download the image
cd to your downloads folder
issue the following command
fastboot flash boot sickkernel-0_0_1.img
Source ->
Bugreports go
Note,
If WiFi doesn't work let me know about it. I am trying a new method of kernel packaging which may backfire. If this happens, there is an easy fix. Enjoy! Also I don't own the device. I have some testers, but if a kernel doesn't boot I have no way of knowing sometimes. Don't be afraid to tell me issues
MOD Edit: Removed DL-Links as OP isn't xda-member anymore
I'd recommend you saying that this is for the Int'l model and not the AT&T model.
Well, it won't cause bricks to flash it wrongly. Besides no one knows if the devices have a definitive difference that prevents it from booting. On a side note, this currently uploaded boot.img has the ramdisk of a cm10 ROM. There for it will bootloop sense
Sent from my PK7630000 using Tapatalk 2
nice to see another one working on this Are the AT&T versions of phone totally different ?? (Other SOC, or something else that prevents it from boot ) ??
n3ocort3x said:
nice to see another one working on this Are the AT&T versions of phone totally different ?? (Other SOC, or something else that prevents it from boot ) ??
Click to expand...
Click to collapse
a totally different base yes not phone, lots of bricks trying to flash international HOX+ software
Look up my kernel release, I think I pretty much nailed down module embedding. There's a total filesize limit it seems on the boot.img but it works.
I can release the framework I'm using, all scripted out to 2 simple commands if you want.
Hi sir could you add call recorder feature into your kernel in such a way we can record calls with the Bluetooth audio ear phone connected....hopefully this can help you
http://forum.xda-developers.com/showthread.php?t=1971302
Just a hope sir
Rgrds
I think you should specify on the top of the OP that this is not for ATT. Hopefully they will split forums for the HOX+ development and add a seperate ATT forum, but until then there will be plenty of havoc over all of these dev threads that are not specific on which device they are for.
Dont mean to bust balls, but Noobs are noobs.
Okay, so gonna do some catchup here. I accadently threw the wrong ramdisk in this kernel (my bad) This will be fixed soon after the holidays. Next terms of buisness, the module is inside the boot.img but i dont have the device so I cant test it. Next, kernels are kernels. The very nature is compatability. How many people bricked there PC trying to install a new kernel. None, would be the answer. When ATT source is released, I will merge the two together, and build one compressed kernel that boots on both. Next line of buisness, features will be slow.. Im helping lloir with something currently.
And finally, because some people are total idiots, and cant use common sense the source is at
github.com/simonsimons34/htc_enrc2b_kernel
simonsimons34 said:
Okay, so gonna do some catchup here. I accadently threw the wrong ramdisk in this kernel (my bad) This will be fixed soon after the holidays. Next terms of buisness, the module is inside the boot.img but i dont have the device so I cant test it. Next, kernels are kernels. The very nature is compatability. How many people bricked there PC trying to install a new kernel. None, would be the answer. When ATT source is released, I will merge the two together, and build one compressed kernel that boots on both. Next line of buisness, features will be slow.. Im helping lloir with something currently.
And finally, because some people are total idiots, and cant use common sense the source is at
github.com/simonsimons34/htc_enrc2b_kernel
Click to expand...
Click to collapse
Simple edit to help solve a simple misunderstanding. Your thread, your rules, though.
Hi, how about sweep 2 Wake?
Sent from my GT-N8000 using Tapatalk 2
Thread closed
As the OP had a wrong assumption about the consequences of breaking xda rules, and preferred to withdraw from xda subsequently, I closed this thread.

[Q] If no roms support my phone, what can I do?

I have the ZTE Avail 2 (aka Z992) (and it sucks, considering it's a $70 phone, buying a new one isn't an option because I just built a computer). It hasn't had an update since 4.1.1 and it's very slow, (usually have only ~50mb of ram free when just sitting at launcher) even with all of the tricks to speed it up (greenfiy, cleaner, etc) and on top of that, it's loaded with features that ZTE put in that suck. So after searching and searching for a custom ROM with support for my phone, I can confirm there is zero. I looked at the rom dev tutorial - http://forum.xda-developers.com/showthread.php?t=1272270 and the kitchen program doesn't support my phone either. Does that mean I'm screwed? If there's a way to make a rom compatible other than the android kitchen or straight up learning to program, please tell me. I'm willing to learn anything that isn't hugely time consuming. Thanks for any replies.
FourZer0 said:
Does that mean I'm screwed? If there's a way to make a rom compatible other than the android kitchen or straight up learning to program, please tell me. I'm willing to learn anything that isn't hugely time consuming. Thanks for any replies.
Click to expand...
Click to collapse
No, you are not. You can try many other porting tutorials around the web. I found a list of phones similar to yours, might come in handy.
In fact, since your are trying to "port" ROMs, just think about the fact that "where did those ROMs come from?" Those ROMs were built from source code. The Android project is open source and if you are feeling adventurous, you can just grab the source code and compile it yourself for your device. It might be very easy or very tough, depending on your device. I would advise you to try to build Cyanogenmod 10.1 from source code. Check here and here.
And make sure to check this (must).
Cheers man! Trust me, trying to build Cyanogenmod from source will be a lot of fun!
Thank you! So I found CM for the xperia tipo, which was on the list of similar devices. I should use that one and change whatever needs to be changed, right?
Also, is it possible to do that for 4.4 stock? That may be a better idea if CM consumes too much ram
tuxboy said:
No, you are not. You can try many other porting tutorials around the web. I found a list of phones similar to yours, might come in handy.
In fact, since your are trying to "port" ROMs, just think about the fact that "where did those ROMs come from?" Those ROMs were built from source code. The Android project is open source and if you are feeling adventurous, you can just grab the source code and compile it yourself for your device. It might be very easy or very tough, depending on your device. I would advise you to try to build Cyanogenmod 10.1 from source code. Check here and here.
And make sure to check this (must).
Cheers man! Trust me, trying to build Cyanogenmod from source will be a lot of fun!
Click to expand...
Click to collapse
Okay, ignore my last replies, I've been reading a lot and kind of know what I'm doing now.
Only problem is, I can't find a stock rom of my phone! The closest thing I found was a custom ROM for a phone similar to mine, which is confirmed working to the one I actually have. So would that do okay? androidforums . com/prelude-all-things-root/795640-azazel-rom-z993-aio.html is the one. Thanks again for any help.
FourZer0 said:
Okay, ignore my last replies, I've been reading a lot and kind of know what I'm doing now.
Only problem is, I can't find a stock rom of my phone! The closest thing I found was a custom ROM for a phone similar to mine, which is confirmed working to the one I actually have. So would that do okay? androidforums . com/prelude-all-things-root/795640-azazel-rom-z993-aio.html is the one. Thanks again for any help.
Click to expand...
Click to collapse
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
tuxboy said:
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
Click to expand...
Click to collapse
Oh, I didn't know that would work, thanks again! I have my rom modded like crazy though, tons of xposed modules and build.prop edits, also I uninstalled a lot of stock apps - I'm sure I could get the build.prop somewhere, but what about the other things? Do they matter at all?
Edit: after the backup I now have a ton of tars, a recovery.img, and a boot.img. I extracted all of the tars, now do I just put all of the folders from the tars in a folder with the imgs and that's my base rom?
tuxboy said:
You can easily take a backup of your current ROM. Try booting into recovery and making your own custom recovery (ClockWordMod).
Click to expand...
Click to collapse
Okay, I've come pretty far and I've made several flashable zips and fixed many errors, but there's one thing I can't figure out - the updater script doesn't work, and I realized it's because I was using the one from the original port, and I need the one for my phone, which I can't get from the cwm recovery. I really need the whole META-INF folder. Where can I get that?
I tried for 1 week and i didnt find any official and stable rom for my samsung galaxy note 4 Sm 910h. I used resurrection remix unofficial and camara didnt worked there . Please any solution there help me

Categories

Resources