yashsingh1/xdaforums huggingface dataset:
[Defy Q&A, Help & Troubleshooting] Nemado:
Bottom line is, the playstore has a convenient auto update feature which Slimroms disables. His brother would have to go to slimroms.net to download further playstore updates. Besides, Slimroms.net could stop supporting the ROM at any time and he would be "stuck" with an outdated playstore. It would work but he would have to pass on any new features or fixes. That's something to consider.

Second thing to consider, every ROM is based on Quarx ROMs. This means that every custom ROM is likely to have Quarx's bugs AND the bugs of the cutomized ROM.

4.3 performs well but it is not 100% functional. I've read they had troubles with bluetooth and I found that some options don't work (adding APN for instance).

4.1.2 is mostly functional but it's not 100% stable. I had several reboots on a fresh install.

Epsylon's latest 4.0.4 is still a good pick. I just installed it and it performs better than JB on Kingdom Rush (it stuttered, crashed and reboot on JB and worked flawlessly on ICS!)

CM7.2 is awesome in every aspects BUT it doesn't have HWA, which means he won't be able to use some of the latest app. Of course, it doesn't mean much since the Defy is not very powerful. But there are some good HWA only apps that still work on the Defy.
[Defy Q&A, Help & Troubleshooting] CodeVanya:
I'll say Xperia D3.4 for Defy/Defy+ based on Quarx's CM10 (20130117). It's fast, clutter free, and stable. A very good music player, stable camera, and lots of other addons. Battery life is also not bad. :)
[Defy Q&A, Help & Troubleshooting] pgreed:
Because AndroidOS is a chopped/adapted Linux for every hardware (it doesn't contain large drivers library for space economy) is per se a not very stable OS. Even the original firmware isn't "very" stable so the various kind of mods is unstable either. Every mod ROMs is made to cover some aspects and for this cause you must pick the most appropriate for your needs. For beginner try to accomodate with original firmware first, after that try a CM7.x and if you wanna adventure pick a JB or a KK mod. Enjoy.
[General Questions and Answers] alexsx06:
CWM recovery device support on Rockchip RK3168?

Rk3066/rk3188 Yes

Rk3168 No CWM, but on this platform a lot of cheap tablets and boxing tv.

CWM from RK2926/RK2928 not suitable, but has the same resolution and block structure almost identical

RK3168(Cube U25GT Pro, Acme TB706, tablet mid-808a thx,Bliss Pad R7014,SKY Labs 7" ,Mystery MID-721,IconBit NETTAB SKY III,Bliss Pad R7014,HSD-7006,KNC MD706,newest R718,MID ZM706CE,Yuandao N70 S,,..........)
[General Questions and Answers] gusarg:
I have also a RK3168 based tablet, 7", 1GB Ram, 16GB internal, Android 4.2. I've tried many CWM based on Rk3066 and Rk3188 (whish this is more similar to Rk3168) but not look. The closed one (that at least booted into recovery, but with errors that can't mount block devices) was the RK CW Generic from androtab.info.

Any help? Thanks.
[General Questions and Answers] r3l4x_pt:
i have a archos 101 cobalt with 3168 and ive managed to port the 3188 version. try this

1. unpack stock recovery and cwm rk3188 recovery

2. copy stock recovery init file (not init.rc just init) and put on cwm

3. open stock recovery etc\recovery.fstab and copy mount points to cwm etc\recovery.fstab

4. pack cwm recovery and flash(idont know if makes difference but ive flash everything not only recovery)

5. if it doesent work copy stock rk30xxnand_ko* and rk29.ipp* to cwm and try again

the only problem my cwm port has is that i cant find a way to acces internal sdcard but nandroid works fine

hope it helps
[General Questions and Answers] dungleanh83:
Custom rom for bliss pad r9733 rk3066 rk30sdk ???

I need custom rom bliss pad r9733 rockchip 3066??thankyou!
[Nexus 5 Q&A, Help & Troubleshooting] PaulB007:
Is there a way I can modify the phone application so that I can unchecked "show notifications?" I feel if I could do that I could stop the persistent voicemail notification on Sprint. Currently the option to unchecked it is greyed out.
[Nexus 5 Q&A, Help & Troubleshooting] gsteelx:
Not 100% sure about this, but if you get a 3rd party visual voicemail app, wouldn't that override the Sprint voicemail notifications all together, and then you can simply use the Visual Voicemail App for your voicemails?
[Nexus 5 Q&A, Help & Troubleshooting] PaulB007:
Yeah, I have tried this and have even called sprint and had them entirely disable my voicemail service and still that voicemail notification persists. I know its tied into the phone apk somehow and that there must be some line of code I can edit and push, but I have no idea what that might be or how to do it.
[Galaxy S III Q&A, Help & Troubleshooting] odoss:
Hi guys,

I've found a werid bug i don't kniw if you guys have it but when i play a Youtube video, after some minutes the phone freezes and youtube crash after a minute or more...

This was happening also with my previous jellybean rom 4.1.2 so i tought it was a problem with the rom and i've changed it with ProBam v1.1 ( kitkat 4.4.2) and it's an awesome rom, but the same thing happens again with youtube crashes :eek:

I've tried cleaning Data + Cache with no luck...

Any help guys :(
[Galaxy S III Q&A, Help & Troubleshooting] odoss:
Ok guys i've found why :

The damn youtube app is buggy ! i just tried an alternative app for youtube like supertube pro, and it's heaven now NO FREEZES AT ALL FINALLY and it includes all youtube quality and features and better player too, it was hell searching about the real cause, and it seems that youtube team doesn't care about fixing their crappy app !
[Galaxy S III Q&A, Help & Troubleshooting] Jumaqidi:
My youtube app nvr crashes...

Sent from my GT-I9300.

Give a thank if i helped you. :)
[Galaxy S III Q&A, Help & Troubleshooting] odoss:
That's weird cause mine does in jellybean roms and cynogenmod too.
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
Reserved!
[AT&T Samsung Galaxy S 4 Android Development] upndwn4par:
Very nice work. Wish I had a MF3 device so I could try it. :)
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
Thank you [MENTION=2471504]jeboo[/MENTION]. I'll see what I can do with this :)
[AT&T Samsung Galaxy S 4 Android Development] dadsterflip:
Nice job man!
[AT&T Samsung Galaxy S 4 Android Development] hobbit19:
it will help to crack the bootloader note 3?
[AT&T Samsung Galaxy S 4 Android Development] budding_developer:
This also works on the I545 with MI1 kernel...

This is directed at [MENTION=4243514]Hashcode[/MENTION] and [MENTION=2471504]jeboo[/MENTION]:

Guys, I just tried this on my I545 running the MI1 kernel, and it works. I am running Hyperdrive RLS 10.2 with the ATT compatibility pack (using AT&T service) -- but as you know, I am still stuck on the stock Verizon MI1 kernel. You should know that I flashed Hyperdrive over the stock ROM -- that's the only way (at the time) I could get it onto AT&T service here in the US.

My immediate question is how will this allow me to completely replace the stock kernel with something like the Infamous 4.6 OC kernel? I am just getting into this phase of development, so I am not as up on this as you guys are. I know every time I flash the Infamous kernel, the flash in SS seems to work -- but the phone always reboots to the stock 3.0.4 verizon kernel.

Of course, I had another thought, too -- I wonder if it is possible to use this to allow us to insert a module that does something similar to the Motorola Trust Zone unlock? Just another item for your consideration...

Here is a screen capture of me running bypasslkm:

=============================================

130|root@android:/data/local/tmp # ./bypasslkm

BypassLKM patch by Jeboo

usage: -r will restore kernel to original

Big thanks to fi01 & CUBE for their awesome CVE-2013-6282 exploit source!

ro.build.product=jflteatt

ro.build.displayid=JDQ39.I545VRUAME7

Patching kernel @ 0xC00B9C28: unsigned modules can now be inserted.

Done.

root@android:/data/local/tmp # ./bypasslkm -r

BypassLKM patch by Jeboo

usage: -r will restore kernel to original

Big thanks to fi01 & CUBE for their awesome CVE-2013-6282 exploit source!

ro.build.product=jflteatt

ro.build.displayid=JDQ39.I545VRUAME7

Patching kernel @ 0xC00B9C28: restoring original value.

Done.

root@android:/data/local/tmp #
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
I have an AMDL S4 so I'm already running AOSP ROM's, so I've never really paid attention to the problems which the newer S4's face.

Does the OP have a patch that allows the newer S4's to run AOSP now also?

Sorry if it's a stupid question.
[AT&T Samsung Galaxy S 4 Android Development] budding_developer:
Not quite yet...

Not quite yet -- but this is looking extremely promising!!
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
OP has an exploit that lets us load unsigned kernel modules. This means we can try to load up a kexec module, which would then load in a kernel over the stock one. So possibly, if it can be implemented.

SS does not actually flash kernels, which is why it reboots to stock. The way this will allow you to run a different kernel is by loading in an unsigned kexec module and loading the new kernel over the stock one using that module. As for the Trust Zone unlock, someone with more real dev knowledge than me will have to look into that.
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
Careful running this on unsupported kernels..I didn't add any sanity checking.
[AT&T Samsung Galaxy S 4 Android Development] budding_developer:
Didn't figure you did at this early stage... I am well equipped with everything I need to restore (short of JTAG, of course)... thanks for the warning, though! :)
[AT&T Samsung Galaxy S 4 Android Development] jball:
I know it's early but are there any Modules handy for testing

SAFESTRAPPED ATT MK2 I337 S4
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Too early, give it a week or so.. it's a long process being that no one is doing it full time...

Then again it's Christmas time, so maybe a few weeks..
[AT&T Samsung Galaxy S 4 Android Development] jball:
I've done some reading on it and trust me I do know it's not an easy thing for you and me.i don't put in development hours as I'm not a developer.i just want to Contribute anything I can even if it's just my phone.if you asked my wife I live and breath XDA .Thank you all for the Hard work your doing an awesome job

SAFESTRAPPED ATT MK2 I337 S4
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
I'd be willing to contribute my phone too :).. even more since there's work around to odin bricked phone back on mk2 :)
[AT&T Samsung Galaxy S 4 Android Development] cerobles1:
What work around are you refering too? I thought there was no way to odin to MK2.
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Let's not clutter this thread.Look it up please
[AT&T Samsung Galaxy S 4 Android Development] USBhost:
i don't mean to be a noob but will this work on mf3?
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Ask in another thread please..and we don't know, but there's a good chance yes..

