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

Root [ROM] MTDEV-CM7 build 2013-03-03

RobD68 said:
In regards to MTDEV-CM7 build 20120921:
Wiped cache, wiped Dalvik cache, install from zip. Phone hangs on initial splash screen.

Updating from the 0915 build. Flashed twice, verified MD5 is a match.
Flashed back to 0915 build and phone boots OK.

Just a heads-up. I did not try a full wipe yet.
Click to expand...

You will need to do a full wipe as many libs have changed from that version to this version. This is the exact reason why we always recommend full wipes and reloads.
 
When I went to load, Bootloader is not loading corectly - just a TopHat logo.
Has 5 "can't mount / open" lines?

Never had this problem before.

Any hints?
 
g60madman said:
You will need to do a full wipe as many libs have changed from that version to this version. This is the exact reason why we always recommend full wipes and reloads.
Click to expand...

Just did a full wipe, dalvik wipe and I'm getting the freeze on Motorola splash screen.
 
mattbodin said:
i ran 1700 without issue through benchmarks and stress tests for hours one night. the following day i ramped up to it(from 1600) to play a game and the phone rebooted nearly immediately. i haven't tested it since then so i cant say more.
Click to expand...

1700 works well until the phone gets too hot, though if you use SetCPU and put a heat profile, then 1700 might be usable
 
Here are the stats, for frequency usage, I know it is only 12 hours, mostly since my phone rebooted, just thought I would put them up since I'll update to the new release
 

Attachments

  • screenshot-1348239591370.png
    screenshot-1348239591370.png
    111.5 KB · Views: 106
  • screenshot-1348239643486.png
    screenshot-1348239643486.png
    113.4 KB · Views: 111
calitrippin said:
Here are the stats, for frequency usage, I know it is only 12 hours, mostly since my phone rebooted, just thought I would put them up since I'll update to the new release
Click to expand...

I'm going to check if there were any changes to the kernel, if not I would ask anybody who is testing for me to flash my test kernel also.

Or maybe wait to flash the new ROM. I really am trying to save a few drops of battery life.
 
dsmryder said:
I'm going to check if there were any changes to the kernel, if not I would ask anybody who is testing for me to flash my test kernel also.

Or maybe wait to flash the new ROM. I really am trying to save a few drops of battery life.
Click to expand...

I did the normal full wipe, cache, dalvik cach, then installed new rom, gaaps, and the test kernal right now, stuck on splash image, gonna try again and if it doesn't work might try to re download it

edit: problem seems to be the updated rom, I've been having trouble with the usb cable so it might have not fully downloaded on my phone
 
calitrippin said:
I did the normal full wipe, cache, dalvik cach, then installed new rom, gaaps, and the test kernal right now, stuck on splash image, gonna try again and if it doesn't work might try to re download it
Click to expand...

The md5 was correct on my download.
I tried to reload twice without success :(
 
g60madman said:
You will need to do a full wipe as many libs have changed from that version to this version. This is the exact reason why we always recommend full wipes and reloads.
Click to expand...

I did a full wipe, factory reset, wipe cache, wipe dalvik cache, install rom, gapps, but the rom wont get past the splash image
 
I always set my clock settings to 122/1401, for some reason in the 09-21 build my setting won't stick after reboot. Anyone else having this issue?
 
I cleared dalvik, factory reset, and formated /system using CWM and the new version worked fine for me. If you haven't already tried formating /system, give that a try; there could be something old in there screwing it up.
 
calitrippin said:
it you make sure you clicked the box for set on boot?
Click to expand...

Yes, this is with set on boot checked.
I know on a previous build sometimes wifi enabled would cause things to not stick so I've tried it both with & without wifi enabled. Nothing will get it to stick. Weird...
 
aakyl said:
I cleared dalvik, factory reset, and formated /system using CWM and the new version worked fine for me. If you haven't already tried formating /system, give that a try; there could be something old in there screwing it up.
Click to expand...

just tried adding the extra step of going into mounts and doing format /system on top of doing the normal factory reset, clear cache, clear dalvik cache, didn't change anything still stuck on the splash image
 
calitrippin said:
just tried adding the extra step of going into mounts and doing format /system on top of doing the normal factory reset, clear cache, clear dalvik cache, didn't change anything still stuck on the splash image
Click to expand...

Since people are having all kinds of problems I downloaded the ROM from dl.mtdev.us. from my phone. I then installed a nifty free app called MD5 Checker the md5 list the exact version online. I booted into recovery using mantera's 5.5.0.4. I did a wide data / factory reset and then the dalvik wipe. After that I installed the new ROM and gapps and it's hanging up on the motorola screen. I will see what's going on.
 
OK,

I got to finally work after resetting permissions. calitrippin give that a shot and let me know if it works. I think this maybe a problem of moving from CM9 back to CM7 as I changed a lot of permissions in CM9 based on changes for Ice Cream Sandwich.
 
You must log in or register to reply here.
Back
Top Bottom