From long time this rom development is at hault. So shall we consider end of further development of Ultimate rom?
Else if some dev willing to continue this project would be great.
Such a great project should go on and on. @joosh3 kindly let us know
I installed this Rom and everything works like a charm except for one peculiar bug.
The whole "messaging" module does not seem to change according to the chosen language in main settings. This whole module is only shown in English, no matter what language you choose.
Has anybody else faced this issue? (with this ROM or any other ROM). Looks like as if the language layer did no effect on this original language module.
Could this whole "Messaging" module be substituted by another messaging module from Philz recovery in order to overwrite it and solve this?
Thanks!... hope someone reads me...
Well, apart from the "Messaging" apk, the "phone" apk and "Mobile network" apk are also in English only.
I was wondering, can I just replace these 2 files "SecMms.apk" and "SecPhone.apk" from another 4.1.2 international custom rom and place them in my N7000's system folder?
Otherwise I think I'll have to install another custom ROM....but I'm just a bit short of time to do that all over again with all configurations, apps and other optimizations I did.
Perhaps this question should be place somewhere else like in "general questions"...provided that it seems there's not much activity in this thread any longer.
Oh, and so far, I still don't know which apk I should replace in order to fix the "Mobile Network" module.
I figured how to re-enable logcat (by commenting last lines in /system/etc/init.d/s73cleaner).
Now I have another issue: looks like, if I update busybox, the old one installs itself on reboot.
Is there a way to prevent this and keep the new busybox?
What Manigma said: On newer versions the music player stops and forces me to restart the phone.
This version has the old fasttoggles and I love it. Also the clock on the patternscreen, which is removed from 5.1 and further.
Only drawback: I have Gravity installed and activated the software buttons. No problem at all, except when showing the phone keys to make a call.
The buttonbar isn't below, but through the phonescreen. But hey, I can live with that !!.
[*]ROM Based on NEW XXLT4 Firmware
[*]NEW PhilZ-cwm6 v4.93.6 with CWM 126.96.36.199 based recovery Touch and exFAT Support – Fixed for bootloop
[*]NEW Modem XXLT3
[*]Updates Over The Air – OTA UpdateMe added on Settings
Jelly Bean 4.1.2
Deleted some useless apps
Added and fixed some more Build.prop tweaks for better optimization, battery life, 3G signal and network, camera, media and more…
Added some more init.d optimizations
Switched to MTP instead of Mass Storage, you can also use Mass Storage
CRT OFF Animation added
Ultimate 4 Way Reboot Options for XXLT4 (just long press power button and decide what you want to do)
Fully working Lockscreen Shortcuts (thanks to eybee1970)
Notification Panel into Settings with possibility to change Toggles order
Call Recording and No ascending ringtone
Multiwindow Hack is available for unlimited apps
SmartRotation and SmartStay Enabled
Ink Effect Mod
Dedicated app to change INK Effect Colours integrated in Settings
Okay, so after reading this entire thread since release of v5, I just wanted to post this:
What to do when experiencing bootloops
So, you flashed this ROM, had your fun and now you are stuck on the "Galaxy Note GT-N7000" screen, and nothing happens.
Did you follow the instructions found in the OP TO THE LETTER when you installed the ROM?
If NO: Wipe and reflash ROM according to instructions.
If YES: Read on.
Here is what you can try:
While stuck in bootloop, hold the POWER button for five to ten seconds. The device will reboot, and it might get out of bootloop. If it boots correctly, have fun. If not, try the next step.
Start the device in CWM then go to advanced - reboot recovery. Wait for recovery to reboot, then select advanced - reboot system. If this doesn't get you past bootloop, try the next step.
Pull out the battery for a few seconds. Put the battery back in and let the device boot. Try this a few times before trying the next step.
Start the device in CWM, and wipe Cache and Dalvik. Try to boot the device. If this didn't work, go ahead and try the next step.
Start the device in CWM and create a backup. Reboot recovery, then restore the backup. Nothing will be lost. After restore complete, reboot the device.
All of the above has been confirmed to work for some users in this thread. It might work for you, or it might not. At least you don't have to roam the thread searching for a solution if you found this post.
If none of the solutions did work for you after several tries, you might want to consider reflashing the ROM according to the instructions in the OP.
Some users are suggesting tinkering with partition sizes. I would strongly recommend not doing this, as this ROM is using the correct partition sizes according to Note requirements.
Also, just a friendly reminder for everyone trying this ROM:
This rom is an experimental leak. That means that it is provided without any warranty of any kind. Everyone flashing this ROM is doing so knowing that it might crash or worse.
If you experience problems, you can report them in this thread. If you need help, post your questions here, and you will get all the help you need (after you tried searching first, of course). If you have suggestions, post them! However, you do not have the right to complain about anything. Recommending another ROM in a developer thread is just impolite. Don't do it.
The developers needs our appreciation to continue sharing their work. They work in their spare time, for free. And everyone benefit from that.
The trolls whine and complains about everything. No one benefits from that.
This was just a friendly reminder
Joosh3: If you would be so kind to put a link to this post in OP, I will personally see to that this post is updated with every confirmed solution to the bootloops as soon as other solutions pops up in this thread.