• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] MidnightRom: Sense 1.5.4

I updated to 1.3.9 and and now it is stuck on the htc screen... might of been my fault since I ignored a message saying it was on "safe mode" and told me to manually wipe dalvik/ cache and format partition.. I also flashed jmz kernel right after flashing the new updated rom. I am a newbie should have been more careful.. Help!! How can I fix this!?
 
529edwin said:
I updated to 1.3.9 and and now it is stuck on the htc screen... might of been my fault since I ignored a message saying it was on "safe mode" and told me to manually wipe dalvik/ cache and format partition.. I also flashed jmz kernel right after flashing the new updated rom. I am a newbie should have been more careful.. Help!! How can I fix this!?
Click to expand...

Just boot into recovery again. Do a quick battery pull. Hold Volume down + Power. Select recovery.

Once in recovery wipe cache and dalvik cache. Format all partitions (except sd card). Flash your rom. Should be fine. Most likely you just need a full wipe and clean install.
 
Brian706 said:
Just boot into recovery again. Do a quick battery pull. Hold Volume down + Power. Select recovery.

Once in recovery wipe cache and dalvik cache. Format all partitions (except sd card). Flash your rom. Should be fine. Most likely you just need a full wipe and clean install.
Click to expand...
Problem is Hboot wont let me select nothing else but to update Radio_V2... wont let me go back to the main screen..

edit: Held volume down and power, went into main hboot screen, pressed power button again to select recovery which doesn't work, it starts loading "parsin...[SD ZIP]" "[1] RADIO_V2" which only allows me to update or Cancel update and results in reboot....
 
With version 1.3.9 my phone has been rebooting while in a calls. This has happened twice already.

I was on 1.3.8 before and did not experience this problem.
 
I don't have an sd reader so I just switched sd cards. I was able to go into recovery 4ext. I am getting this message " ATTN: recovery is in safe mode this is because the following partition is not accessible: "cache" Please enter the wipe menu and wipe cache! If you changed Hboot you should choose to format all partitions (except sd card) Afterwords please reboot recovery.
 
529edwin said:
I don't have an sd reader so I just switched sd cards. I was able to go into recovery 4ext. I am getting this message " ATTN: recovery is in safe mode this is because the following partition is not accessible: "cache" Please enter the wipe menu and wipe cache! If you changed Hboot you should choose to format all partitions (except sd card) Afterwords please reboot recovery.
Click to expand...

Easy. From 4EXT wipe and format cache.
Done. It will get recreated next time you boot.
 
thanx for the help but nothing is working.. I'm thinking maybe my sd stopped working properly since I keep getting that same error message.
 
any one have problems with lag free govenor causing the phone to behave weird after a day or two? i tried increasing the voltages for the speeds above 1.2 ghz in the hopes the cpu was just not getting enough juice but it only seemed to delay the problem but it'll come back.
Anyone want to share there voltages after 1.2 ghz? that'd really help.
 
ENVi3 said:
I've tried running different governors for each core before and I experienced random reboots, so I figure it's best not to mix them.
Click to expand...
thanks, i needed to verify that i wasn't the only one. i guess since i read a few post back that some people were doing split governors that i should try it too. guess it doesn't work for all.
 
nexgenasian said:
thanks, i needed to verify that i wasn't the only one. i guess since i read a few post back that some people were doing split governors that i should try it too. guess it doesn't work for all.
Click to expand...

The real world difference in performance between different governors is pretty minimal, I just don't see any great benefit compared to the known issues while running a different governor on each core.
 
Working on a new version. Thinking of changing kernel from anthrax to mac kernel. I'll see though, after some testing..

Here's a rough changelog

General...
-Add align init.d script
-Change install script
-Update of apps that needed updated

In buildprop...
-Disabled checkin services, error reporting, and logging
-Lots of build.prop changes

In init.d postboot...

-Change read ahead to 1024
-Enable zram compressed memory
-Removed fsync code
-Change wifi settings
-Removed undervolting
-Change memory settings
-Removal of some code that was no longer needed
-Change default clock back to 1.296
 
New version incoming. I consider this one a bigger upgrade than the rest, so a full wipe is DEFINITELY recommended


-No more crashes during calls, wifi no longer takes forever to connect, everything runs faster and smoother, battery life is about the same if not better, clock speeds go down smoother when the screen is turned off preventing more crashes, etc etc etc

1.4.0 12/30/2012 (Latest)
MD5:73fc82d9263b454574738e2ff6e917dd

General...
-Change Kernel to Buttered Toast
-Add zip align init.d script
-Change install script
-Updated Gmail, Titanium Backup, Superuser, Youtube, Google Calendar, AdAway, File Manager
-Removed Smith and QXDM2SD


In buildprop...
-Disabled checkin services, error reporting, and logging
-Changed windowsmgr.max_evets_per_sec to 240
-Change of line "dalvik.vm.dexopt-flags=m=y-"


In init.d postboot...

-Change read ahead to 1024
-Enable zram compressed memory
-Removed fsync code
-Change wifi settings
-Removed undervolting
-Change memory settings
-Removal of some code that was no longer needed
-Change default clock back to 1.296
 
Since im s-off now can i just downloadd the rom from goo and install it stright from recovery withought my pc now?
 
You must log in or register to reply here.
Back
Top Bottom