[MOD] Add Init.d Support T230/NU - Galaxy Tab 4 Android Development

i have been messing with init.d for rooted/stock rom t230/nu and i have come up with a modified version of this >> http://forum.xda-developers.com/showthread.php?t=1912504
INSTRUCTIONS:
Flash the attacthed zip in twrp and reboot...
HOW DO I KNOW IF IT WORKED?
in root browser goto /data/local/tmp/ and if there is a file 'init.d_log_test.txt' and inside is written the date, it worked.
if the file is not present something went wrong? please let me know if it went wrong for you an i will fix it..
dont forget to hit thanks and also credit the @jamesst20 in the above link...​

Ill give it a go.
Sent from my SM-T230NU

BookCase said:
Ill give it a go.
Sent from my SM-T230NU
Click to expand...
Click to collapse
let me know how it goes as i have only tested on my device... thnx

This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.

g_ding84 said:
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
Click to expand...
Click to collapse
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..

Inside 4ndroid said:
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Click to expand...
Click to collapse
Let me if your still having trouble with root afterwards.

g_ding84 said:
Let me if your still having trouble with root afterwards.
Click to expand...
Click to collapse
oh and in your rom it seems we cant update the su binary and have to flash an updated binary seperetely from within recovery.. i found a work around and now when i flash my rom it says binary needs updating an now in my rom the normal method works and alakasm success
if you need me to explain further pm me an i will go through how i managed it..

In the rom that you're working on is based on CyanogenMod or this stock?
on the other hand just flash this file in Stock T230XXU0ANK3'll see that this is

If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english

riotaruna said:
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
Click to expand...
Click to collapse
or you could just simply flash the file file in the OP takes alot less time an is simple an staight forward lol..

File is gone

Related

Speedy Gonzales v1.0 script installation

Could someone please post a step by step on how to properly install the speedy Gonzales script for us less savvy people. Thanks in advance.
You have to be rooted with tenfars recovery and the init hack: http://forum.xda-developers.com/showthread.php?t=1223771
Download the .zip file that says flashable in the title, it located at the bottom of first post. Move it to sd card. This one: http://forum.xda-developers.com/attachment.php?attachmentid=704624&d=1314689490
Open the System Recovery app and select Recovery Mode (unsure plugged in).
Select choose zip from sd card. Navigate to the file and flash it.
What part is the issue, let me know where you have questions.
Ok I am rooted and have tenfars recovery. Do I still need the init hack installed or just go ahead and install new script through system recovery. Confused on first part.
Yes you need the init hack. Its the first link I posted. Its same thing. Download zip. Move to sd. Boot into recovery, flash. May be able to flash the speedy hack right after, but id reboot first just to make sure.
You need to go back into the /etc/init.d folder and delete the kickasskernel and S00tweaks once everything is successfully flashed.
One last question. I notice that there are 3 init.d hacks do you use all 3 or just one. That's the only think im not sure of.
Which ever one you want, but only one. Each is different and the description should describe that difference. I am on the first one. Battery saver or what ever its called.
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
dust. said:
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
Click to expand...
Click to collapse
That's what the instructions say in the original post for speedy.
You know what sucks is that the guy who made this got bashed so much he pulled the script and closed the thread...
This is supposed to be a community you ask and answer questions it gets to the point were people are afraid to ask anything without searching for 3-5 days for something i don't understand why people on these types of forums bash each others work so much its ridiculous...that sucks i feel really bad for the OP of this script he was just trying something and he got the crap kicked out of him....venting
im not gettintg the zipalign logfile he mentioned. hmmm
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
I didnt at first either, but I didnt follow directions proper and do the init.d thing first. after I did that I had the zip log thingy in /data
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
Same here.
Sandso9 said:
Same here.
Click to expand...
Click to collapse
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flash it in recovery and let me know if that works and you see the zipalign logs.
0vermind said:
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/jmvpyf
Flash it in recovery and let me know if that works and you see the zipalign logs.
Click to expand...
Click to collapse
flash it over yours then? or before ?
Sandso9 said:
flash it over yours then?
Click to expand...
Click to collapse
Yeah. Let me know if it works or if it doesn't.
0vermind said:
Yeah. Let me know if it works or if it doesn't.
Click to expand...
Click to collapse
flashed this over yours and still no zip align log file in /data
Sandso9 said:
flashed this over yours and still no zip align log file in /data
Click to expand...
Click to collapse
Sorry, wrong link.
Blah blah blah blah, edit edit edit edit
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flashed the latest file and still no zipalign log in /data.
zetsumeikuro said:
Flashed the latest file and still no zipalign log in /data.
Click to expand...
Click to collapse
Lol same here
Sent from my OG Droid

