Before everyone starts flaming me and trying to kill me for being such a noob, i would like to say that i'm a teen and a noob.
ANYWAYS, i got bored and decided to have a go at porting Firefox OS to the Optimus 2X. After figuring out how to make a flashable zip out of .img's, I tested a bit. Unfortunately ADB doesnt work and I don't know how to do live kernel debugging.
What works: Kernel
What doesn't work: everything else
Source code: http://github.com/JordanRulz
Download:
First Semi-working attempt: http://d-h.st/juX (not a flashable zip)
2nd attempt: link on http://jordanrulz.tk/ (flashable)
3rd attempt (current): http://d-h.st/0We(flashable)
Turn signature verification off before flashing
BUILD INSTRUCTIONS (still doesn't work, but for anyone who thinks they might have the answer, go right ahead)
1.
Code:
git clone http://github.com/JordanRulz/B2G.git
2.extract a cm9 rom to B2G/my_device_backup
3.cd to the B2G directory and
Code:
ANDROIDFS_DIR=my_device_backup ./config.sh p990
and wait for the code to download. This has a good chance of failing because repo and git are stupid.
4.
Code:
./build.sh
5.edit core/sysroot/init.rc so that it imports init.p990.rc
6.go to line 98 of build/core/Makefile and change the build fingerprint to something acceptable by the build system
7.go online and find a wpa_ctrl.h and put it in hardware/libhardware_legacy/wifi/libwpa_client/wpa_ctrl.h
8.copy libcamera.so and libwpa_client.so from a cm9-based rom to out/target/product/p990/obj/lib/
9.it should turn out boot,img, system.img, a system folder, userdata.img, a userdata folder, etc. with adaptations, you should be able to craft a flashable zip out of the folders.
Please hit donate if you feel my work is worth donating to.
Good effort bro!
Way to go buddy.... Expecting this Rom for our beloved Optimus 2x. (me too a noob cant help much)..
Thanks and wish u best of luck..
ahahaha, great work! bring to the old O2X a new system!
Interesting tread, I'll look at the files. Let's hope this will be a cooperative tread to make this
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
nicholaschw said:
Ok. What i did similarly to my phone to get this up. First, use PowerISO and extract userdata.img and system.img. Once done, its just like system folder of android while userdata is just data folder for user's data. Obviously. And then, the boot.img goes to the same as a flashable rom zip root folder. So basically, they are the same as flashing cm. Just need to add another few commands for recovery.img so that the whole thing is flashed like cm10
Click to expand...
Click to collapse
doesn't work. "invalid image file"
i think probably you can pm any recognised dev's for help....if you post a thread here i dont think anybody will try to help....you can pm the dev's like tonyp, harsh, carburano or anyone and you can ask for help in packaging and later on continue with your development....just an idea....:good:
good stuff man., were not the flaming community of yester year
This is getting really frustrating, after restarting multiple times and over 10 failed attempts. I have forked all the repos to my github so that all that want to help are able to do so. http://github.com/JordanRulz
Hello everyone. It's for new bl or old bl? Thanks
Sent from my LG-P990 using xda app-developers app
I say it´s for the old BL, if i don´t read the updater-script inside completly wrong.
It's for old bl
Sent from my LG-P990 using xda app-developers app
build instructions (for a non-working build, but still useful for f*cking around) were added.
JordanRulz said:
build instructions (for a non-working build, but still useful for f*cking around) were added.
Click to expand...
Click to collapse
:good::good:
Don't know if you're going at it the right way but good luck, and you should contact another dev just to make sure at least that you're on the right path.
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
JordanRulz said:
I'm trying to get help from several devs.
Sent from my LG Optimus 2x using xda app-developers app
Click to expand...
Click to collapse
I hope if you develop successful, it will have 1 for SU660 :victory:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob report on f.b.i
alexcyb said:
http://jordanrulz.tk/ not open the sites, is a virus java drive, jordan you really noob
Click to expand...
Click to collapse
Its not a "virus java drive", its a hidden bitcoin miner. If u use a secure browser like Firefox, it will prompt you before running it.
Sent from my LG Optimus 2x using xda app-developers app
Related
Hey the update.zip for nexus's one update is out
here is the link android.clients.google.com/packages/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
and here the prerooted from modaco romraid.com/paul/nexusone/update-nexusone-FRF50-signed.zip
i've started porting. help devs .
Does anyone know how to not flash the new radio cause when i remove the radio.img it always says line 70 installation abonded cause it couldn't find radio.img. any help ? don't worry figured it out
Yeah. I want froyo.
Ohh.. is that real to made 2.2 on Tattoo??
-------------------------------------
Sent via the XDA Tapatalk App
I'm waiting for 2.2 on tattoo.
Developers pls help the Tattoo user.
Thanks in advance.
I'm sorry to say it, but you'll have the same problems as with the 2.1 porting...: the drivers for the camera, sensors, FM radio, etc....
don't tell me xD and what do you believe about the new kernel ? anyway i can always try . and if i don't do it i'm loser .
rwmanos said:
don't tell me xD and what do you believe about the new kernel ? anyway i can always try . and if i don't do it i'm loser .
Click to expand...
Click to collapse
you are brave!
i hope you will be a winner
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
TheSSJ said:
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
Click to expand...
Click to collapse
yeahhhh
TheSSJ said:
Guys, I'm confident that we can at least look at the source of 1.6 Tattoo regarding the camera and port it to the new Kernel...I won't stop researching until a decent ROM is created by all of us!
First I will download the source code of the tattoo ROM, then I will build a VM featuring Ubuntu and get all necessary dev-tools to decently start programming that son of a b****!
Click to expand...
Click to collapse
I belive in you!...You can do it!
If there is source code for HTC's 1.6 camera drivers, then it should be easy to port those drivers for 2.1 or 2.2, even if the Android has changed. It's more easy than reverse engineering binary drivers, no?
We just don't have a man who can (or want) to do it.
I have a problem...I wanted to unpack the boot.img file, but unfortunately the structure of this update.zip seems to differ a lot from the normal update packages...this one seems to patch most files, which unfortunately means that there's no way to start this thing up on our Tattoo's, or am I wrong?
TheSSJ said:
I have a problem...I wanted to unpack the boot.img file, but unfortunately the structure of this update.zip seems to differ a lot from the normal update packages...this one seems to patch most files, which unfortunately means that there's no way to start this thing up on our Tattoo's, or am I wrong?
Click to expand...
Click to collapse
If you flash the original Nexus One 2.1 rom, and the nexus one recovery image, then you should be able to flash this...
Yeah, but I don't think the Nexus One recovery image will work on my phone...this smells like bricking the phone hard
use the modaco one. but i can't find a way to not flash the radio.img . i remove it from update-script but the i can't get rid off the syntax error can't figure out why.
I hope you ALL will be winner
rwmanos said:
use the modaco one. but i can't find a way to not flash the radio.img . i remove it from update-script but the i can't get rid off the syntax error can't figure out why.
Click to expand...
Click to collapse
I know this sounds stupid, but did u resign the zip file after deleting radio.img or did u just deleted the img file from the zip and update-script? I'll resign it and then check - anything else I have to pay attention to? I saw again a patchfile for the recovery image, I hope it does not brick my good Amon_RA one...
/Edit: doesn't the update-script normally need an update-binary?
TheSSJ said:
/Edit: doesn't the update-script normally need an update-binary?
Click to expand...
Click to collapse
Not if uses the recovery images built-in syntax...
kiljacken said:
Not if uses the recovery images built-in syntax...
Click to expand...
Click to collapse
thanks for the info...will try to flash the update package when my tattoo is charged..
yeah i did resign . i don't think it's a radio idea to flash it with the radio.img but you know if you just delete resign and flash it won't work cause it is going to look for the file and poof installation aborted . i think i figured out the syntax error .I'll flash when is my tattoo is charged too always out of battery
*This is my first ever ROM port, so expect not much working*
*I take no responsibility for anything that you do to your phone or what happens to it*
FrostMod GingerSense v1a
This is the first version of what is going to hopefully get more and more working and functional with time.
Working: Not much. Post in comments what's not/what is for you.
This right now is a pretty bare OP, but hopefully with continued development, will grow with time.
NAND Backup before flashing, it's always safe!
Download: http://www.megaupload.com/?d=2TLM7ZMA
(MD5) fd6e8b7b613ed07225e601397944ee7a
Ported from the Desire HD leaked Android 2.3.2 Gingerbread leak found here: http://forum.xda-developers.com/showthread.php?t=983847
Changelog:
v1a: Initial Release
reserved.......
another just in case........
downloading now
Just had to change my pants
Sent from my ADR6300 using XDA App
With not much working. Does that include basic phone functions? Eg. The radio. Calling, sms?
Sent from my ADR6300 using XDA App
Just tried flashing with cwm2 & cwm3.
got installation aborted each time.
Sent from my ADR6300 using XDA App
What cwm is required? Ill give it a shot to see what is working, just sittin in front of tv watchin golf anyways.
Sent from my Incredible using XDA App
theguitarguy58 said:
Just tried flashing with cwm2 & cwm3.
got installation aborted each time.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Same here. Used 2.5.1.2 and 3.0.0.8.
This will not install at all
I may not be a developer but I think I may have an idea on what's going wrong:
1. I think that there's too much being put into the System partition. Correct me if I'm wrong but you're only given so much.
2. I think that the ROM is packaged wrong. When I open up the ROM in 7zip, I don't see the system and boot.img file first, I see a subfolder and THEN the system and boot.img.
Again, I just wanted to give a heads up, I'm in no way educated in this stuff. I'm just reporting as I sees 'em.
Was just gonna say that the structure was jacked. The ROM does seem large as well
kschwarz88 said:
I may not be a developer but I think I may have an idea on what's going wrong:
1. I think that there's too much being put into the System partition. Correct me if I'm wrong but you're only given so much.
2. I think that the ROM is packaged wrong. When I open up the ROM in 7zip, I don't see the system and boot.img file first, I see a subfolder and THEN the system and boot.img.
Again, I just wanted to give a heads up, I'm in no way educated in this stuff. I'm just reporting as I sees 'em.
Click to expand...
Click to collapse
You're right, I was in a hurry and packaged it wrong. Thanks for pointing this out. Will rezip and upload when I get home.
Sent from my Incredible using XDA App
For what it's worth, I repackaged the ZIP myself and am installing it at the moment. It requires CM 2.x (I'm using the temporary flashable 2.5.1.2 that was floating around to bypass my already-installed 3.x series).
I think I did it right, but here's the error I get:
E:Can't symlink /system/xbin/su
E:Failure at line 81:
symlink /system/bin/su SYSTEM:xbin/su
Installation aborted.
donnyp1 said:
What cwm is required? Ill give it a shot to see what is working, just sittin in front of tv watchin golf anyways.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
At the moment, CWM2.
It is not going to install until the system folder in below 250mb or so.
The OP has it at 350mb.
There is no way the OP even knows whether it even works because it will not install like this.
Thanks for the link in the first post. I'm trying a quick test build that I ported. I'll know if this DHD version is any easier to port in a few mins.
Tough to gain confidence if this is how thread starts. Good luck.
ANything yet?
Hello everybody!
Yesterday I was thinking about a new app for Android, and this app would be able to comunicate with the recovery to schedule things like backup and restore. In 2011 I released "ROM Updater" (not that big success though) which used extendedcommands, an extension to the recoveries made by the team of CyanogenMod (it was indeed created to let the CM updater work).
ClockworkMod Recovery adopted this system, but the author probably didn't want the competition, so started to release the ClockworkMod recovery with encrypted extendedcommands. You can still recompile CWM and redistribute with the unencrypted commands, though I decided to opt for something less rouge-ish (why the hell should I recompile something that already "works"?).
Team Win Recovery Project is a 100% open-source recovery with a new scripting language, called "OpenRecoveryScript". It's just like extendedcommands, but without all the implications of "Premium"* or in any case limited API.
Well, TWRP is not only that, it's a full-multitouch recovery, easy to use. It's being built for a list of devices, and this list will be updated every time someone will compile the recovery for his own device. I decided to compile it for the P7500, hoping it will be added soon to the official list. In the mean while, I'll release the builds right here.
I've built and tested the recovery image for the P7500 (WiFi+GSM) and it's been confirmed that it works on the P7510 device too (WiFi only).
Goo.im GT-P7500 TWRP repository
TechErrata GT-P7500 TWRP repository
TWRP 2.2.1.5 - GT-P7500
openrecovery-twrp-2.2.1.5-gt-p7500.img (on Goo.im)
openrecovery-twrp-2.2.1.5-gt-p7500.img (on TechErrata.com)
TWRP 2.2.2.0 - GT-P7510 (thanks to MapleSyrup)
openrecovery-twrp-2.2.2.0-gt-p7510.img
How to flash:
- Copy the recovery into the storage partition (alias /sdcard)
- In adb, as root, execute dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p2
Cheers
*I personally think that Koushik Dutta (the ClockworkMod guy), encrypting the commands with his distributions, played hard: ROM Manager is the "official" CyanogenMod updater (it's distributed along with any CM release even if it's not opensource (and the CM guys worked hard to take the closed-source apps out of their release)), de-facto everybody install the CWM recovery just 'cause it's already there (déjà vu Internet Explorer?). I think this is called "monopoly" and should be fought in any possible way.
I'm all for true open source development, and will be watching your progress on this. Kudos and a thanks to you!
Sent from my GT-P7510 using XDA Premium HD app
I'd be willing to test for the p4vzw. If you build an image for it.
Sent from my Galaxy Nexus using Tapatalk 2
This appears to work on my Wifi Galaxy Tab 10.1 (p7510). Although the log says "E: Unable to mount /sdcard" I can access the sdcard just fine. I tried updating to the latest droidbasement.com kernel and it flashed perfectly.
Oh, and thanks for the quick and easy non-odin way of flashing recoveries.
The recovery is already in the goo.im repository
http://goo.im/devs/OpenRecovery/gt-p7500
The dropbox image is already update to fix the /sdcard "problem" ^^
Would this work on a Galaxy Tab 10.1 wifi (p4wifi)?
Sent from my Nexus One
According to AAccount yes. Please confirm this, so that I'll tell the TWRP guys to add the repo for that device too and I'll update the title of the conversation here.
I can say without a doubt that this is the best recovery I have used on any device in my 3 years with android phones. Wow! Graphics a bit grainy on the p7500, but functionality is fantastic! Thanks!
Very nice recovery system, good to see other options. HTC users had several choices such as AmonRa and 4ext.
Can confirm that it works on the WiFi only version. Thanks for the options , friend. Been running TWRP on my One X since the boot loader was unlocked, and I was missing it.
Sent from my GT-P7510 using Tapatalk 2
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Swammy1979 said:
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
You don't actually need to use adb. Any terminal app should do it. Just tyope "su" before issuing the dd command. I used this app https://play.google.com/store/apps/details?id=jackpal.androidterm&feature=nav_result. I suppose a word of caution would be to make sure you have the command correctly. Don't make a typo like mmcblk0p3 or you could be in a nasty situation.
Adb can be found in the android sdk. Google "android sdk" and download the appropriate one. After that have the sdk download platform tools.
Swammy1979 said:
At the risk of sounding like a noob.....what is adb, and can someone provide a link so I can school myself on it?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
An easy and safe way if you have the SDK installed is to run adb shell
Then type su
paste in the dd command posted earlier
Thanks....I went on google and am now learning about Android SDK. Interesting stuff. I know how I will be spending my weekend!
EDIT: In the meantime, I went ahead and used terminal emulator for the commands. I definitely like the touch interface...and it looks nicer than cwm for sure! It is a little slow graphically, but I think that can be forgiven based on the look of the interface.
Confirmed working on the p7510 wifi
Sent from my GT-P7510 using XDA Premium HD app
Hi
It works like a charm on my 7500.
Thanks for that. Maybe some one could make the install more user friendly, a recovery zip?
Sent from my GT-P7500 using XDA Premium HD app
I could create an update zip... if only I could remember where I left the signing tool...
This is a really nice recovery, thanks for posting it. And I think that with this recovery I can flash a zip from the command line, this will be really useful for my scripts.
elegos said:
The dropbox image is already update to fix the /sdcard "problem" ^^
Click to expand...
Click to collapse
BTW, I'm compiling it for the GT-P7510 (p4wifi), everything works fine, but I don't know how to fix the /sdcard error message, could you please tell me how to do it?
That is a nice one, thank you very much for this project.
MapleSyrup said:
This is a really nice recovery, thanks for posting it. And I think that with this recovery I can flash a zip from the command line, this will be really useful for my scripts.
BTW, I'm compiling it for the GT-P7510 (p4wifi), everything works fine, but I don't know how to fix the /sdcard error message, could you please tell me how to do it?
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/gt-p7500/openrecovery-twrp-gt-p7500-2.1.8.img
^-- this works for the 7510 too
BTW it's just a line in recovery.fstab in the device sources: comment the /sdcard one.
Works great for me although it's a bit slow to boot into compared to CWM or even to TWRP on my brother's HP Touchpad. Also text is a bit pixelated. Other than that though it seems to work well. I use 4ext on my Nexus One so it's really nice to finally get a touch recovery on my tab too
Sent from my GT-P7510 using Tapatalk
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Thanks..
Very Interesting and useful..
Infact i find some guide simple to try...
Good Job!
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
SnXo said:
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
tobixdev said:
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I tried a while ago with this rom: http://forum.xda-developers.com/showthread.php?t=1562603.
The end result was a bootloop. I will maybe try to do it again when I have more time.
this doesn't work with sense without additional work.
Sent from my LG-P880 using xda app-developers app
tobixdev said:
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Click to expand...
Click to collapse
ths very much
Here's presenting stock Slimbean ROM with just 2 commits reverted which prevented users from adding the big menu button to navigation bar and SlimPie. Besides this, this is pure Slimbean without any modification whatsoever. I'm not a developer, in fact I learnt to install linux because I wanted the menu button so bad. I thought maybe I should share this with similar minded people. I'm going to upload updates as and when Slim team releases 4.3 updates as I'm not sure about the changes that would be made in 4.4. I won't be able to take any request as I am totally unaware of how to make any modifications, cherry picks or anything else. Hope you enjoy this ROM.
Code:
Disclaimer: We are not responsible for any damages on your device.
Original Slim Features:
The Real Dark Slim
SlimPIE
Notification drawer Shortcuts
Full hardware key rebinding!
Keyboard rotation
SlimCenter, SlimIRC and much more
Full feature list and changelog can be found on Slimroms website.
Installation instructions
For most users
Please keep in mind if a special instruction is needed it will be noted in the changelog.
Download the latest build from
Addons
!Recommended! Full wipe, and manual format /system
Flash ROM and the addons you want, reboot
Source
This ROM and kernel uses stock Slimbean code, which again can be accessed through Slimroms website.
Credits:
mar5hal
Nebucatnetzer [Slimroms forum]
NeB [Slimroms forum]
kufikugel
Entire Slimroms team for the source code.
Slim team has done an excellent job, please consider donating them.
Download Link:
http://d-h.st/DDf
[If you want to make a mirror, please contact me to update the OP]
Reserved...
another one... just in case...
@gururoop thank you so much for this, the one main thing missing from slim, Menu Button. In theory there shouldn't be any issues since its only 2 extra commits. Downloading now :good:
Just some screens to confirm. Everything is running smooth, no issues whatsoever
Sent from my Nexus 4 using XDA Premium 4 mobile app
Great, thanks a lot
edit: glad to have the menu button back.
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
dark_ente said:
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
Click to expand...
Click to collapse
That would be great, indeed. :good:
dark_ente said:
Great, thanks a lot
edit: glad to have the menu button back.
However, I think it's better if you just make a small patch instead of rebuild the whole rom.
Click to expand...
Click to collapse
finistere said:
That would be great, indeed. :good:
Click to expand...
Click to collapse
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
gururoop said:
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
Click to expand...
Click to collapse
Changelog what is changed?
The new official one has the statusbar mods now. Hate to leave it for the menu key but I might. Thanks for the build.
Sent from my Nexus 4 using Tapatalk
smartymcfly said:
Changelog what is changed?
Click to expand...
Click to collapse
No changelog... Just wanted to check how long does it take to compile in a virtualbox so synced the latest code and compiled...
Sent from my Nexus 4 using xda premium
scottx . said:
The new official one has the statusbar mods now. Hate to leave it for the menu key but I might. Thanks for the build.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
What statusbar mods are you talking about? This build is pure stock with just 2 reverts which enable us to add the menu button, apart from that no other change. The latest build was synced on 5th November, so maybe the statusbar mods were added later.
Sent from my Nexus 4 using xda premium
gururoop said:
i wish i knew how to do that, but if you guys know how to, please guide me and i'll do it...
anyway, just compiled a new build so uploaded it here... OP updated with new link... enjoy...
Click to expand...
Click to collapse
Please correct me if I'm wrong.
I guess you revert the change in framework-res.
In that case, you just need to create an update.zip which replace the old framework-res with your framework-res, and user only need to flash that file instead of the whole ROM.
dark_ente said:
Please correct me if I'm wrong.
I guess you revert the change in framework-res.
In that case, you just need to create an update.zip which replace the old framework-res with your framework-res, and user only need to flash that file instead of the whole ROM.
Click to expand...
Click to collapse
i revert the following 2 commits to achive the desired change:
5dd205257a8cfba3278ddb4ffbdd1897b1feaed7-packages/apps/Settings
8108afc56d15553c1d4abc83c9e9e27ac5b7cb36-framework/base
don't know exactly how many files or what else changes due to that. If you could figure that out, i'll be more than happy to help. and can u tell me whether there is any way i can compile some selected files instead of the whole rom?
gururoop said:
i revert the following 2 commits to achive the desired change:
5dd205257a8cfba3278ddb4ffbdd1897b1feaed7-packages/apps/Settings
8108afc56d15553c1d4abc83c9e9e27ac5b7cb36-framework/base
don't know exactly how many files or what else changes due to that. If you could figure that out, i'll be more than happy to help. and can u tell me whether there is any way i can compile some selected files instead of the whole rom?
Click to expand...
Click to collapse
What I mean is you still compile the rom, but only make a flashable zip of these two files and put it here. It would be easier for both you and me.
From the commit, I guess the two files are settings.apk and framework-res
Sent from my Nexus 4 using Tapatalk 2
dark_ente said:
What I mean is you still compile the rom, but only make a flashable zip of these two files and put it here. It would be easier for both you and me.
From the commit, I guess the two files are settings.apk and framework-res
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
now its getting too embarassing for me, but do you have any easy guide to help me create a flashable zip for these two files??
gururoop said:
now its getting too embarassing for me, but do you have any easy guide to help me create a flashable zip for these two files??
Click to expand...
Click to collapse
No problem mate.
The easiest way is to extract your rom to a new folder, delete boot.img, go to system folder and delete everything except the two files you want to keep. (you must also keep the folder structure). Inside these 2 folders are only files you want to copy (in this case settings.apk and framework-res)
Then go to META-INF\com\google\android\ folder and use notepad to edit the updater-script file like this
After that, you can compress them as simple zip and flash via twrp.
Next time you can just replace 2 files, compress again. No need to edit updater-script
Sent from my Nexus 4 using Tapatalk 2
dark_ente said:
No problem mate.
The easiest way is to extract your rom to a new folder, delete boot.img, go to system folder and delete everything except the two files you want to keep. (you must also keep the folder structure). Inside these 2 folders are only files you want to copy (in this case settings.apk and framework-res)
Then go to META-INF\com\google\android\ folder and use notepad to edit the updater-script file like this
After that, you can compress them as simple zip and flash via twrp.
Next time you can just replace 2 files, compress again. No need to edit updater-script
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So what you are saying is that if someone or I can just extract those 2 apks and add to a flashable zip I have lying round and menu button will be added to normal slim?
Would have been quicker!!
Sent by mobile telephone.
^^^^LOL I agree... Sidenote its funny how many people can creates so much goodness with building or modding files but dont know how to create flashable zips... LOL
dont re-invent the wheel I believe just get a gapps zip and mod away...
OH yea my bad thanks for the rom I too am a big fan of the menu and choose to live with it