Again..please only developers post on this thread!! Keep it clean!!
[AT&T Samsung Galaxy S 4 Android Development] Surge1223:
Thanks! Just cross-compiled and loaded Lime. After I dump the ram, ill start working on getting more stuff over to our device. Have you been doing anything module related lately?

Edit: Successfully compiled lime.ko from kernel source and dumped the ram --couple gigs worth. FYI after a few tries of uncommenting lines in .config, modifying lime.c, and writing my own makefile instead of using limes, I was skeptical that it would even successfully compile the module. Not only did it compile but it loaded and worked as well, dmesg showed the tz accepted it and lime successfully created the dump.
[AT&T Samsung Galaxy S 4 Android Development] cyrushehe:
Just to be clear...

Just to be clear, could this lead to allowing AOSP based roms on MJ7/MK2 Galaxy S4 devices?
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
Theoretically, yes.
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
Ok heres a better just to be clear question, Is there anything that a Loki Device can do with custom kernels that we cant do with kexec/thisexploit.
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Loki already makes it possible to load custom kernels, therefore allowing kernels to load that loads unsigned modules. So no, this won't give you anything more at all.. You already got everything :P
[AT&T Samsung Galaxy S 4 Android Development] Easton999GS:
So if I download the 4.3 Ktoonz kernel. extract the modules from the zip. and try to load them with this exploit I will essentially be running Ktoonz kernel with all features?
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
You don't need this exploit, the ktoonz kernel should read unsigned modules anyways. Yes to flashing the modules though. I wouldn't flash modules unless you know what you're doing. You'd want mdl modules if on a Loki device. Most all kernels made for the i337 are already set up for mdl, so it's kind of pointless.
[AT&T Samsung Galaxy S 4 Android Development] cyrushehe:
How long could it be before an implementation of this for the average user on XDA? Days? Weeks? Months?
[AT&T Samsung Galaxy S 4 Android Development] RK:
Your guess is as good as anyone else's. All I know is that [MENTION=4243514]Hashcode[/MENTION] knows about this and is trying to get kexec working using this.
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
NICE work so far man! I get back home this weekend, I will definitely start debugging things so we can make progress on this project. :)
[AT&T Samsung Galaxy S 4 Android Development] ryanbg:
[MENTION=2471504]jeboo[/MENTION] would you be able to modify this exploit to also enable the ability to use insmod? if the kernel was vulnerable, it's technically possible right?
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
That's exactly the point of the exploit.
[AT&T Samsung Galaxy S 4 Android Development] ryanbg:
Okay, I thought it was to patch lkmauth, I didn't realize it enabled kernel modules too. I'm combing through MI9 zImage now.