[MOD/HACK] init.d re-hack

This is something I realized when the init.d hack by naven was posted, it plain didn't work for me, and after some investigation i discovered that not all busybox versions had the run-parts applet.
It has come to my attention to that many users may not have the proper hack installed, at least the ones using my scripts, I had them check in /data for the zipaplign log and it was in fact not there.
I got it working by modding navens hack. Credit goes to him for his discovery.
Here is a link to the flashable zip. If you are using my scripts, check in /data for the zipalign log, if you don't have one, just flash this zip, reboot, and check again.
http://www.sendspace.com/file/9g6ngz
Thanks!
Edit (8/31/2011): Just so there is no confusion, this is not my new Speedy script, this is just a re-hack for init.d originally discovered by naven. This will just help those of you having problems with his hack. Obviously you need to be rooted and have recovery bootstrap.
Just flashed your zip. Log file in /data
Welcome back! Thanks for your work on the X2.
Sent from my DROID X2 using xda premium
Grapejelly!!
Sent from my DROID X2 using xda premium
Worked perfectly
Sent from my DROID X2 using XDA App
Is this a new version of your script then?
Do we have to flash this the same way with recovery (aka renaming it to update.zip) like i had to go with the manual gb update?
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
SuBDivisions said:
Nevermind, figured that out.. but why am i getting a signature verification on install? Where do i turn off sig verification?
Click to expand...
Click to collapse
There is an option under advanced I think, in recovery, to enable/disable that.....
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You need to use the modified boot -strap recovery available on this forum. D/L it & install it like any other app. When you open it, just read & follow the directions on the screen & you will get to the custom recovery where all good things flash from.
Sent from my DROID X2 using xda premium
SuBDivisions said:
I dont have that option, unless now there is some other recovery peice im missing.. my recovery whichis Android System Recovery (3e) only has reboot, apply update, wipe data, wipe cache.
Click to expand...
Click to collapse
You should be flashing this thru the Bootstrap Recovery, not the default Android Recovery.
Sent from my DROID X2 using Tapatalk
Ahh HA.. See i know i was missing something.. Thanks have been given.
Zip-align logs were not showing in /data/ for me, so I flashed this, and now they do.
I'm assuming that means the rest of the scripts weren't working either?
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
BusyBox with run-parts binary, installed in /system/xbin - If you don't have BusyBox, you can download it from the market here.
Click to expand...
Click to collapse
hapyman said:
Cool. Going to flash this but need a quick question answered.
I have Busybox 1.19.0 installed. I downloaded "Busybox" from marketplace to install 1.18.4 but which location should I chose?
Options are /system/xbin/ or /system/bin/
Thanks
Sorry found this in original init.d hack thread:
Click to expand...
Click to collapse
You should be okay on 1.19.0 now, but busybox should always always be installed in xbin.
So which init is better or the working one?
gkitab said:
So which init is better or the working one?
Click to expand...
Click to collapse
Some people find that the re-hack (this thread) works (and the original does not), others find that the original hack works just fine. A way to test is to install my Speedy Gonzales scripts, reboot the phone, and then check in /data for a zipalign log. If not, then flash this re-hack.
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing. I also noticed when I flashed speedy navens old oo got left behind. So I deleted al scripts in init folder and reflashed yours and all yours are now correct.
With his init and your script. Yours scripts are in there but no zipalign in data.
Should I start over by deleting unit folder flash your unit then speedy would that be the safe bet?
Thanks for staying.
gkitab said:
I am running speedy. So should I us you init when using yours and his when trying his? How can we tell if yours is working and when using his if his is working? This is getting a bit confusing.
Thanks for staying.
Click to expand...
Click to collapse
They are two separate things entirely. I posted the re-hack for those having troubles getting scripts to run with naven's original hack. The re-hack posted in this thread doesn't contain any init.d scripts, it's purely the hack. Like I said above, a good way to test his hack is to install my scripts (which it looks like you have), and then use a file manager like Root Explorer and navigate to /data, there should be a zipalign log, if there isn't then his hack isn't working.
Edit: Well, the biggest question is if the init hack you have installed is even working. I'm assuming you have naven's... try the above, let me know if the log is there or not.
I edited my post can you please check it and let me know what you think.
I do have his with your script.
I think I should I should delete init completely and start fresh with yours and your scripts. That sounds like safest bet. Or does naven init need to be there first then yours on top then your scripts. Thanks.

