Related
This is the latest Sprint Rom based on the latest RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
I have verified that A2SD is working as I downloaded and installed a couple of programs from the market. The programs are being stored in /system/sd/app.
Here's the link: http://www.darktremor.info/files/2.1/2.1-ruu-a2sd-signed.ziphttp://www.darktremor.info/files/2.1/sprintstock-21-a2sd-b-signed.zip
This one now has adb rooted (thanks to nfinitefx45 for his assistance) and does flash (heard complaints on the symlink issue...never sure what causes that, but ended up starting over and porting the files from the previous build).
This is for those people who want to keep with the stock installation but want the addition of A2SD. If you want a customized look, faster performance and A2SD support, I suggest a custom rom. Fresh 2.1.2 or FreshToast is a good one to use.
Note: It will not affect recovery.
Enjoy and I'll answer any questions you may have (if I can answer them).
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
tkirton said:
This is the latest Sprint RUU leak with A2SD support (I used Darktremor A2SD 2.7 since it was easy to add it).
This is definitely an RUU as when I go into adb shell, I get the dollar sign as a prompt rather than the pound sign...I'm pretty certain it is not rooted.
.
Click to expand...
Click to collapse
<<<snip>>>
This makes no sense at all.
Good point about the Rom vs RUU. Edited to correct.
As for the init.rc. Mainly it was init.rc edit.
regaw_leinad said:
did you manually edit the init.rc? and you should mention that this is a ROM, not an RUU
Click to expand...
Click to collapse
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
wctom said:
<<<snip>>>
This makes no sense at all.
Click to expand...
Click to collapse
tkirton said:
Don't look at me...that's what I'm getting. Doesn't make much sense to me, either. I just know if I do adb shell, I don't have root access. But A2SD works fine.
I went ahead and released it since the goal was to get A2SD working...and I did that. Everything else is for a Rom developer.
Click to expand...
Click to collapse
Thanks, I'll just use your boot image for RegawMOD 2.5. saves me a few minutes
working perfectly all apps installed and 132 megs still open internal
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
sandboxlove said:
is it a general consensus that if you want to run a2sd successfully you should use a class6? i currently have a class4
Click to expand...
Click to collapse
right now, I switched back to my class 4 and its working great
nvmchars....
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
sandboxlove said:
i just want to be clear...this is the latest sprint leak? you seriously deodexed the whole thing?
i thought vince was crazy for trying, your completely BANANNAS
Click to expand...
Click to collapse
yeah, i thought I'd post it in here. Didn't think since it's the same thing as he posted but deodexed that I should make another thread.
and yes, the latest sprint leak. you should test this. I can't right now.
Oooh...cool. Enhancements. I like enhancements.
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
tkirton said:
Oooh...cool. Enhancements. I like enhancements.
Click to expand...
Click to collapse
Well, I like your work, so that's for you
did anyone test it out to make sure it boots?
Sorry to be such a noob, but what is "deodexed" a ROM mean?
regaw_leinad said:
tkirton,
here is your exact rom that's in your first post, but I deodexed it. You can add that to the OP if you'd like.
Everyone else, here it is too:
http://www.4shared.com/file/Fm3pXapi/21-ruu-a2sd-deodexed-signed.html
I have not tested it, but it should work fine. Deodexed /system/app and /system/framework
Click to expand...
Click to collapse
Well I flashed it and stuck on the HTC screen. Flashed the non deodexed version and loads fine.
So apparently i f***ed up deodexing lol. I guess that ROM that I did wont work..
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Now that the A2SD stuff is behind me, I'll take a look at that. Flipzmode or Toastcfh may be able to shed some light on how you get this image rooted correctly, especially Flipz since he's using the latest leak for Fresh 2.1.1.
The original goal was to get A2SD working on a stock rom, which I did....but it is rather annoying that it isn't rooted (or fully rooted).
Damage said in his point that it was rooted, but I got the same thing you did...no root when doing adb.
I'll talk to Flipz or Toast and see if they can point me in a direction to go.
nfinitefx45 said:
well just loving this rom, but one question, can we get a updated boot.img with the adb enabled for access as root?
Click to expand...
Click to collapse
well this is a piece from some of the reading I've been doing I beleice this needs to be done with in the boot image. I dont know if this will help in your research,
-------------------------
You also need to modify the ROM update script to change the default permissions for /system/bin/su so it can be used to elevate privileges to root. The script is in $WKD/dst/META-INF/com/google/android/update-script. Open it in your favorite editor and find the line starting with set_perm 0 2000 0550 SYSTEM:etc/init.goldfish.sh and after it add the following set_perm 0 0 04755 SYSTEM:bin/su
=======================
Hi tkirton,
Nice job on this and thanks for all your hard work on everything! I am also wondering what dedoxed means? Is it like where application data is also stored on the SD card instead of on the phone itself?
Thanks!
This is for the DROID 2 ONLY! Do not flash on your DROID 1 please. I will not help you if you attempt this rom on a DROID 1 and will laugh at you.
For all those having a problem install I have updated the update.zip file. Try it out
Things in the rom:
Removed bloatware(Stupid Verizon!)
Added scripts
Many build.prop mods
This rom is fully Deodexed thanks to bizzshow. Thanks
Themse will be ported. The stock theme comes first!
Still has Motoblur, just took my system folder and edited it a lot. This is the first booted build so please report bugs as you find them to my GTalk matt4542
Thanks to birdman for helping me fix my DROID 2 when I screwed up the system.
The known bug is that the backlight wont turn off when you locked the device, the screen is on but black. Please do not report this bug I will fix it in the next release. This release is buggy and is not for normal use.
Btw I don't have a DROID 1 anymore. DROID 2 now. Will try to keep up D1 development.
I have worked my ass off for this rom so just say thanks!
This has the DROID 1 boot animation for a "retro" feel lol.
READ IMPORTANT!
To install need root and koush's bootstrap app. You will need to make a FULL nandroid backup before doing this because if you screw up your system you can restore. After that go into install zip and toggle the zip authentication check off(or whatever it is) because I wanted this release out so quick I didn't sign the package. DO NOT INSTALL VIA ROM MANAGER!
READ IMPORTANT!
Why the hell have you read all this? Just download it!!
HERE IS YOUR DOWNLOAD!!! Don't you just love me for making you read all that?
DOWNLOAD!!! <--- Click me!
FIRST DROID 2 ROM! Hope you love it!!!!!!
If you post this elsewhere link back to this thread! HOPE YOU ENJOY!
By the way here are your scripts
Scripts:
mountsys - mounts system as read/write
unmountsys - mounts system as read only
blockads - blocks ads from apps
showads - shows ads from apps
free50mb - frees internal memory
free75mb - frees internal memory
free100mb - frees internal memory
movecache - moves your cache to your sdcard
swtchba - switches your boot animation (must be named bootanimation.zip on the root of your sdcard)
switchlwp - swithces your live wallpaper (must be named LiveWallpapers.zip on the root of your sdcard)
reboot - reboots your phone
reboot recovery - reboots into recovery
rmbrowser - Removes stock browser
rmcardock - Removes cardock
rmcorpcal - Removes corporate calendar
rmemail - Removes email
rmgenie - Removes genie widget (news and weather)
rmgooglevoice - Removes google voice
rmim - Removes G1 IM app
rmlauncher2 - Removes Launcher2(ONLY DO IF YOU HAVE OTHER HOME APP)
rmlwps - Removes all live wallpapers
rmmms - Removes mms
rmtalk - Removes google talk
rmyoutube - Removes You Tube
For convenience,
http://www.epic.grrmode.com/Epic-Unleashed10-Deodexed.zip
Tell me if you want it deleted and I'll take it off
pics?????????
just curious if anyone is running this yet. i hate being the first to try things out cause it never turns out well for me
Great work! Please pm me and tell you how you built this rom.
When I get back from vacation I'll test this out.
Sent from my DROID2 using XDA App
kwheel596 said:
For convenience,
Tell me if you want it deleted and I'll take it off
Click to expand...
Click to collapse
Thanks for posting it I had to remove the link from the quote because it wouldnt let me post it lmfao
ok so im a noob and this is my first smart phone. i came from a voyager...eww. ive been researching about making a full nandroid backup and am confused by how about doing this. is it the same from a droid x as it is for the droid 2? if someone can point me in the right direction...id appreciate it
heartlessmcfly said:
just curious if anyone is running this yet. i hate being the first to try things out cause it never turns out well for me
Click to expand...
Click to collapse
Bunch of people on DF have tested it. I've tested it throughly so nothing bad should happen. Take a look if you want
Uh, I'd be careful with this one, kids. I haven't tried it myself, nor have I looked at the entire thing, but the {u,}mountsys scripts are wrong.
Code:
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system > /dev/nul 2>&1
1) the d2 uses ext3, so the -t param is wrong (and actually unnecessary)
2) our system block device is mmcblk1p21, not mtdblock4 (we don't even have mtdblock4!)
3) > /dev/nul 2>&1 is extremely very not good - silencing error messages means a load of "HELP IT DOESN'T WORK!" complaints that you can't actually diagnose.
The rest of the rom may be fine, and I can't comment on it's quality/safety as I have very little experience with Android, but the above is clearly incorrect, and if something as important as that has been overlooked, who knows what else has.
heartlessmcfly said:
ok so im a noob and this is my first smart phone. i came from a voyager...eww. ive been researching about making a full nandroid backup and am confused by how about doing this. is it the same from a droid x as it is for the droid 2? if someone can point me in the right direction...id appreciate it
Click to expand...
Click to collapse
Same method as the Droid X. If you have Gtalk add me or just email me at [email protected] and I can help you out
LordLandon said:
Uh, I'd be careful with this one, kids. I haven't tried it myself, nor have I looked at the entire thing, but the {u,}mountsys scripts are wrong.
Code:
mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system > /dev/nul 2>&1
1) the d2 uses ext3, so the -t param is wrong (and actually unnecessary)
2) our system block device is mmcblk1p21, not mtdblock4 (we don't even have mtdblock4!)
3) > /dev/nul 2>&1 is extremely very not good - silencing error messages means a load of "HELP IT DOESN'T WORK!" complaints that you can't actually diagnose.
The rest of the rom may be fine, and I can't comment on it's quality/safety as I have very little experience with Android, but the above is clearly incorrect, and if something as important as that has been overlooked, who knows what else has.
Click to expand...
Click to collapse
I know there are issues with it. It runs fine with bugs. It is just a alpha release, give me time to get everything ready with it.
ljbaumer said:
Great work! Please pm me and tell you how you built this rom.
When I get back from vacation I'll test this out.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
I just did an adb pull of my system folder. It is in the post.
Cool. Sounds like it is time for me to write another how to or something.
Matt, I am interested in learning more about this. I will see if I can get in touch with you.
Understandable, Matt4542, but I'd fix the mount/umount scripts asap, as literally every other script you've provided depends on those (=
darkonion said:
Cool. Sounds like it is time for me to write another how to or something.
Matt, I am interested in learning more about this. I will see if I can get in touch with you.
Click to expand...
Click to collapse
Just hit me up on GTalk, Matt4542.
LordLandon said:
Understandable, Matt4542, but I'd fix the mount/umount scripts asap, as literally every other script you've provided depends on those (=
Click to expand...
Click to collapse
I am gonna work on it
The accelerometer and compass doesn't seem to be working. Just restored to my backup till this is fixed.
SomKen said:
The accelerometer and compass doesn't seem to be working. Just restored to my backup till this is fixed.
Click to expand...
Click to collapse
Sorry bout that. A lot of things are broken.
I did DL it yesterday and DEV. was extremly helpful in all questions I did have. I would recommend downloading 1.1 that's now available.
Great first D2 ROM
What us different about this rom from the stock rom?
Sent from my DROID2 using XDA App
Here is a dump of my /system/app and /system/framework that is deodexed/zipaligned. Its just the directories; its not flashable in CWM. I'll try and put together a stock zip later, but I don't have time at work. If someone else wants to do it, feel free to PM me a link and I'll host it.
For now, developers will know how to use this. In addition, if you feel brave, you can use the following steps:
Prework:
Download the zip. Extract it. Copy the deodex_app and deodex_framework directories to your external SD card.
1) Boot your phone into recovery
2) Mount /system and /sdcard from the mount menu
3) adb shell rm /system/app/*.odex
4) adb shell rm /system/framework/*.odex
5) adb shell cp /sdcard/deodex_app/* /system/app/
6) adb shell cp /sdcard/deodex_framework/* /system/framework/
7) adb shell chmod 644 /system/app/*
8) adb shell chmod 644 /system/framework/*
9) Wipe Dalvik cache from the advanced menu
10) Make sure /system, /data, and /sdcard are unmounted in the mounts menu
11) Reboot. It took about 5 minutes for my phone to boot and then it said "Upgrading Android" or something like that and went through 175 apps or so.
Download here.
ROM developers, feel free to use this to base your ROMs on. Please give credit for the base source of your ROM as always.
Edit: Clarified its also zipaligned.
Awesome!! I wish I was brave enough to try this..
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
pingfl00d said:
So rom does this mean you'll be whippin up a kernel?? : ))))))
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I need the source which is not available yet. I suspect it will be shortly after this is OTA'ed. But yes, once it is, I will be updating my stock-ish
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
rjohnstone said:
Procedure works perfectly.
At "Android is upgrading... " message now
Edit: Home button dead.
Click to expand...
Click to collapse
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
romracer said:
My home button works fine. This seems to be a common problem if you restore with TiBu. Did you do that?
Click to expand...
Click to collapse
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
rjohnstone said:
Only user apps, no system data.
And the button worked prior to replacing files, so I'm curious what was deleted/changed that caused the button to stop working?
Click to expand...
Click to collapse
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
romracer said:
My guess would be something that "Android is updating..." did. I'm still not entirely sure what that is doing.
Click to expand...
Click to collapse
Most likely... no biggie.
Factory reset should take care of it.
Worst case, I have a nandroid backup.
Edit: factory reset didn't fix it... time for a restore.
I will try and add this too a zip. Thank you
EDIT:
I added this to my ROM. I am still working on ironing out all of the issues, but this helped!
http://forum.xda-developers.com/showthread.php?t=1566820
And if you want to mirror that would be amazing.
that actually worked perfectly! although you should probably add in there that people can use emmc instead of sdcard if they dont have an external card (i dont).
Thanks for this.
Sent from my SAMSUNG-SGH-I727 using xda premium
thanks
I waiting for .Zip flasheable
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
I do most of it by hand. I'm a Linux/Windows System Administrator by day, so I'm comfortable with the command line I do use Cygwin for just about everything though rather than the Command Prompt.
promiseofcake said:
Thanks romracer, always run into issues with the kitchen. I'm going to try your classpath includes in a sh script and see if it works where the kitchen hadn't.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
The one liner I pasted in the other thread should work for both app and framework. It has more includes in the class path than are necessary for framework, but I don't think it'll break it.
It assumes the following:
You are in a directory with app, framework, deodex_app, deodex_framework and tmp subdirectories. app and framework contain the originals from the phone. The one liner should be run from this top level directory. I'd recommend doing framework first. You'll also need to Google java.awt.jar and put it in the framework directory too. Don't upload this to your phone though, its just needed for deodex'ing.
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
mjwhirly said:
if you don't mind me asking, how did you come across deodexing this rom? I know others were having troubles doing so. Also how did you zipalign it? I zipaligned my leak by using rom toolbox pro, did you use the kitchen?!?!
Click to expand...
Click to collapse
i think the problem most people are having isnt related to the deodexing (anymore) but trying to flash it in CWM. it seems that flashable zips are messing up everything, as i used the same files i tried flashing in a zip this way and it works now. the zip version was unusable.
quikt said:
finally abit stable with these deodexed files
flash ics leak through odin
boot into android and get past the attready2go
flash cwm through odin
copy your deodexed files to sd and boot into cwm
follow your adb commands to copy and replace
reboot
only problems were superuser being a pain to flash in cwm. someone else mentioned toggle signature verification which is just before choosing your zip to install in cwm. looks good now.
Click to expand...
Click to collapse
That's basically exactly what I did (and my phone seems stable). Thanks for typing out the parts I left out
I've always had to flash the Superuser zip twice for some reason. I just flash it twice right on top of each other (without rebooting, exiting CWM, etc). Never have any problems in the actual OS doing it that way.
Grab the official Superuser zip from goo-inside.me/superuser
Hi everybody! I've switched over to CM 10.2 M1 as my daily driver, but I missed being able to change the volume on my tv with my phone. So, I've managed to get the QuickRemote app from the stock ROM working on Cyanogenmod (and hopefully other AOSP roms). There is nothing carrier-specific in this, so it should work on all variants.
Luckily there is no kernel module involved in driving the IR hardware. Instead the IR chip is a black box that is controlled via an internal serial port interface. The QuicksetSDK.apk package includes the code to control the IR chip. It creates a Service that the LGQRemote.apk app binds to to send commands to the IR hardware.
Installation
This will only work on rooted devices.
To get this working you'll need to install two APKs:
QuicksetSDK.apk
LGQRemote.apk
You'll also need to add a script that runs on device boot.
You can download mine here: 10QuickRemote
Or just make one yourself, containing this code:
Code:
#!/system/bin/sh
chmod 666 /dev/ttyHSL1
setprop persist.sys.lge.eula_agreement true
This makes the serial port accessible to non-system processes. On the LG stock rom the QuicksetSDK package runs as the system user, but here we're running it as a normal unprivileged user, so we need to make the serial port world-readable and writable. We also use the 'setprop' command to tell the QuickRemote app that we've agreed to LG's EULA, otherwise it will attempt to launch a non-existent EULA activity and crash.
I'm not 100% sure how the init.d system works on other AOSP roms, but on Cyanogenmod, you can place this script in the /data/local/userinit.d directory (creating the userinit.d directory if necessary). The script should not have an extension, and should be executable.
A quick method that works on CM, assuming you've downloaded my 10QuickRemote script to your current directory:
Code:
adb root
adb shell "mkdir -p /data/local/userinit.d"
adb push 10QuickRemote /data/local/userinit.d
adb shell "chmod 755 /data/local/userinit.d/10QuickRemote
For the above to work, you'll need to enable root for adb in Settings > Developer Options > Root Access
After a reboot, you should be able to use the QuickRemote app just like on the stock ROM!
If the app crashes right away, or if it launches but won't send any IR commands or learn new ones, your start-up script probably isn't being executed properly. Try running it manually and see if things work:
Code:
adb shell
--- inside adb, as root:
# sh /data/local/userinit.d/10QuickRemote
# ls -l /dev/ttyHSL1
-- result should be:
crw-rw-rw- system system 245, 1 2013-11-06 08:20 ttyHSL1
# getprop persist.sys.lge.eula_agreement
-- result should be:
true
If running it manually works, make sure the script is executable or it won't be called automatically on boot:
Code:
-- inside a root shell
# chmod 755 /data/local/userinit.d/10QuickRemote
If it is executable and still doesn't work after a reboot, and you're running a non-Cyanogen ROM, they probably do init scripts differently. Hopefully you can google up how to make it work
If everything looks correct and it still won't work, send me a logcat and I'll try to figure it out.
Enjoy!
sefnap said:
Hi everybody! I've switched over to CM 10.2 M1 as my daily driver, but I missed being able to change the volume on my tv with my phone. So, I've managed to get the QuickRemote app from the stock ROM working on Cyanogenmod (and hopefully other AOSP roms). There is nothing carrier-specific in this, so it should work on all variants.
Luckily there is no kernel module involved in driving the IR hardware. Instead the IR chip is a black box that is controlled via an internal serial port interface. The QuicksetSDK.apk package includes the code to control the IR chip. It creates a Service that the LGQRemote.apk app binds to to send commands to the IR hardware.
Enjoy!
Click to expand...
Click to collapse
thanks so much!!
would it be possible to make this into a flashable zip?
just a quick question am i suppose to see the list of make and models? if so i dont see it... the remote is installed though
nvm... some how the list came out.. not sure what i did. thx for the mod
blkghost22 said:
just a quick question am i suppose to see the list of make and models? if so i dont see it... the remote is installed though
nvm... some how the list came out.. not sure what i did. thx for the mod
Click to expand...
Click to collapse
I have the same issue. You just keep playing around with it?
Sent from my LG-VS980 using Tapatalk
steveo17 said:
I have the same issue. You just keep playing around with it?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
blkghost22 said:
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
Click to expand...
Click to collapse
Right i installed it by clicking the apk and installed it like normal. And now it works
Sent from my LG-VS980 using Tapatalk
steveo17 said:
Right i installed it by clicking the apk and installed it like normal. And now it works
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
for some reason tho... once i reboot my phone. i need to install that again.
awesome job!
I've been leery of flashing a custom rom for the lack of IR and other features. Plus I'm really digging the stock rom.
But with AOKP coming soon, I am might be tempted. Good to know that the application works with directly with the IR blaster.
I thought AOSP 4.4 was suppose to have support for IR blasters, but it seems noone has them working on CM yet.
blkghost22 said:
for some reason tho... once i reboot my phone. i need to install that again.
Click to expand...
Click to collapse
Same here
Sent from my LG-VS980 using Tapatalk
blkghost22 said:
yes.. but honestly i really dont know what i did... the last thing i did was try to make a universal remote and just cancelled out of it... and installed the sql...apk
---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------
just figured it out.. the •QuicksetSDK.apk is not running at first.. so i just reinstalled it again... and the list comes up... for some reason i guess it doesnt start.
Click to expand...
Click to collapse
The list is actually downloaded by the QuicksetSDK app at runtime. I guess they did it that way so they could add models after shipping the phone.
I hope make flash.zip it is easy
Set this up on my D801, works great! It's a little difficult to navigate sometimes because some of the coloring of menus is designed for the stock rom. It seems to be missing the Comcast cable box settings though, it could be possible the app is different on different phones. Either way I just made it "learn" buttons over my TV remote which works way better than the short while I had it on the stock rom. This is the only feature I miss at all from stock, now my phone has every feature I want!
It's really not difficult to use a little terminal/command prompt, people are scared of putting in commands for some silly reason. If you've used ioroot, you already have adb to use too.
nice job!
i made a quick flashable zip package:
http://www43.zippyshare.com/v/86147127/file.html (new slim mod)
-> http://forum.xda-developers.com/showpost.php?p=47500016&postcount=94
(installs in data partition so it should survive a rom update)
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
I get this
Sent from my LG-G2 using XDA Premium 4 mobile app
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
I tried flashing this zip and working fine on mine thank you!
Sent from my LG-D802 using xda app-developers app
RieGo said:
nice job!
i made a quick flashable zip package:
http://www60.zippyshare.com/v/62581043/file.html
(installs in data partition so it should survive a rom update)
Click to expand...
Click to collapse
Flashable works gr8 here as well.... have not rebooted to make sure everything sticks though... tnx guys!
zplit said:
I get this
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
which recovery?
which rom?
did you do a manual installation before flashing the zip?
thank you SO MUCH sefnap! and thank you RieGo for the flashable zip. just flashed on PA 4.3 for D801 and everything is working beautifully.
and as mentioned above- if there's any way you could get the lg camera to work, too, you would be the king. it looks like some sort of progress has been made over in this thread. the AOSP camera works well, but i'd love to have the manual focus option, and so on.
thanks again for adding this great functionality back for us! :good:
Thanks. Flashable zip works perfectly with slimbean on D801. This was the only thing I was missing with AOSP. Thanks again
LG D801 on Slimbean
A camera port with official firmware LG can not? If you can, do it please.
And that zip up to 160 MB? Driver? Replacing the files?
This should probably go in some general Q&A forum, but this is by far the most helpful community I've come across so I wanted to try here first. I've finally got my Ubuntu box up and running again (upgrading to 14.04 wasn't pretty) and was able to build for both my 700t and my n5 without error, but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen? I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible. Any insight you may have would be most appreciated.
Thanks in advance!
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Sent from my ASUS Transformer Pad TF700T using Tapatalk
psudeke said:
but I'm afraid to pull the trigger and flash it. I'm building straight CM for the tablet and AOSP for the phone, so what is the worst that could happen?
Click to expand...
Click to collapse
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
psudeke said:
I haven't gotten either of them to run in the emulator, but I'm not completely sure that is even possible.
Click to expand...
Click to collapse
That's normal - ARM devices are just too different, and the emulator is just another different device.
psudeke said:
Just thought of this, since I'm running Crombi ROM2SD, could I just install my zip on external, and then refresh the right kernel?
Click to expand...
Click to collapse
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
_that said:
The worst thing that can happen is that you brick your device, but you must do something sufficiently stupid for that to happen. I can't say anything about your phone, but for the TF700T, as long as you have a working recovery, flashing a ROM won't brick it. You may want to create the nvflash blobs if you want to have another safety net - it is possible to brick the TF700T if you force it to boot to the recovery and the recovery is broken.
That's normal - ARM devices are just too different, and the emulator is just another different device.
See my Android dual-booting thread in the dev subforum. I originally developed ROM2SD to be able to test my self-built ROMs without breaking my working installation.
Click to expand...
Click to collapse
Thanks _That, I appreciate your help! After reading your post and the f2fs post, i thought i was in the clear, but i still managed to screw something up. i'm unable to get the tablet to boot off of external, regardless of whether its my ROM or CROMBi. I see a "segmentation error" listed in the output from the the preinit, and then it always boots to internal. I thought maybe i got the mount points reversed in recovered, so i reflashed recovery, but no luck. i also tried deleting the preinit script and then reinstalling CROMBi, but i still get the same error. any thoughts?
psudeke said:
I see a "segmentation error" listed in the output from the the preinit
Click to expand...
Click to collapse
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
You still get that fault with a static busybox but it seems to copy files fine.
@psudeke you can compile the static busybox yourself simply with make static-busybox in your build folder - or just steal mine from /system/boot
sbdags said:
You still get that fault with a static busybox but it seems to copy files fine.
Click to expand...
Click to collapse
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
it comes from the ls -l /init* which indeed doesn't have the busybox prefix but if I do it gives some other error I forget now
Anyway it doesn't harm the boot process - just an error message
_that said:
For some unknown reason, dynamically linked executables don't work for preinit in KitKat. So if your *internal* ROM is not stock 4.2-based (I have no data about 4.3), the only way to run a preinit script is to use a statically linked busybox.
Click to expand...
Click to collapse
_that said:
Your fault may come from one of the programs that you call in your script (did you forget to prefix some line with "busybox"?).
Click to expand...
Click to collapse
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
psudeke said:
Internal is the 5/17 build of Crombi, and its a brand new install. with a full format of the data partition (which in my haste to get this working yesterday, i wiped out my nandroid from right before i tried this).
is there any connection between when the internal is flashed compared to the external? in other words, if i reflash the internal rom, it should still recognize an existing external rom? hope that makes sense, i'm still shaking off the effects of a little too much whiskey last night.:laugh:
Click to expand...
Click to collapse
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
sbdags said:
No currently if you reflash internal it will only see internal. You need to reflash external for that to work.
Click to expand...
Click to collapse
Ahh, thanks sbdags! that fixed the issue with ROM2SD. i got that impression when i pulled the preinit and saw it only had an entry for internal. but, i'm still very much in a learning phase so i didn't want to jump to a conclusion.
and after getting crombi to boot on external, i swapped sd cards and my build of CM11 actually booted! now the real learning process begins as i figure out how to customize it.
Thanks again to both you and @_that, you guys are the best:good:
@sbdags and @_that
Just wanted to thank you both again for your help. After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
https://www.dropbox.com/s/khq17h04b715eyd/C11%20Benchmark%20ART.png
Hats off to both of you! :good:
--- Guess I can't insert an image directly from my DropBox, link is to a screenshot of my score ---
psudeke said:
After much trial and error, i was able to build the 5/27 version of CM and merge in that's 9 f2fs kernel, its running well so far. not a bad quadrant score for someone who doesn't know what they're doing!
Click to expand...
Click to collapse
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
_that said:
Congratulations! If you can build a working ROM from source, you're already in the top 1% of people here who know what they're doing.
Click to expand...
Click to collapse
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
psudeke said:
Good to finally be a "One Percenter" in something! :laugh:
Thanks again for your help, I'm sure that was the first of many questions I can't figure out.
Click to expand...
Click to collapse
Just ask away and congrats! :good:
sbdags said:
Just ask away and congrats! :good:
Click to expand...
Click to collapse
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
psudeke said:
Be careful what you wish for, I've got a laundry list of questions ranging from basic Linux commands to the nature of the multiverse, lol.
I do have one question out of the gate about the update-binary file. I'm trying to add a couple apps to either the system or data folders, but I'm not sure what commands are available from the stock CM file. I think for the most part by looking at your updater-script file I can figure out the commands to do what I want, but given the little I know about this and the size difference of the binary file between CM and the one i was looking at of yours, I'm curious. Is the best way to see what's available CM's git? I basically just want to install a different Launcher and Viper instead of DSP manager for sound. Do I need to study up on edify to look at the binary or is there an easier way?
Thanks again!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes your unwanted apps
note apps can be installed into 2 folders /system/app or /system/priv-app
similarly you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
sbdags said:
yes the easiest way to do it is just make 2 folders with your extra apps in it say /extras/app
then add the following to the updater-script (you don't need to touch the update-binary unless you start using aroma)
package_extract_dir("extras", "/system");
delete("/system/app/DSPManager.apk");
delete("/system/priv-app/Trebuchet.apk");
What that does is copies the extras/app folder into system and deletes you unwanted apps
note apps can be installed into 2 folders /system/app or /systempriv-app
similar you can install your user apps into /data/app but this is dangerous with launchers as if the user manually uninstalls it you can't do anything on the tab
Click to expand...
Click to collapse
Thanks again! i can see how this becomes addicting fast :fingers-crossed:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
psudeke said:
@sbdags do I need to mount data before installing anything to the /data/app folder? I saw in your updater-script this line, and i'm assuming i need the same:
Code:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p8", "/data");
one other quick question (hopefully), I saw in the XDA WIKI that i can possibly test the script using the update-binary, do i have to do this on the tablet itself? i spent all afternoon trying to fix a problem that amounted to an errant quotation mark in my script (and i knew it was something like that too. too many years of non-terminated string errors to not look there first:laugh, but the only way i could find to test it was to rezip the file and flash. any suggestions?
thank you good sir! :highfive:
Click to expand...
Click to collapse
just zip the /meta-inf folder, and flash that to test. obviously comment out any format commands as they will fail. That is what I do.
Hey @psudeke you ever need any help with anything to do with source or git let me know
I am also willing to help out
and just a FYI be careful of @sbdags :cyclops: LOL
Just kidding....
Let me know thx Josh