Database Info

[ROM]Mammon's got Pulse-Beta 11-12-09

First off many thanks to DRIZZY! For all the help getting this bad boy running.
Also many thanks go out to Twisted, Barak, Xdan, Meltus, and Diaztradeinc.These are EXPERIMENTAL BUILDS, so If you do not know what you are doing please refrain yourself from flashing, you might brick your PHONE!
In no way of shape or form will I be held responsible for bricks, flash at YOUR OWN RISK!
THIS ROM IS BASED OFF OF G1-BETA-1.1C added by Diaztradeinc
Mammon’s Change Log:
- Removed Better Terminal, Quick Office, and RoadSync
- Added ‘Reboot’ and ‘Shutdown’
- Added SAM – SlideME
- Removed copybit.*.so
- Mod init within boot.img
______________________________________________
Change Log added from diaztradeinc thread!
Diaztradeinc Change Log:
data is now fixed with swap.
mms
sms
calls
leds
su is now back!
Busybox!
root applications now work!
SD now is readable and mounts! Thank you Twisted!
Meltus audio hack has been added! Thank you Meltus!
Speed of rom is now increased and runs alot smoother!
Uncheck orientation in settings to fix rotation when opening and closing hard keyboard.
Tweaks from Twisted has been added. Thanks Twisted!
Better Terminal has been added.
Wifi tether has been added.
Custom locale has been added.
Quick office has been added.
Superuser has been added.
Automatic Apps 2 SD!!!!
Camera is now working!!!
Boot.img from cyan!! Thanks cyan/xdan
swap is now added and enabled by default!!! thanks twisted.
_______________________________________________
WHAT DOESN'T WORK?
WIFI
BT
Rotation
GPS
Currently testing: Fix for reboot after call ends.
**Note**
#If you call via speakerphone, phone will not reboot.
#To added contacts after setup please check Settings>Data synchronization>Google server settings>Contacts. Then Synchronize now!
#Call + MENU + Power will reboot the phone
****
This is a beta so please bare with me, test it out and post bugs here.
Please know that I am not a Developer. All I did was added files from different rom’s to help pulse stay alive. However I did edit a couple of files. Nothing big at all.
Mammons-Pulse-beta-.08.zip

NVM just read your part of the changelog, Continue on

JAguirre1231 said:
Might want to remove quickoffice and Better Terminal, they're warez
Click to expand...
Click to collapse
Thanks JAguirre

Mammon88 said:
Please look at Mammon's log.
Thanks
Click to expand...
Click to collapse
I did sorry, I might flash this tomorrow, I'm waiting on a call

Wow... Some many error's...At least my rom is running fast.

GREAT WORK the roms looks good but I can't get past the setup

ryansito said:
GREAT WORK the roms looks good but I can't get past the setup
Click to expand...
Click to collapse
hmm..you mustve done something wrong then

I'm comin from a blurr rom ext2 linux swap sdcard I did a wipe before and installed and still cnt get past the setup it reboots at the end of it :{

ryansito said:
I'm comin from a blurr rom ext2 linux swap sdcard I did a wipe before and installed and still cnt get past the setup it reboots at the end of it :{
Click to expand...
Click to collapse
you need to be patient no offense some roms have long boot ups.

Not the boot I'm n the setup and I'm finishing up the setup and it reboots

Ace42 said:
you need to be patient no offense some roms have long boot ups.
Click to expand...
Click to collapse
Thanks Ace! Well for me my rom boots up in less then 3 mins. Before I install any rom at all I do the following setups:
1. Wipe data/factory reset
2. Wipe SD: dalvik-cache
3.part SD: fat32+ext2+swap
4.Repair ext filesystem
5. convert ext2 to ext3
I'm using RA-dream-v1.2.3 http://forum.xda-developers.com/showthread.php?t=566669&highlight=recovery+image

Dev Question!
Have a question for Dev's. How would one edit the libandroid_runtime file without the source?
Thanks!!!

Mammon, I think you should put your change-log on top of Diaz's since yours is more recent.
As for the ROM it feels smooth to me but I'll be waiting on at least a GPS and Rotation fix before I can commit to this. Pulse has been my favorite and I'm hoping you can make a monster out of it.

any idea when the reboot after call will be fixed, it is thr only thing keeping me from this rom

JJbdoggg said:
any idea when the reboot after call will be fixed, it is thr only thing keeping me from this rom
Click to expand...
Click to collapse
I hope soon. I have found a coding mistake made by huawei its related to our 'reboot after call' issue.
This is the reason I would like to know how to edit a lib.so file without the source code.