edit: I don't think I was making myself clear, I mean enable insmod as it's not implemented in N3 kernels.
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
Ah, I was wondering what you meant..I havent looked at how they disabled it.
[AT&T Samsung Galaxy S 4 Android Development] ryanbg:
If you get any free time and feel up to take a look, I'm currently uploading the kernel source which I'll link here. I'm looking through it right now, but I'm not sure what I'm looking for. I can run insmod, and it prompts me to supply a kernel module (.ko), and when you do try one, it'll say "Function not implemented." So it appears it's there, something is just preventing it from running.

I'm setting up a build environment right now, I'm not really prepared to do anything on Windows.
[AT&T Samsung Galaxy S 4 Android Development] Walter.White:
Can't we just enable Kernel Module support using menuconfig and changing CONFIG_MODULES=n and CONFIG_MODULE_UNLOAD=n to

CONFIG_MODULES=y and CONFIG_MODULE_UNLOAD=y

Just a guess.
[AT&T Samsung Galaxy S 4 Android Development] Hashcode:
This only works if you're the one compiling the kernel. And in the case of locked devices (newer S4 builds and the N3).. we don't build the stock kernel. Samsung does.
[AT&T Samsung Galaxy S 4 Android Development] Walter.White:
Gotcha. I guess then they are just rubbing it in our face by releasing the source code for locked devices. Smh.
[AT&T Samsung Galaxy S 4 Android Development] ryanbg:
It's the law if they want to use GPL code in their devices.
[AT&T Samsung Galaxy S 4 Android Development] xxtoxicravenxx:
I really know nothing about kernel source but i had a thought. When it says "function not implemented." Could it be theres a source file the specifies which files are implemented and which are not and if we can change it to see a unsigned file as " implemented." It would let it go through?
[AT&T Samsung Galaxy S 4 Android Development] ryanbg:
With Linux, when you compile a kernel, you choose the option to compile support for it in your config file. It's strange because it has insmod, it's prompts me to supply a kernel name when I enter the command, and if I do it says function not implemented. It seems like it's definitely there, just something preventing it from working.

