Request for V500 boot image - G Pad 8.3 General

Howdy all,
I have downloaded the kernel source for the v500 tablet (lg gpad 8.3), and would like very much for somebody to copy their boot file and send me the boot.emmc.win file. (or it may be a boot.img).
I need the boot.emmc.win file for the ramdisk it contains.
I currently have a kernel with working Gamma correction for the Google Play Edition V510 Here: http://forum.xda-developers.com/showthread.php?t=2647119
And, I was hoping to do the same for the V500 edition. I am willing to see what changes I can make that would be benificial for people, like better battery life, gamma control, smoother scrolling, etc . . .
Feel free to post one here, or private message me and I will give you my email address.
Thank you, sleekmason

I can do it if you have instructions upon how to

While we haven't exactly seen eye to eye on some things I would be glad too help. Would I be able to provide this from a twrp backup? How can I get it to you?
Sent from my LG-V500 using Tapatalk

Thank you to both of you. I sent my email earlier to your private messaging here. Please do send me a copy, it would be much appreciated!

This is the boot.img that's in a backup of the stock ROM that I made using Philz recevery:
https://www.dropbox.com/s/qepievo2w0uboko/v500-bootimg.zip

Thank you everybody! Looks like I've got it! Now to do something with it . . . Stay tuned.

Good luck
Sent from my SM-N900W8 using Tapatalk

So, Check this out; The module I enable in the 510 to get gamma control is "Interface to calibrate LCD color temperature" which is the same one in the 510 that I have enabled to get gamma control on there.
AND it is already enabled in the 500 kernel. this is odd given people say they can't change it. Has anybody tried using trickster mod to change the settings?
There is one other interesting point to this story in that, the lg 500 kernel also has a setting that the 510 doesn't have that is right below the interface setting called "Interface to calibrate LCD color temperature by QLUT" which is also enabled by default in the 500 kernel.
I unfortunately do not currently own the 500 so it will be impossible to test different settings until I get it right.
If somebody with a 500 is using a linux computer (preferably using Debian Wheezy), they can easily follow the guide I wrote to "roll your own kernel" in my signature to compile and test for the 500. The info you would need for the "Anykernel" script to put it back on the 500 device should be present in the ramdisk . . . ?
Sorry I can't do more folks. Without the device it would be silly to post a recompiled kernel I am not certain about. I had hoped that the settings for the 500 would be close enough to simply duplicate, as it is a LGE patch, but no go.
Best regards, Sleekmason

I installed trickster mod. It allows changing of color saturation but don't see a gamma control.
Rolling my own kernel is a bit beyond me.
Sent from my LG-V500 using Tapatalk

Related

[APP] Milestone - Overclock (requires root)

Hi all,
I realize this is a post about a Motorola phone but please bear with me.
As you might know, the Milestone firmware is firmly locked, unlike its cousin Droid. Among many things, this forbids overclocking because we can't change the kernel and unlock new frequencies.
However I developed a solution that allows overclocking by changing key structures directly in the kernel memory in runtime. All you need is a rooted phone; no flashing involved. For this to work, the module must know two memory addresses that are specific to each kernel. Fortunately, Motorola appears to have reused its kernel on most 2.1 firmwares, and I've yet to come across a firmware where it doesn't work by default. Confirmed working are Central Europe, Telus and Brazilian firmwares. Testers are welcome to give it a try.
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone. You may say it's unneeded because you can already overclock; but you must flash a specific kernel to get a particular speed. It would be much better to be able to set any maximum frequency/voltage on the fly without flashing or rebooting. For instance, you could overclock to 1.0 GHz before a browsing or gaming session and then return to a lower frequency like 600 MHz, though still overcloked, for battery savings and safety. It's up to you.
Milestone users can try it out now:
http://code.google.com/p/milestone-overclock/
For the rest of you, what do you think?
sounds fantastic, I'd love to check it out but for the life of me I can't find the page.
If you want to pm it to me, I'll post it.
Nice. Telus Milestone User here. Would love to learn how to do this for mine.
Here is the project link:
http://code.google.com/p/milestone-overclock/
found it. looks like a fantastic idea.
How can we help get the addresses?
awesome .....wht there is no milestone/droid section here is beyond me ....wtf
Because it was decreed months ago by someone and no one seems to like changing their mind once they make a decision in this day and age.....
but it's need to root, could you fix it?
stevecai said:
but it's need to root, could you fix it?
Click to expand...
Click to collapse
what's the problem with rooting the milestone? There's plenty of solutions for that. Just no custom kernel/ramdisk, which this works around by using a kernel module.
hi,
i use the 2.1-reu version on my milestone,
but in order to prevent the 2.1 introduced alarm bug,
i have updated the kernel (only) to the 2.1-telus
(via a sbf).
is possible to use this mod to overlock my phone?
how?
if not, how help you to obtain the addresses?
thank's and continue your great work!
robert
gemini002 said:
awesome .....wht there is no milestone/droid section here is beyond me ....wtf
Click to expand...
Click to collapse
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.
staticshadow said:
XDA is a HTC developer forum, not an Android forum. Google some moto modding sites, i know modmymoto.com is pretty good, found out how to root the Cliq (garbage) there.
Click to expand...
Click to collapse
I have read this explanation several times.
I do not mind, but then because there are subforums dedicated to sonyericsson, hp, etc in xda.
modmymoto is good but the best developers site is, withous any doubt, xda-developers!
Re: milestone-overclock
Xda-developers is for htc and android is for porn.
Welcome to xda btw and great job. Now prepared to be flamed for uttering the M word.
-------------------------------------
sent via xda app from my milestone
ady said:
android is for porn.
Click to expand...
Click to collapse
are you Steve Jobs ?
miragu said:
Hi all,
Now for the relevant part for XDA: in theory this can be applied to any kernel on any other phone.
Click to expand...
Click to collapse
Will the method to find the right address that will be posted at /wiki/Disassembly work with every phone and kernel,too?
Has the app something like a setting where you can just change the address to the one you found with the method above?
Would really love an overclocked 2.1 on the HTC HERO. There is no oc-2.1-kernel for the Hero, yet.
Thanks for the great work, til now!
this is a good via to mod any application.
please, publish the source code of your applicacion ASAP.
thx
Source code for the kernel module released
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.
miragu said:
Hi all,
Thank you for your support. I've just uploaded the source code for the kernel module and also the standalone module itself (it's included in the apk but still). Will write the Disassembly section soon, stay tuned.
Click to expand...
Click to collapse
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx
The overclock.ko is created automatically when you press the "Load module" button in /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko. You don't need to copy it. I'm providing it separately so that people can load/bundle it without ever running the apk.
bartito said:
hi,
i'm interested on include this in my system applications directory,
in order to prevent your deletion on hardreset, and in order to make it available FOREVER
the instructions are that:
cp OverClock.apk /system/app
cp OverClock.ko /system/lib
????
thx
Click to expand...
Click to collapse
ok,
if i'm interested on have overclocking on my milestone after boot the system, and don't interested on manually execute the apk on each reboot, i need only to copy the OverClock.ko to /data/data/pt.com.darksun.milestoneoverclock/files/overclock.ko on boot time ?
but in your wiki page says to execute "insmod overclock.ko max_rate=800000 max_vsel=62"
please, provide me instructions to set overclock in boot time
The module created by the apk is preserved across reboots. However, if you want to run the module completely standalone I recommend you put it in /data/local/overclock.ko and run insmod /data/local/overclock.ko max_rate=800000 max_vsel=62