You could try contacting T-mobile and see if you could get them to talk to Huawei about getting the source for the library released so you can fix it. Telling them what the coding mistake is might help, even if they don't release the source they may fix the error and release it as part of a future Pulse update that you could use. The only other suggestion I've got is to decompile the library and see if you can track the problem down and fix it with a hex editor, if its even possible to do that without messing up all the internal offsets in the code. Not an easy task.

[KERNEL] OTA 1.47.651.1 stock boot.img in update.zip

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

A fix for POLA100, Haret and waiting for notbusy error

I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
It also seems that this error is caused by the double vibration at the beginning of boot process and was solved once by paipo (see this post) by commenting out the vibration part and rebuilding. But those kernel is outdated and misses some latest features and fixes.
So I did the same as paipo but with the latest kernel from the git repository (as of 19.07.2010, revision d5d0a56fae6df779443a82e2d90b7ec8097cb332). zImage is attached to this post. I'll try to update the kernel from time to time.
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post

Disabling the vibration and rebuilding the kernel yourself
So how do you do this?
First of all, follow the steps 1 to 4 of Building kernel For Vogue, Kaiser, and Polaris part from this guide to prepare your building environment.
Now you need to open the arch/arm/mach-msm/board-htcpolaris.c file in your favourite text editor.
Search for vibrate word (it was line 1019). You'll see something like this:
Code:
// vibrate
for (i=0; i<2; i++) {
while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
mdelay(150);
while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
mdelay(75);
}
Remove this part or replace with the following:
Code:
// vibrate
// for (i=0; i<2; i++) {
// while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
// mdelay(150);
// while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
// mdelay(75);
// }
As you can see, all lines now start with two slashes.
Now follow step 5 from the guide, mentioned above. You'll see a menu.
Go to System Type and select Android Optimization accroding to your needs. Then select Exit, than again Exit, then Yes.
Now follow step 6 from the guide. This will take some time. At the end you should see:
Code:
Kernel: arch/arm/boot/zImage is ready
Copy zImage from arch/arm/boot folder to \Storage Card\andboot folder on your device and use it

I update this option in the kernel.
Now double vibration is disable by default.

You are great !!!
leppa said:
I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
...
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Click to expand...
Click to collapse
YOU ARE GREAT !!!
THANKS A LOT A LOT A LOT !!!
THIS EVENING I WILL TRY SURELY !!!!!!!
Only a question: Optimized for Eclair is equal to Optimize to FROYO ?
Can I use your zImage to Froyo RLS 11 ?
Thanks in advance.
Bye

This flag now do nothing, so it's indifferent

GGGGGGGGGGGGGGRRRRRRRRRRRRRRRRRREEEEEEEEEEEEEEEEEAAAAAAAAATTTTTTT !!!!!!
I Have Just tested zImage in attached files.
Froyo seems better reactive, more smooth and rock stable.
Thanks a lot ...
When Video Playback will be solved... I will flash immediately Froyo to give a new life to my Cruise!!!
Thanks thanks thanks!

@foxct2005 : you can flash it month ago!
All these problems are only for haret!

l1q1d said:
I update this option in the kernel.
Now double vibration is disable by default.
Click to expand...
Click to collapse
This change isn't yet in the git repository, is it?
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
The attached kernel images work as they did before - with double vibration on boot and "waiting for notbusy" error. To disable the double vibration (and get rid of the error) add board-htcpolaris.no_boot_vibration=1 to default.txt so this line:
Code:
set cmdline "board-htcpolaris.panel_type=1 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
will look like this:
Code:
set cmdline "board-htcpolaris.panel_type=1 [COLOR="Red"]board-htcpolaris.no_boot_vibration=1[/COLOR] ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
Adding this parameter is mandatory if you suffer from "waiting for notbusy" error.

big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!

leppa said:
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
Click to expand...
Click to collapse
Good idea!
I have long think why developers not added it to the cmdline.

Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..

DmK75 said:
Good idea!
I have long think why developers not added it to the cmdline.
Click to expand...
Click to collapse
I think, they have much more other, more serious, things to do
michasch said:
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
Click to expand...
Click to collapse
nikiiv said:
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
Click to expand...
Click to collapse
You're welcome
If this patch gets upstream, we will not need to rebuild the kernel every time a new build comes out. I already posted it in the Polaris Android Linux Kernel Development Project thread.

thanks leppa,
i tried the froyo one, but for me doesn't work. last days i used the last dzo one, it worked for 2 or 3 days, and now doesn't work again. the only zimage that works is the 29-04 one, but my battery doesn't like it so much

loscassapalle said:
thanks leppa,
i tried the froyo one, but for me doesn't work.
Click to expand...
Click to collapse
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.

leppa said:
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
Click to expand...
Click to collapse
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.

loscassapalle said:
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
Click to expand...
Click to collapse
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).

