Place GApps, ROMs, Kernels, etc. in this thread.
I have the ROM ported, just need to get the bugs out.
The bugs being that the rom will not install due to a
set_perm: some changes have failed (status 7).
If there is a known fix for this please post it!
Sent from my GT-P5110 using xda app-developers app
Which recovery are you using, and which version?
TitanTaber said:
I have the ROM ported, just need to get the bugs out.
The bugs being that the rom will not install due to a
set_perm: some changes have failed (status 7).
If there is a known fix for this please post it!
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
status 7 error is because of you using SELinux disabled ROM/kernel in previous ROM that you used.
Sent from my XT907 using Tapatalk
I remember reading in @CodyF86 's thread that you need CWM 6.0.4.4 or newer for KitKat, which is why I mentioned the recovery, could be something to look at if you're using a different recovery / version.
Related
hello guys. I have a galaxy tab 10.1 WIFI 16GB. Currently im using milestone 4.
My problems started I think when I went to AOKP build 26. Many crashes (reboots)
WIFI doesnt work sometimes. sometimes when i didnt use the tab for a while and then i click the power button, I see the unlock screen but my touches do nothing.
This is realy frustrating cuz I cant use my tablet, Im having troubles ALL THE TIME.
I have CWM 4.0.0.4, yesterday when i tried to move to milestone 4 I also tried some other roms (not AOKP) and they all showed the same bug when i tried to install them: assert failed: getprop("ro.product.device")=="p4wifi" || getprop("ro.build.product")=="p4wifi"
WTF? i cant install roms that arent AOKP's. so guys, what can I do to save my dying tablet? please help
thanks, Amit.
up
You on old build, update to newer version of either aokp or cm9 and see if it changes.
Sent from my SGH-I777 using xda premium
nakedninja42 said:
You on old build, update to newer version of either aokp or cm9 and see if it changes.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Also flash 5.5.0.4 recovery before updating your OS.
Sent from my SGH-I777 using xda premium
nakedninja42 said:
You on old build, update to newer version of either aokp or cm9 and see if it changes.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I was also on build 31 just a few days ago, I updated every build, now Im on milestone 4.
nakedninja42 said:
Also flash 5.5.0.4 recovery before updating your OS.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
alright, just flashed it
will try to install cm9 rom nightly now..
update 1: great! I managed to install cm9 nightly, nice boot btw... now ill just wait and see if i still run into this bugs... thanks man!
Phill known developer of safe kernel for i9100 is now on N7000 too and with bless of him we have now safe stock kernel for ICS ROM for N700
Here brief note about PhilZ-cwm6 Kernel
-mmc erase cap command is disable from both recovery as well kernel
-You can safely wipe with this kernel, as well flash zip file too.
-This also available in flashable zip format and you can flash from stock recovery too.
-You will get root added with flashing this kernel
-Clockworkmod 6 for added features (incremental backups...) and smoother GUI
-PhilZ-cwm6 comes naively with the last busybox 1.20.2, that is entirely part of the cwm recovery (/sbin/busybox)
Here is original thread for kernel
http://forum.xda-developers.com/showthread.php?t=1901191
dr.ketan said:
New safe kernel on the way
I have tested kernel. This kernel won't universal for all but just like Cf kernel. It will be according ROM. B'coz here there is no other modification from stock kernel but just made it safe by removing mmc_erase_cap command.
This is stock kernel but binary patched with MMC_CAP_ERASE removed from both recovery as well kernel
Best thing is you can flash with stock recovery and also gives root.
So anyone want to test let me know.
Click to expand...
Click to collapse
I would love to Ketan! I can PM u my mail id if you want!
Developer is monitoring this thread and you will get PM from him just mention your ROM to get kernel accordingly
I am on ddlr9
Sent from my GT-N7000 using xda app-developers app
Where to get
Sent from my GT-N7000 using xda app-developers app
jaskiratsingh said:
I am on ddlr9
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
You will get PM soon.
puduraja said:
Where to get
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Just mention your ROM here, developer will send you link
Rom Stock XXLRT
N7000XXLRT
Thanks,
djoni_gitara said:
N7000XXLRT
Thanks,
Click to expand...
Click to collapse
Same here!
Sent from my GT-N7000 using xda premium
tell me more , tell me more
i wan it...!!!!
Sorry,
Did not want all this buzz
It is the same PhilZ-cwm6 released for the i9100. See my signature for what it is about
Actually, I was about to release for the Note, but there are small issues I need to fix before even release further beta
There are 2 options:
- stock with cwm6 + patched MMC_CAP
- same as above + some features like customboot.ss, init.d and custom boot animation (you can still keep the samsung anim of course), something like CF-Root from which this kernel is inspired
I prefer 2nd option even if it seems to be more work at first sight. The reason is the i9100 kernel is already based on theses features. I can automate all the process for future kernels and it would be easier to maintain one version of script for both phones
For now, I have to rebuild my dev environment include OS reinstall and maybe increase RAM
Give me 2-3 days to sort this and maybe release first kernels
Meantime, you can still tell if you prefer option 1 or 2, porting builder scripts shouldn't be difficult after all
2nd option with custom bootanims
LR9
Sent from my GT-N7000
LRI option 1
Enviado desde mi GT-N7000 usando Tapatalk 2
LRT Option 1:angel:
Phil3759 said:
- stock with cwm6 + patched MMC_CAP
Click to expand...
Click to collapse
+1
I can't test things on my main phone however my "vote" for which version of the kernel I would prefer to see released is option 1.
Thanks to both of you!
N7000XXLRQ
Option 1
Sent from my GT-N7000 using xda app-developers app
LRT option 2
Cant wait!
one ov eeech please
hoping to be on LR9 sooon
PROBLUMS HAVE BEEN SOLVED BY KAYANT. THX FOR HIM
Problem comes here.
Some of my friends from our association including me want to develop roms based on AOKP or cm, and those development projects are based on STOCK kernel for it is less likely to crack and are much easier to test.
WHEN I dealt with 4.1.2, I made a mixture of it (mostly framework) with the older 4.1.1-stock kernel rom, and was finally able to boot on stock 2.3 kernel. (see my post on Defy General)
BUT HOW can I transplant/fix those 2NDBOOT ROMS to STOCK KERNEL without MAKING a 'mixture'? The method mentioned above is NOT able to make the latest 4.2 rom to boot.
ps. removing the custom kernel and change default bootmode into 2ndinit IS USELESS.
Sent from my DEFY using xda app-developers app
NO ONE KNOWS HOW?
Sent from my IdeaTab A1107 using xda app-developers app
TerenceWSK said:
NO ONE KNOWS HOW?
Click to expand...
Click to collapse
1. Don't yell
2. Forum rules require waiting more than 24 hours between bumps, so please follow that rule.
I'm sorry, I'm new here. Thank you.
Sent from my IdeaTab A1107 using xda app-developers app
Anyone know how to find which process is giving me this error or any suggestions on how to fix it
Sent from my GT-N7100 using xda app-developers app
nore info please what ROM Kernel MODS... what have you done to your phone...when did it start....need moer info... Did you flash gapps for a 4.2.1 rom?
I am using Defy+ MB526 And have installed paranoid androind CM10 Rom of Jelly Bean!
it gives me 3 recoveries :
1. Stock recovery
2. Stable recovery(ICS recovery)
3. Custom recovery(JellyBean recovery)
But none of these recoveries allow me to make a complete nandroid backup! sometime it shows error while copying android data sometimes android_secure or whatever! Or sometimes Stucks UP!
The fact is recovery is a fail! So any suggestions??
wow no reply after 127 views!
Guess d defy developers have no answer!
I get that error sometimes. It's never caused me any trouble.
Sent from my MB526 using xda premium
koolboy420 said:
wow no reply after 127 views!
Guess d defy developers have no answer!
Click to expand...
Click to collapse
Developers don't visit this part of the forum
Sent from my MB526 using xda premium