Nexus 7 Help Thread

Welcome to the Nexus 7 Help Thread
This thread is here to help our community out as best as it can.
Why is this thread here?
There's 2 main reasons really. The first reason is to stop the development threads getting filled with questions which have nothing to do with the thread they're posted in. That then makes the thread go off-topic which is not what a development thread is there for.
The second reason is because there are too many repetitive questions being asked. The main problem with that is the fact that other users will sometimes attack the OP and 'flaming' them.
The main way which this thread will help to stop that happening is by helping you out as much as possible, while being in a friendly environment.
Below you will find the Thread Rules which I expect you all to follow and not to break them.
Thread Rules
1. Remember that while posting in this thread and across the whole site, you must not break the Forum Rules.
2. Even though this thread is for everyone to use, there'll be a lot if new members in here so no flaming or insulting anyone else.
3. As this is a help thread, remember that there is no such thing as a stupid question.
4. Even if you get your question answered by reading the 2nd it 3rd post, be sure to come back here and read some more. It will help you to learn even more.
Hall Of Fame
As I'll be keeping an eye on this thread quite a lot, I'll be adding the people to this list who have been the most helpful and are contributing the most.
1.markj338
2.
3.
4.
5.
Nexus 7 Moderators
If you report any posts, the report will go to our SM (Senior Moderator) and FSMs (Forum Specific Moderators). They are our SM - zelendel and our FSMs - Shreyas Jani, chrisd1a1, GODZSON, Divine_Madcat, babijoee and Moscow Desire. If you have any questions about this forum in particular then feel free to drop them a PM.
In post 2 there will be some really useful links so be sure to check them out.
In post 3 there'll be an FAQ which will help you out aswell ​
Useful Information & Links To Help You
XDA In General
First of all, I'm linking to some general XDA threads which can help you become more familiar with this site and how things run. I feel this is one thing which new users don't realize because they think it's okay to come to this site and post anywhere.
If you don't feel this applies to you, please move onto the Nexus 7 links further down this post.
XDA New User Guide - I can't stress enough how important that thread is. If you follow what that guide says, you'll be well on your way to becoming an asset to the XDA forums.
[HOW TO] Make A Substantial Thread, Post, Question & Poll - This is also a must read thread. Why, you ask? Well it's simple. Reading this will show you the best way to post your thread to ensure that people will respond and be able to help you. Rather than just giving no information or a thread title called "Mah phone brikked. Hlp me plzzz!", following that thread will give you the best chance of being helped.
[HOW TO] Make A Good Signature - This really is needed because as you'll see in a lot of signatures, mine included, is that we list our current devices and what ROM/kernel we are using. This helps people to help us. Take a look at the thread to find out what else to include in your signature.
Nexus 7 Helpful Links
I'll have these threads numbered so if you ask a question and it can be answered by looking at the first thread here, I'll say "Go to post 2 > nexus 7 > thread 1"
1. READ THIS FIRST - Nexus 7 General Section
2. [GUIDE] Flashing a factory image with fastboot/ returning to stock
3. N7 kernel test results (Performance & Battery tests)
4. Nexus 7 All-In-One Development Index​
5. [Index]- 28 Jan 2013 - All for NEXUS 7 - "Nakasig/Tilapia" - (GSM/HSPA+)
6. NEXUS 7 3G-"nakasig"-For all Your Jelly Bean Discussions, Problems and Solutions
More will be added at a later date
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]ASUS GOOGLE NEXUS 7 – GROUPER & TILAPIA (WiFi & 3G)[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: Do I need a toolkit to root this bad boy?....?[/SIZE]
Its a Nexus, imo if you need a toolkit you're either not experienced enough for rooting or too lazy Toolkits are out there and they are really straight forward, but you should get to know how to use fastboot/adb in case you need it. If you don't know what you're doing, you shouldn't be mucking around with your $200+ toy in case you screw something up and don't know how to use ADB or fastboot to restore it​
[SIZE=+1]Q2: I'm thinking of getting this device/I'm new to this device. What are the main problems i should look out for? [/SIZE]
Look through the following threads - Nexus 7 defects? - List of known faults.​
[SIZE=+1]Q3: Which ROM/kernel/recovery etc. would be the best choice for me? [/SIZE]
No-one can answer this for you. We all have our favorites, so just test different ones out and see which you prefer.​
[SIZE=+1]Q4: When I flash my first custom ROM, how come I get stuck in a bootloop? [/SIZE]
While it's recommended that you always do a full wipe before installing, you HAVE to do a full wipe before installing your first ROM. If you don't, you N7 will not boot up.​
[SIZE=+1]Q5: I flashed a new kernel and when I change frequencies, it reverts to stock settings 1.3GHz after a while. WHY??? [/SIZE]
You need a patched PowerHAL. On a very basic level, after a while the stock google PowerHAL likes to revert a lot of settings to stock. This includes the CPU clock speeds, etc. I got my PowerHAL from here
http://imoseyon.host4droid.com/grouper/beta/
And I flashed the nofreq one. It will NOT change your frequency, ever. After you flash the PowerHAL, use your favourite app (I like tricksterMOD, but support your devs by buying their apps) to set your kernel settings, and set them on boot. This is the easiest way to get settings to stick.
OR
You could use an init.d script to set a maximum clock speed. This way, you will need a kernel/ROM that supports boot.img.
http://forum.xda-developers.com/showpost.php?p=35493253&postcount=1366
This is a lot more difficult but it works ​
[SIZE=+1]Q6: How much overclocking is too much? Am I damaging my device? [/SIZE]
No chips are created equally. Some can take more OC than others. It is fact that too much OC can shorten the life of your CPU. A general rule I have seen used a lot is to not go around 20-30% over the stock speed. That is around 1.5GHz which most kernels get up to. However, a lot of devices can take more and will go higher. See for yourself, just don't be stupid ​
[SIZE=+1]Q7: What is the difference between x and y kernel governors/schedulers? [/SIZE]
See here: [GUIDE]Kernel Governors and I/O SCHEDULERS
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs​
[SIZE=+1]Q8: I tried to boot my device into recovery from the bootloader and now it is stuck on the google screen. Is it bricked? [/SIZE]
No. Probably not. Chances are you're on an old bootloader, which has a bug that doesn't allow you to get into recovery from the BL without being connected to a computer. So, connect it to your computer, hold vol down/power for 10 secs to go back to the bootloader. You can go to the recovery from there.​
[SIZE=+1]Q9: On my HTC (whatever) I could transfer files onto my sdcard while in recovery. How do I do it on the N7? [/SIZE]
You can't drag/drop in recovery between your N7 and a PC. Either boot into android and transfer your files, or use ADB while in recovery.
"adb push nameoffile /data/media" or wherever your things are (beware of how many 0's there are on your sdcard).​
[SIZE=+1]Q10: My files on my "sdcard" appear under /data/media/0/0/0/0/0/0/0/0/0/0/0/0/0. WHY so many 0's?? [/SIZE]
Ask Google. It’s got to do with the multiuser feature brought to android in 4.2. Ever user has their own folder, so you might have /0 and /1. If you're having troubles with it in recovery, I would update to the latest TWRP.​
[SIZE=+1]Q11: I’m trying to update my stock rooted modded N7 to 4.2 from 4.1.2 but it won't work. Help? [/SIZE]
You need to be running completely stock to update. So, you need to either flash a stock ROM or the stock image.​
[SIZE=+1]Q12: When I finish watching a video the screen goes weird. Its like, washed out or something. Is my device bricked? Is my screen bricked? [/SIZE]
No. Its the tegra smartdimmer. When your device is playing a video, the Tegra 3 automatically bumps up the contrast and dims the backlight, to save battery. This is a feature. To turn it off, either use a script or tricksterMOD (which is much easier).​
[SIZE=+1]Q13: Battery life on this kernel/ROM sux. I've been using it for half an hour and its dropped 30% already. Why? Restoring to my old kernel..[/SIZE]
When you flash a new ROM/kernel, you need to give it a few battery cycles before battery is reported accurately. So, flash the new kernel, drain it (not necessarily to 0%), charge it fully, drain it again, charge, then play around. Do not complain about battery or anything without doing a few cycles first.​
[SIZE=+1]Q14: I am about to flash another ROM. Do I have to full wipe or can I flash it on top? (Dirty flash).[/SIZE]
Usually you can probably dirty flash. But if it causes problems, don't report them. Best thing to do is to reflash the ROM with a full wipe and see if bugs persist. I always wipe when changing to a different ROM, but when updating a ROM i don't wipe usually.​
[SIZE=+1]Q15: Should I unlock the bootloader when I get the tablet if I am going to root it anyway?.[/SIZE]
I would say no. Because, if there is a problem you have sort of voided your warranty. I like to keep my devices for a month without rooting/unlocking them in case there is a fault or something. You should do the same, I’d hate to have a brand new device, root it and then find a fault and have voided your warranty. Companies can be sneaky and can probably try to avoid fixing your device under warranty if you tamper with it. However you could always relock and revert to stock, but it is much easier to be patient and make sure there are no problems ​
[SIZE=+1]Q16: Will rooting my tablet make it faster/awesomer and have improve battery life?[/SIZE]
Short answer: no.
Long answer: nope.
Rooting alone will not change anything relateds to battery or performance. However custom ROMs, kernels and other mods will change things. For example flashing a more optimised kernel might improve performance, especially if you overclock it. Similarly, underclocking generally improves battery life. Of course it depends on what crap you have on your device too, but that's the general idea. Usually in the OP of a ROM/kernel thread, and in the comments you can get a good idea on whether it is optimized for battery, performance or a combination.​
[SIZE=+1]Q17: What’s difference between N7 “Grouper – Nakasi” and N7 3G “Tilapia – Nakasig”?.[/SIZE]
Wi-Fi (all models) = Nakasi - Grouper
3G/Wi-Fi = Nakasig - Tilapia
The Nakasi/Nakasig is the image (operating system)
and
the Grouper/Tilapia is the hardware build.
Because one of the files for the phone call apk is named "tilapia"
assert(getprop("ro.product.device") == "tilapia"
getprop("ro.build.product") == "tilapia".​
[SIZE=+1]Q18: Can I use same recovery for N7 “Grouper” and N7 3G “Tilapia”? [/SIZE]
Yes, but it is preferable to use a special recovery for the tilapia. You will find 3 special recoveries for Tilapia.​
[SIZE=+1]Q19: What's the difference between "Development" and "Original Development"?[/SIZE]
Here are the rough guidelines as to what should be placed in "Original Development":
*Official release of highly original and upstream custom ROMs (built from the ground up with significant original development within them).
*Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
*A significant "first" in development for a device. This is something which took considerable time/effort and is generally accepted by developers to be non-trivial.
*Kernels which are built with beneficial changes that are not simply pulled from other kernels already available.
*Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
*Significant port of a ROM from one device to another, giving enhanced features or functionality to the users of the target device.
All other development work goes into "Android Development".​
*
[INDEX]All In One Nexus 7 Index Thread (WiFi)
[Index]All for NEXUS 7 - "Nakasig/Tilapia" - (3G/GSM/HSPA+)
[GUIDE][BOOTLOADER][4.2.2] TILAPIA JDQ39 - 4.18 Flash Image Instructions (FOR 3G VERSION)
*Use the thanks button if someone helps you or answers your question*
*Read the sticked threads*
*Google probably knows the answer to your question*
<> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
Forum Rules | New Users Guide | XDA Tour | Report Posts​
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to those who contributed to the production of this FAQ, especially kinfauns, kidcarter93, philos64, ronnie498, fellow RC's, me ​
Good thread, make it a sticky !
At least good helpers will be honoured ^_^ !
Since this thread is for newbie I want to ask , can i use franco kernel on N7 3G 32GB?
nazz.rule said:
Since this thread is for newbie I want to ask , can i use franco kernel on N7 3G 32GB?
Click to expand...
Click to collapse
There is a difference in being new and being spoon fed. You will find your answer in the Franco kernel thread.
Cheers Danny
nazz.rule said:
Since this thread is for newbie I want to ask , can i use franco kernel on N7 3G 32GB?
Click to expand...
Click to collapse
Yes you can
Sent from my Nexus 7 using Tapatalk HD
Thanks to Moscow Desire, this thread is now stickied so hopefully it will be able to help as many people as possible
Sent from my Nexus 7 using xda premium
I got my nexus 7 yesterday and updated it immediately to 4.2.1. All good so far. I start using and all goes well until I remember "this thing has the swipe keyboard, right?". I start swiping and nothing happens. Check the settings, it is on. Boot the device, no effect. Enable and disable the thing and boot the tablet a few times more, still no go.
At this point I decided I'll fix that later and made another user account for my GF to use. I immediately notice that the swipe typing works on that account just fine. I check the settings and looks like it's on by default. I go back to my own profile and check the settings again, but still no go.
Any ideas?
badmoj0 said:
I got my nexus 7 yesterday and updated it immediately to 4.2.1. All good so far. I start using and all goes well until I remember "this thing has the swipe keyboard, right?". I start swiping and nothing happens. Check the settings, it is on. Boot the device, no effect. Enable and disable the thing and boot the tablet a few times more, still no go.
At this point I decided I'll fix that later and made another user account for my GF to use. I immediately notice that the swipe typing works on that account just fine. I check the settings and looks like it's on by default. I go back to my own profile and check the settings again, but still no go.
Any ideas?
Click to expand...
Click to collapse
Its definitely checked on your account?
Try this one as a quick workaround
http://forum.xda-developers.com/showthread.php?p=35596988
Sent with swag from my Kanged Nexus 7
Thanks for the tip. I tried that, but settings crashes every time I try to enable the PC layout keyboard.
I'm gonna do a factory wipe since the tablet is still almost on default anyway.
edit: Ok did reset and everything works just fine now. Now just wait for play store to install all the apps back
I have just got my new Nexus 7 and I want to root my N7 with Wug's root toolkit. I was thinking if I just don't check the box: flash custom recovery. Can I then just do the OTA updates? Because I don't want to install a Custom Rom.
Hi guys!
Just got a stock unrooted unmodded N7 32GB with build JZO54K. On first boot it found the OTA update to 4.2.1 so I happily accepted the update. A few minutes into the upgrade process I get the "dead" droid with the triangle, guess something went wrong. It boots up again into JZO54K and works fine.
I can force another attempt at the update by stopping and clearing the data for Google Services Framework and searching for updates again, but with the same results.
Am I missing something? Would like to try pure AOSP before going CM on this little beauty
How to root Nexus 7 without toolkit?
Root Nexus 7 must flash the CWM or other recoveries? In the menu of "Google Nexus 7 TOOLKIT V4.0.0", I found the button "Root" and the check "and flash recovery...". Does it mean I can root the machine without flash any recovery? Thanks.
AngryGamer025 said:
I have just got my new Nexus 7 and I want to root my N7 with Wug's root toolkit. I was thinking if I just don't check the box: flash custom recovery. Can I then just do the OTA updates? Because I don't want to install a Custom Rom.
Click to expand...
Click to collapse
If you've only rooted you can do ota's. Just as long as you don't change ANYTHING in the /system partition like installing flashable zips
frdd said:
Hi guys!
Just got a stock unrooted unmodded N7 32GB with build JZO54K. On first boot it found the OTA update to 4.2.1 so I happily accepted the update. A few minutes into the upgrade process I get the "dead" droid with the triangle, guess something went wrong. It boots up again into JZO54K and works fine.
I can force another attempt at the update by stopping and clearing the data for Google Services Framework and searching for updates again, but with the same results.
Am I missing something? Would like to try pure AOSP before going CM on this little beauty
Click to expand...
Click to collapse
Sure its completely stock? If it is, it should work... If you be got any more troubles ask Google
If you want pure AOSP there are ROMs for that you can flash, if you root
tmbu said:
Root Nexus 7 must flash the CWM or other recoveries? In the menu of "Google Nexus 7 TOOLKIT V4.0.0", I found the button "Root" and the check "and flash recovery...". Does it mean I can root the machine without flash any recovery? Thanks.
Click to expand...
Click to collapse
You can root by having all the right superuser binaries etc
But its easier to flash the recovery, and then flash the latest superuser/ supersu zip.
Sent with from my Asus Nexus Unicorn
markj338 said:
You can root by having all the right superuser binaries etc
But its easier to flash the recovery, and then flash the latest superuser/ supersu zip.
Sent with from my Asus Nexus Unicorn
Click to expand...
Click to collapse
Thank you for reply. I can understand your second sentence, but I can't understand the first one. Can you say something more? I just want to root the machine without any toolkit and recovery.
tmbu said:
Thank you for reply. I can understand your second sentence, but I can't understand the first one. Can you say something more? I just want to root the machine without any toolkit and recovery.
Click to expand...
Click to collapse
I would recommend flashing the recovery in order to get everything working properly, and to easily recover if something goes wrong
I was wondering whether it's possible to share files between the different users of the same N7? For instance to make video or music files available regardless of who is logged in.
I don't seem to be able to find anyone even discussing this anywhere at all.
Sent from my Nexus 7 using xda app-developers app
opticon78 said:
I was wondering whether it's possible to share files between the different users of the same N7? For instance to make video or music files available regardless of who is logged in.
I don't seem to be able to find anyone even discussing this anywhere at all.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The closest option to that is Multi-User App Share. It doesn't have the ability to share files though. Maybe the creator will make it possible in a future update though
Sent from my Nexus 7 using xda premium
I have seen it in the play store, but I'm not sure how that would make sharing files within the tablet possible, and since it requires rooting I can't even try it unfortunately.
Sent from my Nexus 7 using xda app-developers app

Here is the source code for the LG Gpad GPE (510)

this includes the kernel source. I am in the process of trying to build a gpe kernel. so far I can get into the menu config but cannot make successfully. I'm going to download a different distro with a clean build environment and try again. If anybody else has ideas and/or answers on how to do this successfully please post here.
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv510
my attempt to build a kernel will be to allow for gamma correction and for the addition of ext2 to used on the SD card if possible. I have built kernels for my Linux box before but this is quite a bit more involved.
Will this allow a gpe ROM on the stock LG device
Sent from my LG-V500 using Tapatalk
Canadoc said:
Will this allow a gpe ROM on the stock LG device
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I don't know enough about it yet. one would think that with the source code you could simply build and install GPE on to the framework of the LGE device, meaning the removal of all of the old software in the installation of all new software based on the GPE Kit Kat build.
Apparently, by reading other threads here that is not the case, or they would have already done so. Then again, I did not see anything posted about the source code before now.
Maybe a developer will decide to do something with this, and even better write a tutorial on how to do something that is worthwhile for the GPE. In the meantime I will muddle through.
Just my 2 cents
http://forum.xda-developers.com/showpost.php?p=49468038&postcount=329
Demetris said:
Just my 2 cents
http://forum.xda-developers.com/showpost.php?p=49468038&postcount=329
Click to expand...
Click to collapse
howdy, I like your idea, but I would also like to see more development for the GPE itself. maybe even a separate forum dedicated just to the GPE as right now it seems that everything is spread out, disorganized and very difficult to keep together for one or the other version. Upon this basis it would be easier to see what items and options are available for one device, without being distracted by the same for the other.
That being said, I definitely agree there should be a collaboration to achieve the ends that you desire, as they will also help the GPE users find what they are looking for.
was I able to successfully compile a kernel? Yes! Yes I did!! Arch/arm/boot/zimage is ready!
unfortunately this does not mean an awful lot of this point all I did was change the name of the kernel slightly and if not adjusted anything else nor do I have it back into a boot image but! This is/was the hardest part I think. Reason being the dependencies for getting this done.
I have successfully compiled, and pushed a kernel onto my gpad gpe 510. Now you can too! I wrote a tutorial at : http://forum.xda-developers.com/showthread.php?t=2628951
You will be able to control your device now. No need for a custom ROM if your willing to put in a bit of effort, but I understand if you dont.??

[MOD]Hey Snapdragon! Mod - 4/14/15

Disclaimer
I'm not responsible for anything that may happen to your device. I've tested this mod to the best of my abilities, but I can't guarantee anything. Make a complete backup before applying any of these changes. If you brick your device, boot loop, lose data, or etc...again, I'm not responsible.
CM12 - Working
- CM12S YNG1TAS0YL with stock kernel
- CM12 nightly with stock kernel
CM11 - Working
- CM11S XNPH30O, XNPH33R, XNPH38R, XNPH44S, and XNPH05Q with stock kernel
- CM11, PAC-man, crDroid with most recent kernels
- franco r35 kernel
CM12.1 - Not Working
- CM12.1 nightly (bootloop)
CM11 - Not Working
- LiquidSmooth ROM (mediaserver seg faults immediately)
- OmniROM
Also, I found a commit in the CM source that adds Voice Wakeup options to the Settings app. If the ROM doesn't have this code compiled into their Settings, the mod will probably not work. You'll still be able to go through the training process, however, I don't believe Google Now will launch because the intent action is never being set.
Instructions
1.) Backup any important data on your phone (files, pictures, etc.)
2.) Boot into recovery. I use and have only tested with TWRP
3.) Make a nandroid backup
4.) Flash the mod
5.) Reboot
Recovery
If you encounter any issues (e.g. bootloop) or just want to remove the mod, go into recovery and restore just the System partition from the backup you made earlier (this will preserve your Data partition).
After Installation
After installing, you'll get a notification to enable Voice Wakeup and to train your voice. You can do this now or skip it. It can always be setup later by going to:
CM11: Settings --> Voice Wakeup --> Retrain your voice
CM12: Settings --> Language & Input --> Voice Wakeup --> Retrain your voice
Also...
1.) Go into the Google Now settings and disable "OK Google" detection settings.
2.) Disable your lockscreen if on CM11S or CM12S...other CM11/CM12 based ROMs should work fine since the apk is signed correctly. Some users have reported being able to use a 3rd party lockscreen (e.g AcDisplay) as a work around for CM11S.
If something is not working for you, I need the following or I can't help...
- The ROM you're using (date/version too)
- The kernel you're using (date/version too)
- A description of the problem
- A logcat of the problem in action
Changelog
Code:
[I]4-14-2015[/I]
- New test version for CM12 based ROMs. I believe this should work with most kernels.
[I]Version 2.0[/I]
- CM11 based ROMs only
- Updated mixer_paths.xml with more recent version from CM11
- Deodexed, signed, and zip aligned VoiceWakeup.apk. The app can now bypass the lockscreen on CM11 based ROMs
Disabling the lockscreen is still necessary for CM11S ROMs because those keys aren't public
- Added a "loud" version. It increases the microphone volume levels to make it more sensitive
[I]Version 1.0[/I]
- Initial Release
Woow. It seems working flawlessly
me wanty. Hopefully you can post a how to in the near future
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
jojo_whit3 said:
I bought the OnePlus One in August because I was interested in the always on listening feature that they showed off back in the Spring. So when I actually received the phone, I was pretty disappointed to learn that they took the feature out before shipping. Over the past couple weeks, I've been working on a way to get this feature back in the phone and I think I finally got it working pretty well. I've only tested it on the 25R and 33R builds, but it should work on most ROMs for this phone. The mod uses the always on low power core, so there's no significant drop in battery life. I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here. But in the meantime, here's a demo of it working...
Click to expand...
Click to collapse
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
share it pls!
Overdose1986 said:
share it pls!
Click to expand...
Click to collapse
Did you read the OP?
I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here.
Click to expand...
Click to collapse
Transmitted via Bacon
looks cool, do keep us updated if you are able to share this "legally" or can you pm me the "not so legal" way? LOL
I didn't know I wanted this until now
That looks awesome
I've been trying to contact someone from the Cyanogen team to get some more information about posting this. If anyone has any contact info, either send me a PM or send them over to this thread.
To give a little more information about this mod, its essentially a port of the VoiceWakeup.apk I found here. If you use apktool to disassemble this file, it's easy to tell it came directly from Qualcomm. However, if the Cyanogen team intended to release this apk with the phone initially, then I'm assuming they already have some agreement in place with Qualcomm. So hopefully that also means it'll be ok for me to post this mod in the near future.
26.2man said:
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
You would still be able to download the OTA updates, but you wouldn't be able to apply them since there would be changes to your file system. If you make a nandroid backup in recovery, then anything is easily reversible.
Thanks. Hope you can release this soon.
Sent from my A0001 using Tapatalk
Looks great, wonder if the cm team is working to make it work by choosing you own wake up command. Had it on my find 7a and saying snapdragon was strange
If it's already freely available then it's unlikely to cause any more issues, depends on what did you do to"port" it I guess.
All the cm11s apps have been made available, so if it came from an existing rom I can't really see much of an issue. But I'm not a lawyer
Alternative is to post a walkthrough of your changes to the original.
Sent from my A0001 using Tapatalk
Awesome work, hopefully you're and to post it up for us eventually.
Hi Everyone...I did a little thread cleaning. Please, lets not harass the OP about when this will be released. Like everything else on xda, it will be released when the developer is ready. Just as a reminder to everyone,
yes this is a hackers site, but certain things are not allowed. If the OP wants to make sure that he isn't violating CMs or Qualcomm's Intellectual Property then we should let him do this to his own satisfaction. Nobody
wants to see a modification removed because CM or Qualcomm complained.
Thanks!
This looks really good! Would love to have this feature, keep it up man
If you're worried about posting the modded APK and the IP issues, can you at least let us know what you modded so we can do it on our own?
had a quick play with it earlier,
Cm 11 nightly contains the background libs (except liblisten.so) but there's some java calls missing. Curious that cm have left most of the libs in place.