Also [MENTION=2471504]jeboo[/MENTION] I noticed when I tried to use the exploit and saferoot on my MI9 kernel, while it didn't work (bad address), in my tima_debug_log, I was getting kernel verification errors at the memory addresses you specified to be patched. Interesting, it might have worked, but I'm not sure. I've got a hard brick now from something else, but I'm getting my device replaced today hopefully.
[AT&T Samsung Galaxy S 4 Android Development] kevinco1:
Anymore progress on this??
[AT&T Samsung Galaxy S 4 Android Development] cyrushehe:
There are a lot of people I know who check this thread every day to see if there is any progress. I would at least like to know if there's still hope for this leading somewhere every once in a while...
[AT&T Samsung Galaxy S 4 Android Development] X_DroiD_X:
Might be an obvious question but my brain just doesnt want to function right now going on 24+hours no sleep how is this used now? Download the zip and unpack thru recovery thing? Or unpack on computer etc? Any1 gota step by step
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Hashcode is probably mostly keeping to himself on the work with it. There is definitely hope and I don't see any reason it wouldn't get implemented.

It's not ready for everyday use, and still to be implemented for everyday users. If you can't figure it out yourself how to use it or what it does, you don't need it.
[AT&T Samsung Galaxy S 4 Android Development] X_DroiD_X:
i get what it does its the whole correct way of use thats getn me
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
Again, if you can't figure it out then you don't need it. There's directions in the OP. All this does is let you load modules, it's not for loading in other kernels directly. And again, it's not in end user form.
[AT&T Samsung Galaxy S 4 Android Development] bennyboy78:
Yea definitely not user ready. Just wait it out :)
[AT&T Samsung Galaxy S 4 Android Development] tommydrum:
Reminder, no one should post on here unless it's a dev needing to talk to another dev here. I know for a fact hash is working on this, so let's keep it clean so he can use this if he needs to.
[AT&T Samsung Galaxy S 4 Android Development] Venom0642:
Nice job :good: so with you saying this you would be able to take the AT&T MK2 Kernel and do the samething for 4.3 assuming i'm correct, Also that would be awesome if you did that to the AT&T Kernel mk2 for 4.3 so many here would love that Kernel for 4.3 Big Hint lol!;)
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
Thanks. Would there really be demand for MK2 stock z-patched??
[AT&T Samsung Galaxy S 4 Android Development] Venom0642:
No was just wondering my friend i for one wouldn't mine using it, It was just a request if not i will understand all is good thought and great job on the 4.4.2 Kernel! :good:
[AT&T Samsung Galaxy S 4 Android Development] cyrushehe:
I don't mean to fragment this, but for informational purposes, what will this do for us regular users stuck on the mk2 bootloader?
[AT&T Samsung Galaxy S 4 Android Development] RK:
Nothing!
[AT&T Samsung Galaxy S 4 Android Development] timmytim:
Jeboo, you already patched the 4.4.2 zImage? Can you share that with me? I made a TW 4.4.2 ROM but if you remember (in the leak thread by DG I was getting stuck at the AT&T splash screen because the kernel does not match my MDL bootloader. I cant flash anything because my stupid f'ing USB port is melted. I'd love to test it out with my ROM and of course donate, thank and praise you
[AT&T Samsung Galaxy S 4 Android Development] CNexus:
Awesome write-ups [MENTION=2471504]jeboo[/MENTION]

Even though I have kernel source for my Sprint SGS3, I was able to apply your z-patch to my 4.3 kernel stock boot.img and force a return true every time WITHOUT needing to recompile :good:
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
Glad it was useful, good job!
[AT&T Samsung Galaxy S 4 Android Development] numbR7:
Sorry, I posted this earlier in the i9505 SHOstock-i v5.0b4 thread:

"This may be the most embarrassing question to date--but here goes. If the SHOstock-i 4.4.2 ported ROM above does not require the 4.4 bootloader and the kernal has been z-patched (fooling the MK2 bootloader) could this be a way to get a KK ROM--using SafeStrap--on the MK2 locked device?

EDIT: meant exploit BypassLKM"

I meant to post here and I meant to say your exploit BypassLKM NOT z-patched and refer over to the SHOstock ROM. I think I understand I was mixing apples and oranges. I hope it makes a tad more sense now. Anyway, I'm trying to understand the new practical options this brings to the SS locked BL user. Since you can load a different kernel in memory (the new option I can see), does that mean I could load a none TW 4.3 ROM in a slot? Are you pretty much "locked" into the 4.3 TW stuff? I believe--if this is possible--that it would be a one-off--when I changed slots--to be re-applied but would do the job? I've been cruising along flashing with a custom recovery for awhile--recently, my S4 was damaged and with the replacement I ended up in the fun new hard locked bootloader world. I will get the hang of it. I fully understand that there must be valid question in order to get and answer. I hope this is closer to the mark. Thanks...
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
This does not load a different kernel. This allows the loading of modules to the current kernel. Hashcode, the developer behind safestrap, has been working on using this on order to implement the loading of a kexec module - a module that would load a kernel over the stock kernel. If that works, then yes, non TW ROMs will be an option. For now, it's not happening though. If it were a simple process then it would have been done already.
[AT&T Samsung Galaxy S 4 Android Development] numbR7:
Thanks. Apparently I need to study this a little more. I need to understand the term "module" like the jfltatt-MK2-modules.zip that needs to be flashed on many of the SS ROMs. Are they the same type modules? Is thier mode and function the same? What is the goal--the pratical result? Any way, the question is--can you provide a link to some reading on this?

Thanks again...
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
I can't link you to any specific readings, I've just googled a few things like kexec and modules and such.

AFAIK kexec is a module just like those in the zip. They hook in to the kernel to provide some functionality (like wifi in the case of the zip). Our kernel checks the modules to make sure they're signed before using them. This exploit allows us to get around that signing however. Different modules have different functions to allow the phone different functions. It's like adding sections to a machine that let it do other different tasks along with previous ones. The goal in the case of kexec is to enable a function to boot another kernel over the current kernel. If implemented to Safestrap, it will be the next best thing to an exploit, as it will basically give us back custom kernels.

Sent from Black<3's I337 running Foxhound ROM
[AT&T Samsung Galaxy S 4 Android Development] numbR7:
Thanks a lot. You provided a ton of info. That's great start for me! Nice succinct lesson.
[AT&T Samsung Galaxy S 4 Android Development] the_mentor:
Would this exploit work on a galaxy s3?

I know this might be the wrong place to ask and I'm sorry if it is.

but do you think the exploit described above would also work with a verizon galaxy s3 on 4.3 ?

Thanks.
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
You shouldn't need it. You can flash custom kernels that don't require module signing.

Sent from Black<3's I337 running Foxhound ROM