leppa said:
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
Click to expand...
Click to collapse
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
the animation problem is strange. the zimage of 29-4 works, the animation ends in a few seconds, but the battery life is very short. the last dzo zimage worked for a couple of days, then i had the same problem after a softreset...and this one is the same...
EDIT: now it works... lol

loscassapalle said:
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
Click to expand...
Click to collapse
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
loscassapalle said:
EDIT: now it works... lol
Click to expand...
Click to collapse
So, it started working?

leppa said:
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
So, it started working?
Click to expand...
Click to collapse
i don't know how to edit the zimage...but now it works...i didn't change anything...

loscassapalle said:
i don't know how to edit the zimage...
Click to expand...
Click to collapse
You don't need to. I was talking about editing default.txt as I described in post 8.

Problems installing Froyo on Polaris

Hi!
i wanted to install Froyo on my Polaris NAND. I followed the instructions in this Post: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
I used this package: http://forum.xda-developers.com/showthread.php?t=712310
It works well, NBH Update ok. I have a visible screen. But then the Installation stucks. The last Message is:
Code:
mount: mounting /dev/block/mtdblock3 on /data failed: Device or resource busy Failed
Install module for this Kernel
After a while it continues but with more Error-Messages.
What did i do wrong?
Regards
Volker
P.S.: Sorry about my english...

Left "auto" in fstab part and retry...

Hi!
Ty, i tried that. No Effect. Problems still there. What can i do else?

No Suggestions?

What parameters did you select in atools?

it has something to do with the nbh file,.. you probably created with a/tools, or dl’ed from the website http://it029000.massey.ac.nz/vogue/files/
I had the same problem..
now using rom from:
website
ROM files
probably you need panel 1 for polaris100 (first) and panel 3 for polaris200(version from 2009?)
NBH from androidonhtc.com worked for me..
BUT!!!!........ phone speaker works only on speaker function! normal call is strangely not working....
so..
problem must be in .nbh file or androidinstall file..
I tried to pack my androidinstall with good kernel and flash with right nbh file.. but no success. still had the {install module for kernel} error just like you
hoping for a better solution!
Btw,.. i wanted to install on nand but sd card is already full, is it possible to install on fat32 without running haret.exe from winmo? What are right settings in a-tools for NAND installing?
Click to expand...
Click to collapse

hmmz.. flashing the nbh file made from nbheditor (not the same as a-tools, a-tools is problably based on nbheditor dough..)
did the trick, now i can call with normal built-in ear speaker,.. got mass load of errors instead, plus camera doesnt work

atools is not exactly based on nbheditor...
atools is created from bsg, keymapper and the python porting of nbheditor (original nbheditor was written in mono)
jhonniedj said:
website
ROM files
Click to expand...
Click to collapse
Are deprecated.
For modules you miss to install it. follow all steps of atools guide or a new release with modules alredy in it.

l1q1d said:
What parameters did you select in atools?
Click to expand...
Click to collapse
See Attachments. TY!

Download atools 1.0.4 and select modules

will try again tomorrow, selected all the modules just like Serpens Alatus,
made new androidinstall with stable and development modules..
both gave the same error:
"install modules for this kernel"

What Modules? I use the latest A-Tools...

this ones:
http://webserv.nhl.nl/~rijn0902/modules.PNG
the one you have to flash your polaris with (.NBH file)
the one you have to add to the androidinstall.tgz, and make a new androidinstall.tgz file..

I downloaded the latest A-Tools. Credits say 1.03?
An i use the right modules. But the error stays...

This is the latest...
1.0.4!!!
The right modules are the first.

Tried it again. Still same Error Message.
I own a Polar100. Do i have to set something special??
And, btw, A-Tools credits still show 1.03

Put the androidupdate from sourceforge in your
sd/andboot/
on boot press dpad
select install update
reboot
Ps: thank you for the credits info.

I tried that.
Same Error: Install module for this Kernel
Regards
Volker

Try this http://sourceforge.net/projects/androidhtc/files/modules/androidupdate.tgz/download

l1q1d said:
Try this http://sourceforge.net/projects/androidhtc/files/modules/androidupdate.tgz/download
Click to expand...
Click to collapse
Looks like this fixed it..
before the androidupdate.tgz ==> [Install module for this Kernel]
after the installupdate - androidupdate.tgz ==> Hello Android!
Checked on Kaiser (same procedure as polaris..)
Checked with stable module: 2.6.32-default.tgz
Will try on Polaris, and will try if Camera works asap
Thx for support btw! - camera works on kaiser
Click to expand...
Click to collapse

[Rom]DeodexedBOH6 ThrashRom lite -3.4** update 9-10-2015*

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