lollipop/kitkat versions of Low Lying Fruit Kernel (LLFK) for N915T

(6/30/15) Newest LLFK for T-Mobile Note EDGE N915T Lollipop.
Now has TCP congestion control options with default TCP Westwood
This version is flashable using TWRP.
Features:
SELinux=Permissive option
init.d support
adbd insecure
TCP congestion controls: TCP options include Westwood, cubic, reno among others: default is Westwood
Modifications that need to be made when using LLFK kernel
1)In build.prop set
ro.securestorage.support=false
2)For those that use AllShare Cast you will need to do two things.
First, add the following line at the end of build.prop
wlan.wfd.hdcp=disable
second, you need to have the Xposed module Wanum Xposed installed. In Wanum select "security hacks" then check box of Fake system status
Download link:
https://www.dropbox.com/s/6bg9l8qqcmmh83x/llfk_permissive_initd_adbd_tcp_lpop.zip?dl=0
Check below for other information that might come in handy and good luck!
(06/11/15)New Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (lollipop)
I've added adb insecure to kernel. This gives you root access to modify /system on phone from a pc
Features:
SELinux = Permissive option
init.d support
adb insecure
download link
https://www.dropbox.com/s/kr7xb22449p497w/llfk_permissive_initd_adbd_lpop.zip?dl=0
(06/10/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T)
Two new flashable kernels. One for Lollipop the other for Kitkat.
Lollipop: This new version has init.d support so, for example, you can write scripts that run on boot up. (more below).
Features:
SELinux = Permissive option
init.d support
https://www.dropbox.com/s/k8w423ecoj1covs/llfk_permissive_initd_lpop.zip?dl=0
Kitkat:This version now has TCP congestion control options available (e.g. Westwood)
Features:
SELinux = Permissive option
init.d support
adb insecure (allows you to have r/w access to phone's /system from you pc)
TCP congestion control options
Thanks to JT man for testing
https://www.dropbox.com/s/jbifzsuztb73wpg/llfk_permissive_initd_adbd_tcp_kkat.zip?dl=0
Example of init.d script to automatically set SELinux=permissive given here
https://forums.oneplus.net/threads/how-to-selinux-permissive.314120/
couple notes on how-to-selinux-permissive
1)You only need have permissions of /sys/fs/selinux/enforce set to 644
2)Make sure permission of init.d script is 775
One more thing, knox based warnings can be silenced using wanum.
(05/27/15) Low Lying Fruit Kernel (LLFK) for Tmobile Note Edge (N915T) running Lollipop.
For those that miss having SELinux=Permissive on their T-mobile Note Edge running lollipop, here is a kernel
that supports this setting. The kernel is based on the Tmobile Note Edge Lollipop source code. The only thing that was
changed was a setting in the kernel's Makefile to allow the user to choose whether they want to have SELinux=Permissive
as described for the previous Kitkat version of LLFK below.
NOTE: This time around, the kernel is packaged as a zip file than can be directly flashed in recovery.
But before I go any further I need to give credit to @TEKHD for providing a zipped
version of the T-Mobile kernel I could modify and, in addition, for testing it.
Please buy him a well deserved cup of coffee!
Once you have flashed the kernel and rebooted you are ready to set SELinux=permissive by opening a terminal and typing
su
and
setenforce 0
To check it worked, go to settings > About device and you should see, under SE for Android status, that it is now set to Permissive.
An alternative way to change the setting with this kernel is to use the apk SeLinuxModeChanger. Unfortunately this apk is no longer
available at the play store but you can still download it from the F-Droid site.
https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
A third option would be to set up an init.d script if your rom permits it.
I must admit, at the time of this writing, I'm still on KitKat and have yet to try this on my phone. I'll be checking out lollipop soon
but till then, let me know if/how it works. If successful I'll start adding a few more low lying fruit I've picked!
Remember to do a full nandroid back-up before trying this so your phone can return to its original state before trying llfk if needed.
The usual disclaimer applies!
Good Luck!
lollipop LLFK download link:
WAIT! Only one person has tried this version and although it worked for him, I still consider it beta at best. You have been warned!
WAIT! WAIT! One more thing: You need to do the following otherwise you may experience problems with WIFI:
Download the apk BuildProp Editor and use it to set
ro.securestorage.support=false (thanks @TEKHD for checking this)
WAIT! WAIT! WAIT! May be an issue with private mode not working (see http://forum.xda-developers.com/showpost.php?p=61033627&postcount=109 ). I did not have this problem on kitkit. I am unable to test till next week so if someone can check it out that would be great.
http://www.4shared.com/zip/Z8g1u3FHba/llfk_permissive_lpop.html
dropbox link
https://www.dropbox.com/s/ud84t2fc3n9sqdg/llfk_permissive_lpop.zip?dl=0
Below only applies to the KitKat version.
(04/07/15) Update:
Well, I had a little time and decided to add a feature to LLFK. So for now it has the following three capabilities.
1)Allows you to set SELinux = Permissive
2)adb insecure
3)init.d support
Here is the link for the tar file. (follow same instructions given below to install via ODIN):
http://www.4shared.com/archive/2PepSJcPce/llfk_permissive_initd_adbtar.html
Let me know if/how it works...
New features:
The kernel is now adb insecure. This was accomplished by replacing the adbd file in ramdisk with one due to @freeza. Big thanks to him (as in buy him a cup of coffee!) for giving me permission to use it. With adb insecure you can now remount system as r/w from your pc which can come in handy at times.
The kernel has init.d support (Allows you to run scripts from boot) by modifying the ramdisk using the instructions in STEP 1 (Making kernel ready) of the following post
http://forum.xda-developers.com/showthread.php?t=2287540
So this part is done for LLFK
For it to work, the user still needs to make some minor modifications (add a file and create a directory) in their rom. To do this, please follow all 4 parts of STEP 2 (Making Rom Ready) in the same post.
Once you have completed STEP 2 you are ready to try some scripts.
You can search the Internet for init.d scripts to try.
For example there are some init.d scripts in the later half of the following post to give you an idea.
http://en.miui.com/thread-5685-1-1.html
If folks can experiment to see what scripts work I will make a list and post it here.
Seems to work OK on Hyperdrive and Lab Rats (let me know otherwise).
CAVEAT: When testing whether init.d support was successfully implemented I had tried some scripts (like echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb; ) that should have modified some kernel settings at boot up. But as it turns out there are a set of scripts that run after boot up that supersede these settings. These scripts are in the file /etc/init.qcom.post_boot.sh. (some other neat stuff to play around with in there!) If you want those scripts to not take effect you can simply comment them out and then your init.d scripts will work.
The usual disclaimer and Good Luck
Original post 1/30/15
**********************************************************************************************************************************************************************
Hi. I thought I'd give out this kernel which allows one to set SELinux=permissive for a rooted T-Mobile Note Edge with base NK3. This setting is needed if you would like to run Linux on Android and, I believe Viper4Android if you are so inclined, as well as some other specialized apps (for future reference, let me know what apps you use that need this setting). Once you have loaded this kernel you can use the app SELinuxModeChanger, found in the play store, to set SELinux=Permissive and back to Enforcing. Note, this setting is maintained until you change it back in the app (rebooting will not change the setting). Anyways, what I am providing is a gzipped tar file that you can download, gunzip and then load on your phone using ODIN (version 3.07 worked fine for me, goes in PDA). Remember, this kernel is ONLY for the T-Mobile N915T NK3 rom. Actually, I have only tested it on the Lab Rats rom so hopefully it will work on other roms for T-Moble N915T with NK3 base.
As most folks like to have a name for their kernel I've decided to call this the "Low Lying Fruit Kernel" (LLFK) because it only has a minor change made to it. Indeed this kernel is about as low as it goes (lol) as not a single line of code is changed. I only changed an option in the Makefile from true to false. Details are given at the following github site.
https://github.com/mscion/Permissive-Kernel-N915T-EDGE/
Anyways, I've been using this kernel for over 10 days with no problems, but, of course , for those that try LLFK, the usual warnings apply! I am not responisble for anything that happens to your device as a conseqence of
using this kernel. Indeed you have to be crazy to try it as I have zero experience at this! You also might want to read this before you try setting SELinux=permissive:
http://en.wikipedia.org/wiki/Security-Enhanced_Linux
One more thing, while my preference is that an experienced dev make a kernel worthy of the N915T EDGE, I am open to suggestions to make some more modifications assuming the request are somewhat consistent with the philosophy of LLFK.
Thanks to @jimmydene84 for boot.img and @deeznutz1977 for testing!
Don't forget to do a full back up! Good luck!
Kernel Download link: For SELinux=Permissve option only
http://www.4shared.com/archive/oH5fE053ba/llfk_permissivetar.html
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
VenpaCasa said:
Hey that you that working. I was wondering if there was anyway you would make/try to make the same type of mod/kernel for the sprint version. N915P I believe it is. I will be more than willing to help anyway I can.
The reason I need SELinux to permissive is because to use certain bluetooth controller mapping apps u need it on permissive. Specifically the OG Moga Pocket, that controller only works with the pivot app. In order to have android pick it up as a hid controller, I need the app I use to access linux. I really hate to ask but it looks like there's very limited dev for sprint ?
Click to expand...
Click to collapse
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Awesome @mscion
deeznutz1977 said:
Awesome @mscion
Click to expand...
Click to collapse
Thanks! What would be even more awesome is if someone tries it and it works! lol.
I'll flash it now kind sir
mscion said:
Ok, As long as you are willing to test it! Presumably no harm will be done as long as you do a full nandroid back up. Give me a few days to gather files and such...
Click to expand...
Click to collapse
Omg dude if ur really serious, hell yeah I'm willing to test. I'm extremely greatful n lost for words right now. Thanks so much for just attempting ?? at least. Made my day lol
deeznutz1977 said:
I'll flash it now kind sir
Click to expand...
Click to collapse
I hope you mean Odin it! Drum roll please....
mscion said:
I hope you mean Odin it! Drum roll please....
Click to expand...
Click to collapse
kernel is not se android enforcing
@mscion you still had to use the selinux changer app correct?
deeznutz1977 said:
kernel is not se android enforcing
Click to expand...
Click to collapse
Hi @deeznutz1977. Depending on rom, I think when you boot up you will get that message. Please check in settings > about device and see what SE for android is showing. For now I have pulled the kernel because I unwittingly used the boot.img from lab rats rom to pack in my zImage file that allows permissive setting, cause I thought it was not modded. I am currently waiting to hear from @jimmydene84...
deeznutz1977 said:
@mscion you still had to use the selinux changer app correct?
Click to expand...
Click to collapse
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
mscion said:
Yes. Check the OP for more details. Once you have installed this kernel, you have the option to turn permissive on or off with this app. You should also be able to set it from command line as well. May I ask which rom are you using? Also, as I just mentioned I need to check with jimmydene84 about his boot.img...
Click to expand...
Click to collapse
Stock deodexed. And sorry about not reading the op. Don't you know that all of the cool people don't read ops
Sent from my SM-N915T using Tapatalk
@mscion I asked jimmydene to pm you ...
deeznutz1977 said:
@mscion I asked jimmydene to pm you ...
Click to expand...
Click to collapse
Thanks very much! We're all good. I'm putting the link back up shortly.
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
VenpaCasa said:
Got excited for a minute I thought deeznutz1977 said he flashed on a Sprint Note Edge. Had to read it over a couple times.
Click to expand...
Click to collapse
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
mscion said:
Almost there. It appears to have compiled fine. I need to download the sprint rom and extract its boot.img file so I can pack the file for you to odin. Maybe this afternoon...
I will use the sprint deodexed version NK1, to extract boot.img from, that @snovvman has posted in the sprint developers thread. (hope that is ok! EDIT: We're good!)
Click to expand...
Click to collapse
Honestly your awesome. I was starting to regret my purchase too. I'll assume you weren't asking me if it's ok but if you were, yeah that's fine. I'm actually any using that ROM
EDIT: Just saw your edit n thanks (to both) that's so awesome! I owe you guys!
When ubr done are you going to post here or a new thread?
VenpaCasa said:
When ubr done are you going to post here or a new thread?
Click to expand...
Click to collapse
Just pm'd you with link. If it works I'll post it in this thread.

Categories

Resources