[MOD][KERNEL MODULE] wp_mod: disable system write protection

wp_mod: Module to disable system write protection
This is a kernel module that disables write protection on the system partition while running the stock kernel.
HTC changed the MMC_MUST_PREVENT_WP_VIOLATION code to make it much harder to crack. I had to redo the module completely, so this is experimental. In the past, it was a simple matter of changing a variable, now we have to replace a function in the kernel so it returns something different, causing the kernel to skip over the write protection code.
I would caution against loading the module after attempting to make changes to the system partition. It could end up corrupting the filesystem. If the module is loaded at boot, there should be no worries.
This module will probably need to be updated to load with future kernels when they are released.
Please consider a donation to support ongoing development
Many thanks to those who have donated!
Download:
wp_mod for GPE Marshmallow 6.0 can be found here:
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Sense 4.4.4 (thanks @migascalp):
http://www.mediafire.com/download/4vyqslnc4crsnto/wp_mod_3.28.401.6.zip
Sense 4.4.3 (2.22 base):
wp_mod.ko
Sense 4.4.2:
wp_mod.ko
GPE 4.4.4 (thanks to @italyforever):
wp_mod.ko
GPE 4.4.2:
wp_mod.ko
Installation:
Wait for it to be implemented in your favourite ROM
* or *
Copy the module to your device, and type
Code:
su
insmod /location-where-you-copied-it/wp_mod.ko
Changes:
April 2, 2014 - wp_mod 4.1
-only return non-existing partition number if called by generic_make_request_checks
-remove exit from module (we don't want to be able to unload it)
-clean up code
March 31, 2014 - wp_mod 4.0
-new method for HTC One m8
Source:
https://github.com/flar2/wp_mod
Module was compiled against m8 Google Play Edition source. Some symbol CRC checks had to be hexedited in the compiled module to match the stock kernel. Thanks to Michael Coppola for example of function hooking on arm: http://poppopret.org/2013/01/07/suterusu-rootkit-inline-kernel-function-hooking-on-x86-and-arm/#arm
Nice Job!!!! this is awesome
AWESOME! Thank you! Will test and see
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Confirmed working here. I was able to delete stuff with titanium backup and it stuck after reboot. Thanks so much!
Sent from my M8 via XDA Premium app
So as an end user, before it gets baked into ROMs, we need to load this after each boot?
Worked here as well on the AT&T variant. I added the line to the install recovery script that chainfire uses for SuperSU and it loads it on boot now
what i did was run the insmod command in terminal emulator, made the system rw/ edited /system/etc/install-recovery.sh and added the insmod line in there Sure it would be easier if I had init.d support but I'm on stock and am too lazy to change to a custom rom
You guys are awesome.
Awesome work....Can now scratch my theming itch
Sent from my unknown using Tapatalk
gjlowe said:
So as an end user, before it gets baked into ROMs, we need to load this after each boot?
Click to expand...
Click to collapse
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
mattman83 said:
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
Click to expand...
Click to collapse
Hmmm..I ran the command in the OP and rebooted and when I try to create a directory in / it says that it is a read only file system.
graffixnyc said:
Worked here as well on the AT&T variant. I added the line to the install recovery script that chainfire uses for SuperSU and it loads it on boot now
what i did was run the insmod command in terminal emulator, made the system rw/ edited /system/etc/install-recovery.sh and added the insmod line in there Sure it would be easier if I had init.d support but I'm on stock and am too lazy to change to a custom rom
Click to expand...
Click to collapse
Can you share your zip please
Sent from my HTC One_M8 using Tapatalk
gjlowe said:
Hmmm..I ran the command in the OP and rebooted and when I try to create a directory in / it says that it is a read only file system.
Click to expand...
Click to collapse
You need to run it each time you boot, until it is correctly working as init.
mattman83 said:
Nope. It'll get rolled into the kernel/scripts that are loaded at boot automagically.
M.
Click to expand...
Click to collapse
Electronic Punk said:
You need to run it each time you boot, until it is correctly working as init.
Click to expand...
Click to collapse
Ok then, I guess @mattman83 was referring to when we have this in custom ROMs?
gjlowe said:
Ok then, I guess @mattman83 was referring to when we have this in custom ROMs?
Click to expand...
Click to collapse
Yup, I have already added it to my copy of ARHD 3.x and it is working great, so look for a release as soon as Mikes connection allows!
im on the vzw m8. we have temp 'root access' to /system/xbin. is it ok to do this as well? which will make /system writable?
-4ndr01d- said:
im on the vzw m8. we have temp 'root access' to /system/xbin. is it ok to do this as well? which will make /system writable?
Click to expand...
Click to collapse
I don't know what method they use to get root access to /system/xbin. This is probably compatible, if it loads with the Verizon kernel. Backup all your data and try it.
flar2 said:
I don't know what method they use to get root access to /system/xbin. This is probably compatible, if it loads with the Verizon kernel. Backup all your data and try it.
Click to expand...
Click to collapse
jcase has got us root access ...its only writable to /system/xbin and has to run on every boot. the app used is called WeakSauce
but i was thinking. once my phone boots up, i wait til i have root access, then download the file, place it in the correct directory, download terminal emulator and run the commands. then /system becomes writable until next reboot?
@flar2 nice job as always man!! :good:
awesome awesome awesome
looking forward to elementalx on the m8!
For users who have init.d support in their ROM. Flash this and your good to go
https://mega.co.nz/#!XINyDIrB!QcdP3sZJjgKAivkEa7iN8Jusx0e78T1rpA5PT7VGAxQ
Sent from my Note 3

(L5 II) CWM for Locked Bootloader(Beta 2)

Hey guys
I finished building CWM Recovery for locked bootloaders.
its still in the beta phases.... actually there was no alpha tests because no one on my team has a l5 II.
Due to forum rules I cannot choose who I want to give this recovery or exclude anyone from using it. so if you are a noob I cannot stop you from using it but please dont blame me if you brick your device!!!!!
The recovery as far as I know has no errors.
I have tested flashing Mother of all ad blocking and it worked perfectly.
How Does It Work?
the recovery uses 2nd int.
when your phone boots It is hacked to load scripts from init.d folder.
inside the init.d folder there is a script called 1.unsecure
this stops the system an kills process and launches the recovery.
How Do I Install?
Busybox must be installed
Extract the zip(attached)
Run the init.bat
Enjoy
How Do I Enter Recovery?
Reboot
after the lg logo before your boot animation starts repetitively hit the Vol + key
or run the reboot recovery app
Who do I thank?
ME for all the hard work testing and retesting
@IGGYVIP for giving me hope that its possible and all the support he has given me so far.
Optima Team for being such a great team
Can I port this to my device?
Yes!!
Port this to as many devices as possible. If you need advice or need to know how to port feel free to PM me.
It doesnt work for me?
some user experience problems when the script applies permissions
to fix this
Change permissions to all files in /system/bootstrap/* to 775
Download
DOWNLOAD
Great work man! Optima Team is proud of you!!!
Sent from my GT-I9300 using Tapatalk
slipsystem said:
Hey guys
I finished building CWM Recovery for locked bootloaders.
its still in the beta phases.... actually there was no alpha tests because no one on my team has a l5 II.
Due to forum rules I cannot choose who I want to give this recovery or exclude anyone from using it. so if you are a noob I cannot stop you from using it but please dont blame me if you brick your device!!!!!
The recovery as far as I know has no errors.
I have tested flashing Mother of all ad blocking and it worked perfectly.
How Does It Work?
the recovery uses 2nd int.
when your phone boots It is hacked to load scripts from init.d folder.
inside the init.d folder there is a script called 1.unsecure
this stops the system an kills process and launches the recovery.
How Do I Install?
Busybox must be installed
Extract the zip(attached)
Run the init.bat
Enjoy
How Do I Enter Recovery?
Reboot
after the lg logo before your boot animation starts repetitively hit the Vol + key
Who do I thank?
ME for all the hard work testing and retesting
@IGGYVIP for giving me hope that its possible and all the support he has given me so far.
Optima Team for being such a great team
Can I port this to my device?
Yes!!
Port this to as many devices as possible. If you need advice or need to know how to port feel free to PM me.
Download
https://dl.dropboxusercontent.com/u/51036208/Android/Stock/cwm.zip
Click to expand...
Click to collapse
why not mod one of the 2nd-init recovery apks with this?? Make much simpler for n00bs as well as give the reboot to recovery option.
Modding the apk I have exp with, I just never had any success building a working 2nd-init binary.
PlayfulGod said:
why not mod one of the 2nd-init recovery apks with this?? Make much simpler for n00bs as well as give the reboot to recovery option.
Modding the apk I have exp with, I just never had any success building a working 2nd-init binary.
Click to expand...
Click to collapse
The apk pushes the script to a different location and only executes on the l3 ii. So the app doesn't work on the l5 ii. I would have to do allot of editting. Enable init.d and change where the files get pushed to.
But it's pretty simple for noobs.
And this is not ment for noobs as I said on my thread its still on beta testing.
slipsystem said:
The apk pushes the script to a different location and only executes on the l3 ii. So the app doesn't work on the l5 ii. I would have to do allot of editting. Enable init.d and change where the files get pushed to.
But it's pretty simple for noobs.
And this is not ment for noobs as I said on my thread its still on beta testing.
Click to expand...
Click to collapse
ahh, I've just messed with 2nd-init on the LG Motion & Spirit and the same apk works on the F3, F6, & F7 (I think). The Spirit no longer needs 2nd-init tho.
PlayfulGod said:
ahh, I've just messed with 2nd-init on the LG Motion & Spirit and the same apk works on the F3, F6, & F7 (I think). The Spirit no longer needs 2nd-init tho.
Click to expand...
Click to collapse
Ya I think the apology works on most devices. If not then mine should work pr you will just have to change the key. It's pretty simple to port. I will try make. A guide tommorow
Awesome Work Mate !!!
@slipsystem
Great Job
You have made so much more out of that apk then i ever would
I can see Newsworthy thread when porting to other devices works
I can't reboon in recovery mode
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!
jamonazo3000 said:
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!
Click to expand...
Click to collapse
Check
/data/local/tmp
There is a file called init.d_log_test
Check if you have that file
Open it check if the date and time matches your last reboot.
Great! Now we only need custom roms and android updates.
jamonazo3000 said:
Hello, I can not reboot in recovery mode, I was run the init.bat, then, reboot my L5 II (e450f) and pressed repetitively the Vol + key. But I never reboot in recovery
Could you help me?
PS. Your team is awesome!!
Click to expand...
Click to collapse
Sorry its dues to permissions
Change permissions to all files in /system/bootstrap/* to 775
slipsystem said:
Sorry its dues to permissions
Change permissions to all files in /system/bootstrap/* to 775
Click to expand...
Click to collapse
the init.sh has chmod rules to 755
the attached one has 775
Updated Version in first post!
Now Includes Reboot Recovery app
and hopefully fixed permission problem.
slipsystem said:
Check
/data/local/tmp
There is a file called init.d_log_test
Check if you have that file
Open it check if the date and time matches your last reboot.
Click to expand...
Click to collapse
Hello, I was open /data/local/temp/ and only can see a file recoverylog.txt
I will check your new update.
Thanks for all
IGGYVIP said:
the init.sh has chmod rules to 755
the attached one has 775
Click to expand...
Click to collapse
sorry my math is bad. the permission are meant to be 755. for some reason when shell is changing permissions it gets permission denied.
I think that the script 001unsecureboot doesn't kill the bootanimation, in fact when I reboot to recovery there is the bootanimation (deformed and with strange colors) on the screen, and only when I press a key the recovery appears for one second.
After adding the line "$BB killall bootanimation" after "$BB mount -o remount,rw /system /system", the issue is solved.
ownership ?
slipsystem said:
sorry my math is bad. the permission are meant to be 755. for some reason when shell is changing permissions it gets permission denied.
Click to expand...
Click to collapse
May be try changing owner to root before changing permissions ?
in the .sh add this code before chmod but after the remount,rw
Code:
chown -R root /system/bootstrap
in theory as its owner it must allow change of permission
Let me know
IGGYVIP said:
May be try changing owner to root before changing permissions ?
in the .sh add this code before chmod but after the remount,rw
Code:
chown -R root /system/bootstrap
in theory as its owner it must allow change of permission
Let me know
Click to expand...
Click to collapse
I actually had the script setting permission for
/System/etc/bootstrap
And not
/System/bootstrap
@HandyMenny
Thanks For that. I added that in a update.
slipsystem said:
I actually had the script setting permission for
/System/etc/bootstrap
And not
/System/bootstrap
Click to expand...
Click to collapse
with system as System? never had em capped b4.

GT-P5210 kitkat

From Sammobile new 4.4.2 P5210XXUBNH1
Luxor said:
From Sammobile new 4.4.2 P5210XXUBNH1
Click to expand...
Click to collapse
http://samsung-updates.com/device/
there is the download link i am downloading it right now.
will it work on my dutch tab 3 10.1?
damian312 said:
http://samsung-updates.com/device
there is the download link i am downloading it right now.
will it work on my dutch tab 3 10.1?
Click to expand...
Click to collapse
downloading now too, please report!
Downloading.
nowo said:
downloading now too, please report!
Click to expand...
Click to collapse
I am a little afraid to test it.
Do i have to flash through odin?
hey,
if you guys are hesitant, i'll test it. give me a couple of hours to get it and do the usual
@Restl3ss - dude OP look !
m
moonbutt74 said:
hey,
if you guys are hesitant, i'll test it. give me a couple of hours to get it and do the usual
@Restl3ss - dude OP look !
m
Click to expand...
Click to collapse
You are the man.
i wait for it
dead link bud!
RoninTPD said:
dead link bud!
Click to expand...
Click to collapse
http://samsung-updates.com/device/
not that hard to fix it:good:
Installing. can't wait to pull it apart.
CAG-man said:
Installing. can't wait to pull it apart.
Click to expand...
Click to collapse
cag,
when you are go can you pull the /system/vendor directory and post it?
also /system/bin/toolbox ?
my download just started , i can't wait !!
m
M,
I will do so.
Holy crap, finally!
damian312 said:
http://samsung-updates.com/device/
not that hard to fix it:good:
Click to expand...
Click to collapse
thanks!!:good:
CAG-man said:
Installing. can't wait to pull it apart.
Click to expand...
Click to collapse
Does it work?
The firmware works, but two things are proving to be very difficult.
one is extracting system.img, i dont know what's different, but the method i used for the 4.2 firmwares just crashes now.
two, and this is a big one
rooting it..
working on it
edit: super SU 1.9.4 zip from chainfire worked. No other method works though, the superuser apk will install but the binary doesn't stick
edit 2: successfully extracted the system image
notes
hey,
if the update with the t211 was any indication, be sure to only write boot.img and system.img
i am making a flashable zip and will post after i get it right and debloated and get the script correct.
realistically, sometime tomorrow, will update.
@Restl3ss okay so iam laughing at myself right now becuase i can not get the damned thing to write. i don't use windows
so no odin. i have tried dd writing the images but on boot i hang at logo and with no adb i can't get a visual on the problem.
i have a .zip put together to do the same and get the same. i have another zip set up ota style but can't script worth a damn.
can you whip up a script and post it?
an interesting note- in /sbin is a binary file named partlink. thoughts?
Restl3ss
@Restl3ss
okay so this is the joke
i am too poor to upload a large file to devhost. :laugh:
solution - i going to upload the otapackge for the firmware WITHOUT the system folder.
the package has the modified to unsecure boot.img and the updater script which just happens to be the
same one i am using for cm11 :laugh: :victory:
these are the instructions for converting, mounting and pulling the system image into an cwm flashable zip
to convert and mount sparse .img in terminal
simg2img system.img system.img.ext4
mount -o loop system.img.ext4 /a/directory
then nav to that directory in file browser, copy the contents of /system and insert in to package.
there is also a second step to correct issues with symlinks in vendor. drop that package into ota second
sorry for the inconvenience. it's in your folder with the patches.
but hey, i'm poor.
m
i'm running it right now and it seems very kitkatty
If i flash 4.4 can i still flash back to 4.2.2?
moonbutt74 said:
@Restl3ss
okay so this is the joke
i am too poor to upload a large file to devhost. :laugh:
solution - i going to upload the otapackge for the firmware WITHOUT the system folder.
the package has the modified to unsecure boot.img and the updater script which just happens to be the
same one i am using for cm11 :laugh: :victory:
these are the instructions for converting, mounting and pulling the system image into an cwm flashable zip
to convert and mount sparse .img in terminal
simg2img system.img system.img.ext4
mount -o loop system.img.ext4 /a/directory
then nav to that directory in file browser, copy the contents of /system and insert in to package.
there is also a second step to correct issues with symlinks in vendor. drop that package into ota second
sorry for the inconvenience. it's in your folder with the patches.
but hey, i'm poor.
m
i'm running it right now and it seems very kitkatty
Click to expand...
Click to collapse
got it system folder is properly extracted and what not, trying to deodex. About 10 apks are failing on every deodex attempt, can't figure out why. Gonna upload a 100% stock to xda anyway, deodexed + rooted will just have to come a bit later.

Categories

Resources