Related
CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded
I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.
Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Any comments from people that have this applied (and working with full root)?
Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
That worked Thanx
Kernel's working just fine with Avalaunch's Froyo ROM.
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.
lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!
Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.
Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk
Hi guys!
As some of you must have noticed, latest Samsung GT-I9500 firmwares carry a kernel configuration supposed to prevent SETUID privilege elevation.
Stock unmodified firmware with root is my preferred setup but also a strong dependency for all my development, for me this change is a massive setback if not a dealbreaker.
While poking around I found in about an hour something weird that reveled being a vulnerability, so I created a little thing to make it useful for now.
README:
Stupid SU: Galaxy S4 root helper by François SIMOND aka @supercurio
Circumvent an extremely weak false-security "Anti Root" mechanism implemented
on latest Samsung Galaxy S4 devices (on both Exynos and Qualcomm versions)
Preventing proper root function on official firmware breaks all my Voodoo apps
requiring stock+root and is a move that's hostile to both users and developers.
Samsung security might be embarassed by this proof of concept, as it defeats
their mechanism in a single line... not even with complex ARM assembler
but *one* line of shell script.
However, the goal here is to show Superuser solutions developers how to
deal with those devices for now, and provide a working solution to people who
bought a Galaxy S4 expecting to root it cleanly and easily but cannot.
This proof of concept is slightly slowing down Superuser calls, but its
"plain text" implementation has the merit of showing how stupid this exploit is.
SELinux configuration stays unmodified and active.
Features:
- Detect and supports both SuperSU and Koush's Superuser
- Installs Super SU binary by default
Make sure you have one of those Superuser apps installed:
- https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
- https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Root feature doesn't rely on a "StupidSU kernel" which is only an installer.
Feel free to flash back Samsung's original boot.img from their official firmware
after booting at least once.
Important Note:
This "exploit" is so lame that it will be fixed in no time, making updated S4
a pain to root again.
I wish Samsung will reconsider their "Anti Root" approach, which is damageable
in every regard and defective by design as demonstrated here.
Also, I'm simply not interested developing for and promoting devices from
manufacturers hostile to developers: It's just a waste of valuable time.
Click to expand...
Click to collapse
INSTALL
1/ copy rooting/ directory in your initramfs
Make sure "root.sh" file is has an executable permission (chmod 744 recommended)
2/ Add those lines at init.universal5410.rc end:
# Stupid SU
service rooting /stupidsu/root.sh
class main
user root
group root
oneshot
3/ Assemble your initramfs with the associated Samsung official kernel binary
of choice in a regular boot image
4/ flash as boot.img
5/ At each boot, Superuser app are detected automatically and su binary adjusted
accordingly.
Click to expand...
Click to collapse
Source code
On GitHub
License
Kernels downloads, only for demo purposes of the concept, you can flash back original Samsung boot.img once rooted
GT-I9500 Stock + root StupidSU v4 UBUAMDE
GT-I9500 Stock + root StupidSU v4 XXUAMDK
GT-I9500 Stock + root StupidSU v4 XXUAME1
What's next
Owners of Qualcomm Galaxy S 4 devices experiencing the same dificulties with Samsung the anti root strategy might want to try this method, please let me know if you're ready for some experimentations.
Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
Sent from my LG-P500 using xda app-developers app
Going to try this on latest LE1 stock kernel now .....thread is in correct section
edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..
Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.
Here comes the master welcome to SGS4 development forum mate.. (rahulzeven from twitter here )
So the BEST thing's just happened?!:laugh::good:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Edit: New file uploaded
grgsiocl said:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Click to expand...
Click to collapse
Thanks fo much! Will Titanium Backup work on this kernel?
Hope chainfire will start working on mobileOdin soon. So much easier to flash than.
... tapat*lked
GSeeker said:
Thanks fo much! Will Titanium Backup work on this kernel?
Click to expand...
Click to collapse
wrong file uploaded. Please download the same in 5 minutes. Uploading is on and the kernel date should be MAY 04
---------- Post added at 12:33 PM ---------- Previous post was at 12:28 PM ----------
GSeeker said:
Thanks fo much! Will Titanium Backup work on this kernel?
Click to expand...
Click to collapse
it should work as i dont use titanium backup and instead i use gobackup pro and it works fine anyway
MDK from OP working good, thanks
grgsiocl said:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Edit: New file uploaded
Click to expand...
Click to collapse
I'm trying to repack the kernel of korean gs4,
but I am a noob in kernel devs.
I can edit ramdisc, but fist trying in initramfs, zImage.
Is rooting directory means both root.sh and files(folder)?
and paste them on first class route?
hope you give some advices.. thanks
aslak89 said:
I'm trying to repack the kernel of korean gs4,
but I am a noob in kernel devs.
I can edit ramdisc, but fist trying in initramfs, zImage.
Is rooting directory means both root.sh and files(folder)?
and paste them on first class route?
hope you give some advices.. thanks
Click to expand...
Click to collapse
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image
grgsiocl said:
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image
Click to expand...
Click to collapse
then, is not necessary to recompile zImage?
ok I m going to try it right now, thank you grgsiocl
muhamet said:
Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
Click to expand...
Click to collapse
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.
grgsiocl said:
Going to try this on latest LE1 stock kernel now .....thread is in correct section
edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..
Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.
Click to expand...
Click to collapse
Great then
aslak89 said:
then, is not necessary to recompile zImage?
ok I m going to try it right now, thank you grgsiocl
Click to expand...
Click to collapse
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.
Which gives you several usage options:
keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed
you can flash back the official kernel and still enjoy root the same.
supercurio said:
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.
Which gives you several usage options:
keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed
you can flash back the official kernel and still enjoy root the same.
Click to expand...
Click to collapse
Thank you for awsering
then I repacked my kernel but still not work.
copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.
I guess permission is the thing,
attach my shots
hope you loot at once.
Sent from my SHV-E300S using XDA Premium HD app
walda said:
Hope chainfire will start working on mobileOdin soon. So much easier to flash than.
... tapat*lked
Click to expand...
Click to collapse
He will after he will come back from his vacation.
I'll look into a fixed CF-Auto-Root for the I9505 as soon as I'm back on Sunday. I imagine that will be tested by Sunday evening, with a I9500 test version available sometime Monday. If all is well
In StupidSU environment and for this initial release Koush's Superuser app would
be preffered as SuperSU main UI refuses to launch because it cannot detect its
original su binary. Aside from that both work as expected.
Click to expand...
Click to collapse
This is because you're not installing the backup su binary. The UI app detects this is missing and triggers an update. Bug in StupidSU
aslak89 said:
Thank you for awsering
then I repacked my kernel but still not work.
copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.
I guess permission is the thing,
attach my shots
hope you loot at once.p
Click to expand...
Click to collapse
Alright I'm adding some logging in my scripts so you'll be able to see what's happening − or not
supercurio said:
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.
Click to expand...
Click to collapse
Brilliant news!!!! Thanks a LOT!!
Let's make it work!! It will be AWESOME if I could use latest STOCK Kernel in my ROM's......
I'll give you a hand
Multiboot for Sony Xperia Z1 Compact
How its look -> http://i58.tinypic.com/35346bt.png
How to install boot menu
download bootmenu_amami.rar, extract folder "bootmenu" to the your internal storage
put boot.img or kernel.elf to the mainrom folder, make sure thats the same kernel like your primary rom (aka main rom)
download bootmenu.img from attachment, flash bootmenu.img using fastboot commnd: fastboot flash boot bootmenu.img
Click to expand...
Click to collapse
Since your bootmenu folder no contain settings.ini (you runing bootmenu at a first time), settings.ini will be created easily. You need to complete main step aka main rom creation:
(mainrom creation)
reboot into bootmenu, chose "patch rom package", navigate to the bootmenu folder on your internal storage, navigate to the mainrom folder, select mainrom.zip package (make sure boot.img or kernel.elf is the same like your current main rom kernel, and make sure boot.img is in folder mainrom), select mainrom.zip and click "yes". Main rom will be added into boot menu entry. Now reboot again into boot menu and you will see new menuentry, chose these menu to boot into your primary rom!
(other roms creation - you can do only if you completed main rom step)
reboot into bootmenu, chose "patch rom package", principe is a bit diferent than main rom step (we have 3 steps):
(step 1): make sure seccond rom package is on your external storage ...see this post -> http://forum.xda-developers.com/showpost.php?p=52830021&postcount=45
(step 2): chose rom zip you want to patch, patch them
(step 3): reboot again into boot menu (new rom entry will be displayed), select these rom to boot, on led blinking press to boot into cwm, now you are in cwm of these rom, now navigate to the same folder where is your package, you will find zip with appended name "patched.zip", chose these patched zip to install trought these recovery, you are done!
Click to expand...
Click to collapse
WARNING:
there is possibility for your partitions of the main rom to get overwriten if multiboot.sh fail to patch these rom you going to patch, just to let you know! Two click solution is in testing stage so there is probably a lot of bugs! I am not responsible if you lost your private data! So guys if you willing to help, I am waiting. Things need to be improved in multiboot.sh !
Click to expand...
Click to collapse
Source code of the my bootmenu project
https://github.com/munjeni/bootmenu_z1_and_z1c
Public License for BOOTMENU and for my Auxiliary Work
You can Distribute my source without my Permissions. Distribution should include my XDA name 'munjeni' and Link to this 'BOOTMENU' thread in your Credits sections/About sections and Properly Visible to Human Eyes. If you use our source and have them modified, you need to make them public to everyone!!! If you not propertly use my source and you not give proper credit, and you not share your modified source code which is based on my source code, I will find you and I will report your post!
Click to expand...
Click to collapse
No doubt, I'm really interested in multi boot,
I have tried it on my XU and it was awesome:laugh:
munjeni said:
Hallo, just to reserve our thread for something that you will like for sure! I have plan to port my old project to our device, more info you can see here -> http://www.xda-developers.com/android/xperia-boot-menu-ported-to-the-xperia-p-in-preview-form/
First thing - I will port them, thats for sure! Next thing - will try to integrate all things into boot menu (look into tutorial thread to see how it working) to make all things easy to all as possible, first of all I need to get more free time! Soon when I get one free day I will give you beta version! By now whant to see your opinions! Do you have interest in multiboot??? Let me know first!
Click to expand...
Click to collapse
I'm flashoholic,like to test everything, multiboot sounds nice
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Would this for example allow to have stock and cm11 both installed and easily switch between those 2? If yes then im totally up for it
Sounds definitely awesome!
Progress... Boot menu beta done, having problem with kexec, seems kexec not working. Will try with stock kernel since cm kernel probably have no working kexec.
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
munjeni said:
Beta 1 is out! By now I have included 2 multiboot things, cwm and stock kitkat, will give you more (cm11...etc) when I get more free time! Enjoy!
Click to expand...
Click to collapse
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
XperienceD said:
Can you not disable CABL and enable taptowake as any and all searching shows them to be kernel related?
Click to expand...
Click to collapse
I'm sorry but I do not know what you're talking about! Plese be more clear!
munjeni said:
What? Plese be more clear
Click to expand...
Click to collapse
tap2wake
CABL
XperienceD said:
tap2wake
CABL
Click to expand...
Click to collapse
Sorry mate but our thread is related to the multiboot and not to the kernel things, you can open a new thread for your problem, sorry!
munjeni said:
Sorry mate but our thread is related to the multiboot and not to the kernel things
Click to expand...
Click to collapse
Oh, given that a boot.img is actually a kernel I thought it might be something you could implement whilst working on it.
munjeni said:
you can open a new thread for your problem, sorry!
Click to expand...
Click to collapse
They're not problems they are suggestions.
New version is out!
Changelog:
- all isues with kexeced kernel solved (missed modile data, wifi, bluetooth...etc)
- black theme
Enjoy!
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
munjeni said:
I have trying to boot cm11 from sdcard whole day and have no idea why fail to boot! Anyone tried to boot cm11 from sdcard? What might be a problem?
Click to expand...
Click to collapse
I'm planing on trying tomorrow, I'll try and give some feedback
Solved! Will give you soon cm11 in multiboot!
munjeni said:
Solved! Will give you soon cm11 in multiboot!
Click to expand...
Click to collapse
Well then I shall wait until you do so Thank you for your effort:fingers-crossed:
Done and CM11 is booted sucesfully from sdcard By now have only one problem which I have experienced last year on my multiboot for Xperia Go, I have solved them on Xperia Go but unable to find a thread how I got fixed them solved, problem now on Z1C is these seccondary rom runing from sdcard is very slow like was a year ago on Xperia Go, if some one found my post where I have fixed that please give me a link. I don't know if there is something related to the tune2fs parameters since I forgot how I got them fixed. Every idea is welcome!
Maybe this
http://forum.xda-developers.com/showpost.php?p=44945343&postcount=24
http://forum.xda-developers.com/showpost.php?p=44969886&postcount=36
http://forum.xda-developers.com/showpost.php?p=44979190&postcount=47
Yes seems 3.th post related to tune2fs and journal_data_writeback to cache and data giving better performance. Stil noticed some lags, probably because my 8gb old sdcard is so slow Will try to boot from internal storage, maybe it will give better performance or at least maybe an 64gb class 10 sdcard can solve lag problems? What you think guys?
I have tried to compile TWRP 2.3.
It compiled with errors, but after solving a few errors, it was built successfully.
However, on flashing the zip via CWM, no effect took place, I am attaching my TWRP.
Anybody with knowledge and experience can help me compiling a successful build.
XDA:DevDB Information
TWRP 2.3, Tool/Utility for the Samsung Galaxy Y GT-S5360
Contributors
Nachiket.Namjoshi, DC07
Version Information
Status: Testing
Created 2014-06-08
Last Updated 2014-06-08
Downloads
DOWNLOADS
Removed
Go Here for working Builds: https://forum.xda-developers.com/galaxy-y/development/recovery-twrp-3-0-3-0-touch-recovery-t3550609
Reserved
Problems and Changelogs
Changelogs
latest update: Sun, Jun 8 ,2014.
v1.0a(alpha)
-Initial build (doesnt boot into twrp)
Problems and Errors(Intended for the ones who are willing and are able to help)
P.S you can read it but in case you dont understand what you are reading please refrain from posting questions about them in this thread.
If you are really curios, shoot me a PM or USE_THIS_LINK
Several errors (so cant paste) while compiling a otapackage (make -j4 recoveryzip)
Code:
Several mistakes in [B]bootable/recovery/updater/install.c[/B]
some [B]int[/B] not already declared,
some [B]arguments[/B] not appropriately passed in some [B]functions[/B] namely
[B]make_ext4fs(const char *filename, const char *directory,
char *mountpoint, int android, int gzip, int sparse);[/B]
and applypatch funtion...
all this is found on install.c
probably the reason why things arent built properly while [B]make recoveryzip[/B]
hence the size... 1mb
A few errors about the libs which are never compiled !
Code:
collective errors:
libopenaes.so, libblkid.so not a prelink map
These libs are never ever built !
Hence the errors.
Update01
After Solving and re-writing almost all of install.c and the update folder
got this stop
Code:
make: *** No rule to make target `out/target/product/totoro/obj/STATIC_LIBRARIES/libselinux_intermediates/libselinux.a', needed by `out/target/product/totoro/obj/EXECUTABLES/updater_intermediates/LINKED/updater'. Stop.
make: *** Waiting for unfinished jobs....
I think I should halt for today....
update02
recovery.img looks fine, however, there seems to be some problem
if I mount the img (dont ask me how to )
and calculate the size of all the files and folders,
it roughly comes upto 738 kb
but recovery.img is of 4.7 mb
Moreover, If i try
Code:
[B]make -j4 recoveryzip[/B]
there are still errors in install.c (make_ext4fs function errors)
Will try to dig into this again.
and update the thread with my findings :cyclops:
till then, if anyone can advice something, you can.
Update03
No progress yet...
Taking a rest now,
and i need a lil help in this... if anybody has ported before, plz post it here
Brief overview of things:
Getting a recovery.img of 4.7 mb but when executing
Code:
make -j4 recoveryzip
I get the recovery.zip to be 577.6 kb
however, by playing with the code, Its building the extra libs
but NOT adding them to the zip
so, need a proper updater-script
i think you must include it on a kernel., because the recovery of our sgy is not separated to the kernel.,
rio. said:
i think you must include it on a kernel., because the recovery of our sgy is not separated to the kernel.,
Click to expand...
Click to collapse
not really... I believe that if a flashable CWM can be created... a flashable TWRP can also be created...
Anyways, I was going to try dumping it into a prebuilt kernel...
but the issue is my odin doesnt work (in case of bricks)
and it can also hardbrick the device if dumped on to a kernel
Nachiket.Namjoshi said:
not really... I believe that if a flashable CWM can be created... a flashable TWRP can also be created...
Anyways, I was going to try dumping it into a prebuilt kernel...
but the issue is my odin doesnt work (in case of bricks)
and it can also hardbrick the device if dumped on to a kernel
Click to expand...
Click to collapse
oohh sorry i didn't wsee the zip. i thought you just build only img..
i checked the zip and there is no killrecovery.sh which is called by the updater-script..
rio. said:
oohh sorry i didn't wsee the zip. i thought you just build only img..
i checked the zip and there is no killrecovery.sh which is called by the updater-script..
Click to expand...
Click to collapse
oopss... im soo sorry, uploaded the wrong zip
EDIT:
Thread has been updated for the Devs and ppl who can help me.
Nachiket.Namjoshi said:
oopss... im soo sorry, uploaded the wrong zip
Click to expand...
Click to collapse
i checked your zip..
i guess you haven't used any theme.. there is no any images, fonts, twrp,ui.xml in res folder.. and i'm not sure if there are any 240x320 theme officailly available..
and you are missing 30+ libraries and some binaries in the sbin folder..
and mke2fs.conf,twrp.fstab in the /etc folder
and supersu folder
and selinux stuffs..
don't know why you are getting the install.c errors..
which branch are you using.. you need to use latest cm11 with twrp patches or omni branch to build twrp 2.7.x
for the not a prelink map error i think you need to add shared libraries or somethinh like that in prelink-linux-arm.map
anyways.. nice work. and keep trying... you can also ask for help in the official twrp thread here at xda..
psych.half said:
i checked your zip..
i guess you haven't used any theme.. there is no any images, fonts, twrp,ui.xml in res folder.. and i'm not sure if there are any 240x320 theme officailly available..
and you are missing 30+ libraries and some binaries in the sbin folder..
and mke2fs.conf,twrp.fstab in the /etc folder
and supersu folder
and selinux stuffs..
don't know why you are getting the install.c errors..
which branch are you using.. you need to use latest cm11 with twrp patches or omni branch to build twrp 2.7.x
for the not a prelink map error i think you need to add shared libraries or somethinh like that in prelink-linux-arm.map
anyways.. nice work. and keep trying... you can also ask for help in the official twrp thread here at xda..
Click to expand...
Click to collapse
Exactly... missing libs are the reasons, but there is absolutely no way of making these libs individually, well, I can try porting from other device as my last option..
and the most head-banging error is those install.c :/
I use twrp 2.7 branch (refer the link in the OP)
and Im building this with CM7 sources as it was GB
i tried to run your recovery file thru terminal but it doesn't show any action, can u pls upload your source?
i agree with @psych.half
some files are missing that must be call by recovery..
i don't know much about compiling a binary so pls update this thread on your progress. am willing to help
rio. said:
i tried to run your recovery file thru terminal but it doesn't show any action, can u pls upload your source?
i agree with @psych.half
some files are missing that must be call by recovery..
i don't know much about compiling a binary so pls update this thread on your progress. am willing to help
Click to expand...
Click to collapse
Yeh, Im currently updating github with todays changes...
I will now stop for today...
EDIT: Here, are the sources you asked for.
you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.
SpaceCaker said:
you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.
Click to expand...
Click to collapse
Yeah we got our mistake and reverted back to twrp2.3 and cm7 compatible build tools as Minus40 said.
He forgot to update the thread.
and the new twrp.zip in post #3 is twrp2.3,
stopped the work on this for today, will continue tomorrow,
Thanks for pointing it out anyways
Regards
recovery works on GT-S5367? (Galaxy Y TV)
EsromG5 said:
recovery works on GT-S5367? (Galaxy Y TV)
Click to expand...
Click to collapse
I doesn't work with original Galaxy y
Galaxy pocket devs
ı heard about galaxy pocket devs has finished twrp on pocket this can help you
Pocket has also new camera lib for cm9
Only proplem is Audio (On MadTeam)
SpaceCaker said:
you compiled a higher twrp version
this one needs selinux hence the selinux error.
Some stuff needs to be updated to support the base of "kitkat if i say correct
you need to adjust boardconfig proper and such.
it isnt just a simple compile and get file thing
much much research and also you might need to edit the .C# source yourself.
Click to expand...
Click to collapse
Updated thread, sorry, was in a hurry yesterday, forgot to update it just like post #13 by @DC07 says...
Sorry,
So, I can smell the victory though
Good News
I am getting a recovery.zip of a larger size, and finally, the build tools are working great and building the missing libs too...
thanks anyway @Minus40 for giving me the libs, but those libs are not gonna work on this device, its a bit complicated architecture...
Anyway, this is a good break through, ill update the github by the end of the day.
I hope to have a working TWRP by the weekend
presently, build tools error is that it doesnt dump proper permissions for the extra libs, will try give them the proper permissions (which i dont really know, which perms to give), a few days more and it'll be done.
Nachiket.Namjoshi said:
I am getting a recovery.zip of a larger size, and finally, the build tools are working great and building the missing libs too...
thanks anyway @Minus40 for giving me the libs, but those libs are not gonna work on this device, its a bit complicated architecture...
Anyway, this is a good break through, ill update the github by the end of the day.
I hope to have a working TWRP by the weekend
presently, build tools error is that it doesnt dump proper permissions for the extra libs, will try give them the proper permissions (which i dont really know, which perms to give), a few days more and it'll be done.
Click to expand...
Click to collapse
Try twrp 2.2.2.0 for cm7.
I Welcome to the first custom ROM for the note 5 it is light fast with great battery life and a few minor modifications in due time I will add things I appreciate you for coming and trying out my work.. You can flash whatever kernel you enjoy the best. as I see everyone has different preferences.
2 versions.so please mind the instructions for each
You can choose between stock deodex or live on the edge and go with ThrashRom lite.. Your choice... Happy flashing.
The old AOGE downloads will be at the bottom if you need.
Developers-I do not mind if you use this as a base just please give credit.
9-11-2015 THRASHROM 3.4 clean flash
https://www.androidfilehost.com/?fid=24052804347813339
9-8-2015 ThrashRom 2.4 https://www.androidfilehost.com/?fid=24052804347811318
Boh6 modem- https://www.androidfilehost.com/?fid=24052804347812657
BOH4 modem only if you need - https://www.androidfilehost.com/?fid=24052804347809079
Arter kernel http://forum.xda-developers.com/showthread.php?t=3189907
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Features for lite
-rooted
-deodexed
-busybox
-3minit battery mod
-zip aligned
-over 200 fonts
-debloated
-private mode working
-SuperSU built in
-Knox removed
-boot sound removed
-international samsung boot animation
-ext read/write fix - thanks @TEKHD
-Netflix fix
-Removed volume warning
-block messages
-disable sms to mms threshold
-Removed Knox version in settings
-removed input method switcher in statusbar
-27 quick settings toggles
-5 way reboot thanks @foreverloco
-ram fix
-custom boot animation
-save restore messages
-enable camera during call
-increased volume throughout
Working V4A- http://forum.xda-developers.com/showthread.php?p=62783064
-more I'll post later when I get home
donations are not required or expected but if you feel like it.. It will give me more red bull to motivate me! ... paypal.me/JThrasher47
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Instructions - erase all registered fingerprints!BEFORE FLASHING! After you can put back in.
For THRASHROM LITE
Boot into recovery (TWRP OR PHILZ) NOT FLASHFIRE
-1. Make a backup
2. Perform a full wipe
3. Flash rom
( I recommend arter kernel but that is optional)
4.flash xposed (optional)
5.reboot. sometimes can take up to 10 minutes to boot first time.
6.thanks button goes a long way.
Uodated 3minit https://www.androidfilehost.com/?fid=24052804347810304
If you do not like 3 minit remove it with this-https://www.androidfilehost.com/?fid=24052804347809789
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ADD ONS-
Custom boot animation push to system /media and fix permissions
https://mega.nz/#!zN1ARSBA!3IOtVjsJbZH_f-Mz-v3cZ6BkioSThWNynIlsQjrvPas
-3minit for BOH4 ONLY - https://www.androidfilehost.com/?fid=24052804347810304 THANKS @foreverloco
3minit battery mod for AOGE ONLY https://www.androidfilehost.com/?fid=24052804347802688
Xposed framework-http://forum.xda-developers.com/xpo...samsung-lollipop-t3180960/page59#post62556222
noble kernel rebuild 2in case you have reboots with rebuild 3
https://www.androidfilehost.com/?fid=24052804347803877 @drbveb88 thanks for the link I lost lol
Xposed running great!
Old downloada-
Old V2-download- https://www.androidfilehost.com/?fid=24052804347803738
Still dirty flash and flash SuperSU
Old Debloated version- https://www.androidfilehost.com/?f...ww.androidfilehost.com/?fid=24052804347807578
ThrashRom Lite BOH4 with some mods- --please perform a full wipe on this one - https://www.androidfilehost.com/?fid=24052804347808630
list of apps removed--View attachment 3463572
Thanks to @Manh_IT for root and the kernel.
Thanks to @TEKHD for helping behind the scenes.
Thanks to @Chainfire for supersu
Thanks @-viperboy- for the updater script and all the help
Big Thanks to @markbencze for the banner!
Changelog:
V2- removed drive and lookout.. So you don't need to disable
Included kernel and su in rom
9-3-2015- Updated to new base
9-7-2015-removed volume warning
-removed input method switcher
-call/message block In settings
-Netflix fix
-removed Knox version in settings
-removed 3 minit.. Optional to flash
-disable sms to MMS threshhold
9-8-2015- added 27 toggles at boot
fixed private mode
Thanks to @daxgirl and @foreverloco for pointing me in the right direction
9-11-2015
-updated to boh6
-custom boot animation
-ram fix
-5 way reboot thanks @ foreverloco b/c I was being lazy
Thanks for getting things rolling!
dandroid7 said:
Thanks for getting things rolling!
Click to expand...
Click to collapse
No worries.. I'm just as ready as everyone else.. Too bad I don't have kernel knowledge
Misterjunky said:
I found this N920T (note 5) STOCK kernel posted in this forum earlier today but
forgot who posted the link. It's an Odin flash TAR file, perhaps you can use it.
Here is the download link in case you can use it:
https://www.androidfilehost.com/?fid=24052804347800814
Good luck,
Have a great day!
Click to expand...
Click to collapse
Thanks but no stock kernel will not work unless it has been modified.. There's a reason I left it out lol
Misterjunky said:
I found this N920T (note 5) STOCK kernel posted in this forum earlier today but
forgot who posted the link. It's an Odin flash TAR file, perhaps you can use it.
Here is the download link in case you can use it:
https://www.androidfilehost.com/?fid=24052804347800814
Good luck,
Have a great day!
Click to expand...
Click to collapse
I posted that earlier and that is not the stock kernel that is the stock recovery you should give credit where credit's due man not upload that to your own file host..
re: ok
jthrasher47 said:
I posted that earlier and that is not the stock kernel that is the stock recovery you should give credit where credit's due man not upload that to your own file host..
Click to expand...
Click to collapse
I just edited my post and also removed it from the file hosting.
Thanks for letting me know!
Have great day!
Misterjunky said:
I just edited my post and also removed it from the file hosting.
Thanks for letting me know!
Have great day!
Click to expand...
Click to collapse
I will put together a stock boot tar.. And if you send me one for your device I will put together one for your device too. But it's just not cool to take peoples stuff they put together for the community and upload to your host and share it around..
No harm no foul..
Will that stock boot tar be compatible with my s6 edge+ too?
Perhaps since the Note 5 and the s6 edge+ are almost identical
the roms, recovery and the kernel might be interchangeable. ..
Maybe that's just a lot of wishful thinking on my part.
Have a great day, and good luck with the rom.
Sent from my SM-G928T using Tapatalk
Misterjunky said:
Will that stock boot tar be compatible with my s6 edge+ too?
Perhaps since the Note 5 and the s6 edge+ are almost identical
the roms, recovery and the kernel might be interchangeable. ..
Maybe that's just a lot of wishful thinking on my part.
Have a great day, and good luck with the rom.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
I'm not sure. If it has any similarities to the s6 and s6 edge then it might boot but stiff gets broke like screen gets twisted on x Axis and whatnot so I kind of doubt it.. But recovery I'm sure would be fine.
In the build.prop issues like the screen might be an easy fix by renaming
the model numbers or the versions.
To me it looks like the actual rom has parts in it for more than one phone
model and certain files like the build.prop tell the rom which parts to use
depending on the phone's model.
Or am I completely wrong?
Sent from my SM-G928T using Tapatalk
Misterjunky said:
In the build.prop issues like the screen might be an easy fix by renaming
the model numbers or the versions.
To me it looks like the actual rom has parts in it for more than one phone
model and certain files like the build.prop tell the rom which parts to use
depending on the phone's model.
Or am I completely wrong?
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
Yeah I don't mean to sound rude but yea you're wrong the build.prop won't do anything if you make the changes I mean if you flash it and your axis gets inverted you just put in the dialer code *#2663# and press ftp firmware upgrade and it will fix it it..
The kernel modules is what tells it what to do
re: screen issue
jthrasher47 said:
Yeah I don't mean to sound rude but yea you're wrong the build.prop won't do anything if you make the changes I mean if you flash it and your axis gets inverted you just put in the dialer code *#2663# and press ftp firmware upgrade and it will fix it it..
The kernel modules is what tells it what to do
Click to expand...
Click to collapse
Yea, I know about that *#2663#, it saved my bacon when my touchscreen on my
Note 4 went crazy, it was the right resolution and size but none of the touches
corresponded with what was on the screen, however the s-pen did work properly.
After punching in that code and doing the upgrade the phone worked perfectly.
Before finding that code I was about to flush the phone down the toilet. LOL
The problem was all my fault, I by error odin flashed the wrong version of twrp.
Zip failed to flash on my Note5. Restoring my backup, I'll get you the error log when I'm back in Android.
EDIT: Literally nothing helpful...
Code:
Installing '/sdcard/Deodexed-N920TUVU1AOGE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Deodexed-N920TUVU1AOGE.zip'
Updating partition details...
Let me take a look inside the zip and see what's up.
EDIT2: Yeah, you don't have a META-INF folder. No updater-script or anything. No wonder this won't flash. You'll need to fix that before this will flash.
-viperboy- said:
Zip failed to flash on my Note5. Restoring my backup, I'll get you the error log when I'm back in Android.
EDIT: Literally nothing helpful...
Code:
Installing '/sdcard/Deodexed-N920TUVU1AOGE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Deodexed-N920TUVU1AOGE.zip'
Updating partition details...
Let me take a look inside the zip and see what's up.
EDIT2: Yeah, you don't have a META-INF folder. No updater-script or anything. No wonder this won't flash. You'll need to fix that before this will flash.
Click to expand...
Click to collapse
It says the zip is uploading on the OP lol.. I had a bad connection at work and had to stop uploading I'm about to be back and I'm going to start uploading to flashable
jthrasher47 said:
It says the zip is uploading on the OP lol.. I had a bad connection at work and had to stop uploading I'm about to be back and I'm going to start uploading to flashable
Click to expand...
Click to collapse
The ROM I downloaded was complete, not corrupted. It's just missing essential files needed to flash the ROM.
What you're going to upload next, you've tested and it flashes? I can help you if you need.
EDIT: Oh, the link you put up was a system download lol gotcha, missed that part.
-viperboy- said:
The ROM I downloaded was complete, not corrupted. It's just missing essential files needed to flash the ROM.
What you're going to upload next, you've tested and it flashes? I can help you if you need.
Click to expand...
Click to collapse
That is not the ROM that you downloaded that is just the system files that I put there for anyone to use as a base if they need I have to run it through archikitchen to get the updater script unless you have one lying around that will flash on our phones lol
I'm just getting home so I'm about to start running that it should not be long
jthrasher47 said:
That is not the ROM that you downloaded that is just the system files that I put there for anyone to use as a base if they need I have to run it through archikitchen to get the updater script unless you have one lying around that will flash on our phones lol
I'm just getting home so I'm about to start running that it should not be long
Click to expand...
Click to collapse
Yeah, I missed that lol I quickly threw one into the system download, it just successfully flashed, but it's bootlooping after hitting the T-Mobile logo haha I'm at work, so I'll look at it later.
-viperboy- said:
Yeah, I missed that lol I quickly threw one into the system download, it just successfully flashed, but it's bootlooping after hitting the T-Mobile logo haha I'm at work, so I'll look at it later.
Click to expand...
Click to collapse
The lollipop updater scripts are different from jelly bean they have to find the block and mount it that's why I have to run it through the kitchen real fast I just threw this up there the other day for any better qualified people to use as a base.
Now that we have root I'm about to get the updater script and throw it in there and upload
jthrasher47 said:
The lollipop updater scripts are different from jelly bean they have to find the block and mount it that's why I have to run it through the kitchen real fast I just threw this up there the other day for any better qualified people to use as a base.
Now that we have root I'm about to get the updater script and throw it in there and upload
Click to expand...
Click to collapse
No, you can do something like this:
Code:
run_program("/sbin/mount", "-t", "auto", "/system");
and that'll work just fine.
I have a feeling mine bootlooped because of permissions or symlinks, but it wasn't booting far enough for me to get a logcat of it.
-viperboy- said:
No, you can do something like this:
Code:
run_program("/sbin/mount", "-t", "auto", "/system");
and that'll work just fine.
I have a feeling mine bootlooped because of exactly permissions or symlinks, but it wasn't booting far enough for me to get a logcat of it.
Click to expand...
Click to collapse
Exactly.. Archikitchen does all the sym links in the updater script.. I'll admit I'm not that skilled lol I can just build a simple ROM. It seems like you know what you're doing if you can help in any way that would be appreciated other than that the only way I know how to do it is through the kitchen