107 replies to this topic

[harolds5]

GPTom, on Nov 24 2010, 06:31, said:

is it anyhow possible to awake the desire z via the button on the front?

http://forum.xda-dev...ad.php?t=830806

[GPTom]

harolds5, on Nov 24 2010, 20:02, said:

http://forum.xda-dev...ad.php?t=830806

thank you so much

[gr8gorilla]

The pre-baked version is not Deodexed. Just making you aware.

[harolds5]

gr8gorilla, on Nov 25 2010, 06:38, said:

The pre-baked version is not Deodexed. Just making you aware.

Forgive my ignorance, but I don't know what that means.

I also found it easier then following the step for installing was to:
Just copy the file curcial-oj.kl to /system/usr/keylayout/ in the unsigned zip file I created in the kitchen and re-flashed without a data wipe.
Not sure if there are any possible problems being created doing it this way, but I haven't noticed any.

[wvn]

Post nr 1 states:

> In order to use this ROM on your device, you must have a custom recovery image installed (Clockwork Mod).

I used visionary to TEMPROOTmy device, Then I used Titanum backup to install Clockwork Mod.  So literally, my device now fits the requirement: I have Clockwork Mod installed. Right? Anyway, I am a bit hesitant. Will this work, or should I do a PERMROOT?


EDIT:
Well well, isn't this a busy forum.
On other forums I have found the answer. The first post of this thread is incomplete. You need full root and S-OFF.
Thanks all for helping.

Edited by wvn, 08 December 2010 - 07:26 PM.

[sonofabit]

Any updated ETA on this? I'm really looking forward to the next release.  

[toucan509]

jdschrock, on Nov 17 2010, 17:57, said:

Alright so I've only just rooted my G2 with Visionary r13, and successfully gained perm root and S-off. So thank you very much for all the hard work on that. I also went ahead and flashed your MCR with Sense, and that also worked flawlessly. I'm really enjoying the UI. Here is where I've hit a bump in the road though. In going through the process of installing the MCR I was also checking out the work of CyanogenMod, as I have used their ROMs before. You both had the same directions with the exception of yours not needing me to wipe my system or having a seperate file for google apps. The long and short of it is that I did in fact do a Nandroid backup, wiped my device, and installed your MCR. The ROM works well as a whole, but I find myself unable to restore my backed up apps with no working app manager/market. I understand that HTC Likes is meant for app downloads but it continually force closes whenever I try to install something. What's more is that I seem to have lost the Clockwork Recovery, and can't reboot into recovery to reistall the ROM or switch to a different one. Any idea to the source of my problem here? Again I do appreciate all the hard work, and apologize for the length of my post. I just wanted to be concise with my information. Thank you in advance for any help you or anyone else can provide.

Paul

Ive had my G2 rooted for some time now and last night decided to try out this MCR Sense Rom on my G2. It works flawlessly, but I am not a big of the whole interface and decided to go back to my original G2 Rom, and this is where I am stuck. I did everything the poster I quoted did before flashing this MCR onto my phone,and am basically having the same issue. My G2 apparently has lost root access after flashing this Rom. I cant get SuperUser permissions for anything, Clockwork Mod will not work. When I boot into Recovery mode and I select any of the options, all I get is a black, blank screen. Ive tried installing Visionary to see if would let me gain root access again, and It just gets stuck in a loop and never does anything. I just want to go back to my factory G2 Rom, any help would be very much appreciated. Thanks in advance.

[Fredisco]

Thanks for the Kitchen Paul, you r0ck!. No issues at all to report after using it quite a lot for a couple of days.  

[Armani G]

Is there going to be an update soon?

[fjuicy]

Hi,
am having FC with com.htc.bgp and com.htc.laputa(in the car panel when i hit premium navigation)

[da900]

Hi, Paul. I like your MCR ROMs. And this one is also very good. But the new version of  leaked RUU for DZ was published on XDA. HERE. Are you going to update MCR for DZ with this and adding some enhasements (just like in Desire MCR ROM) such as new kernel (Pershoot or Cyanogen), overlocking, deodexed etc.?

Edited by da900, 21 December 2010 - 08:27 AM.

[mardenator]

i just tried to flash this and the installation aborted. i did a full wipe and flashed as directed, but it aborted the installation.

[Michael Perry]

mardenator, on Dec 27 2010, 15:07, said:

i just tried to flash this and the installation aborted. i did a full wipe and flashed as directed, but it aborted the installation.

Is there going to be a new reelase based on the 1.72 sense sources like Virtuous over on XDA? I'd like to try a few different sense ROMs on my G2. Virtuous is pretty cool and I think its based on a later sense release.

Thanks!

[PaulOBrien]

Changelog

30/Dec r2

• Based on 1.72 release
  
• Updated all components (in turn compressed and optimised)
  
• Added init.d support
  
• Updated busybox
  
• Added terminfo

[PaulOBrien]

Changelog

30/Dec r2

• Based on 1.72 release
  
• Updated all components (in turn compressed and optimised)
  
• Added init.d support
  
• Updated busybox
  
• Added terminfo

[sonofabit]

Paul, on Dec 30 2010, 18:04, said:

Changelog

30/Dec r2

• Based on 1.72 release
  
• Updated all components (in turn compressed and optimised)
  
• Added init.d support
  
• Updated busybox
  
• Added terminfo

Thanks! Will try this out now.

[AlThePost]

Sorry Paul..... seems like there may be a gremlin in the works.

I performed a full wipe of r1 and flashed r2 - no issues with that and the initial setup went smoothly. Love the new boot screen btw! I then reinstalled Root Explorer.... again no problem. Superuser Permissions asked to grant access, I accepted, RE worked. I then reinstalled Titanium Backup, but when run it is unable to obtain root access and Superuser Permissions force-closes. I've tried downloading a new copy of Busybox from within TiB to no avail, uninstalled/reinstalled it several times and reflashed the ROM - same result.

[kyhwana2]

AlThePost, on Dec 31 2010, 13:43, said:

Sorry Paul..... seems like there may be a gremlin in the works. :(

I performed a full wipe of r1 and flashed r2 - no issues with that and the initial setup went smoothly. Love the new boot screen btw! I then reinstalled Root Explorer.... again no problem. Superuser Permissions asked to grant access, I accepted, RE worked. I then reinstalled Titanium Backup, but when run it is unable to obtain root access and Superuser Permissions force-closes. I've tried downloading a new copy of Busybox from within TiB to no avail, uninstalled/reinstalled it several times and reflashed the ROM - same result.

I get this too, except the first app (that needs root) I ran was Titanium Backup, then every other root app after that doesn't work. I get a su force close when I type "su" in connectbot for example. Here's a copy of the log.

V/Performance( 2864): >>AppBindData{appInfo=ApplicationInfo{4743cef0 com.noshufo
u.android.su}} handleBindApplication
V/Performance( 2864): >>android.app.ActivityThread@4743bd08 newApplication
V/Performance( 2864): <<android.app.ActivityThread@4743bd08 newApplication, 0ms
V/Performance( 2864): >>android.app.Application@47440ab0 onCreate
V/Performance( 2864): <<android.app.Application@47440ab0 onCreate, 1ms
V/Performance( 2864): <<AppBindData{appInfo=ApplicationInfo{4743cef0 com.noshufo
u.android.su}} handleBindApplication, 9ms
V/Performance( 2864): >>com.noshufou.android.su.SuRequestReceiver@474494d8 onRec
eive:Intent { act=com.noshufou.android.su.REQUEST cmp=com.noshufou.android.su/.S
uRequestReceiver (has extras) }, tid=2864
I/Database( 2864): sqlite returned: error code = 14, msg = cannot open file at l
ine 27206 of [42537b6056]
I/Database( 2864): sqlite returned: error code = 14, msg = unable to open databa
se file
E/Database( 2864): sqlite3_exec to set journal_mode of /data/data/com.noshufou.a
ndroid.su/databases/permissions.sqlite to WAL failed
D/AndroidRuntime( 2864): Shutting down VM
W/dalvikvm( 2864): threadid=1: thread exiting with uncaught exception (group=0x4
0025a70)
E/AndroidRuntime( 2864): FATAL EXCEPTION: main
E/AndroidRuntime( 2864): java.lang.RuntimeException: Unable to start receiver co
m.noshufou.android.su.SuRequestReceiver: android.database.sqlite.SQLiteException
: unable to open database file
E/AndroidRuntime( 2864):        at android.app.ActivityThread.handleReceiver(Act
ivityThread.java:3018)
E/AndroidRuntime( 2864):        at android.app.ActivityThread.access$3200(Activi
tyThread.java:136)
E/AndroidRuntime( 2864):        at android.app.ActivityThread$H.handleMessage(Ac
tivityThread.java:2239)
E/AndroidRuntime( 2864):        at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime( 2864):        at android.os.Looper.loop(Looper.java:143)
E/AndroidRuntime( 2864):        at android.app.ActivityThread.main(ActivityThrea
d.java:5068)
E/AndroidRuntime( 2864):        at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime( 2864):        at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime( 2864):        at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:858)
E/AndroidRuntime( 2864):        at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:616)
E/AndroidRuntime( 2864):        at dalvik.system.NativeStart.main(Native Method)

E/AndroidRuntime( 2864): Caused by: android.database.sqlite.SQLiteException: una
ble to open database file
E/AndroidRuntime( 2864):        at android.database.sqlite.SQLiteDatabase.dbopen
(Native Method)
E/AndroidRuntime( 2864):        at android.database.sqlite.SQLiteDatabase.<init>
(SQLiteDatabase.java:1906)
E/AndroidRuntime( 2864):        at android.database.sqlite.SQLiteDatabase.openDa
tabase(SQLiteDatabase.java:889)
E/AndroidRuntime( 2864):        at android.database.sqlite.SQLiteDatabase.openOr
CreateDatabase(SQLiteDatabase.java:923)
E/AndroidRuntime( 2864):        at android.database.sqlite.SQLiteDatabase.openOr
CreateDatabase(SQLiteDatabase.java:916)
E/AndroidRuntime( 2864):        at android.app.ContextImpl.openOrCreateDatabase(
ContextImpl.java:589)
E/AndroidRuntime( 2864):        at android.content.ContextWrapper.openOrCreateDa
tabase(ContextWrapper.java:203)
E/AndroidRuntime( 2864):        at android.content.ContextWrapper.openOrCreateDa
tabase(ContextWrapper.java:203)
E/AndroidRuntime( 2864):        at android.database.sqlite.SQLiteOpenHelper.getW
ritableDatabase(SQLiteOpenHelper.java:98)
E/AndroidRuntime( 2864):        at com.noshufou.android.su.DBHelper.<init>(DBHel
per.java:58)
E/AndroidRuntime( 2864):        at com.noshufou.android.su.SuRequestReceiver.onR
eceive(SuRequestReceiver.java:23)
E/AndroidRuntime( 2864):        at android.app.ActivityThread.handleReceiver(Act
ivityThread.java:3003)
E/AndroidRuntime( 2864):        ... 10 more
I/Process ( 1301): Sending signal. PID: 2864 SIG: 9
I/global  ( 1301): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
I/global  ( 1301): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
W/ActivityManager( 1301): Process com.noshufou.android.su has crashed too many t
imes: killing!
D/ProcessManager( 1301): executeProcess(): waiting for child process ...
D/ProcessManager( 2872): executeProcess(): in child process ...
D/ProcessManager( 2872): executeProcess(): in child process, after dup2()
D/ProcessManager( 2872): executeProcess(): in child process, after closePipes()
D/ProcessManager( 2872): executeProcess(): in child process, after fcntl()
D/ProcessManager( 2872): closeNonStandardFds(): skipFd=[161]
D/ProcessManager( 2872): closeNonStandardFds(): after getrlimit(): RLIMIT_NOFILE
=[7], rlim_max=[1024]
D/ProcessManager( 1301): executeProcess(): read child status count=[0], result=[
15909224]
I/global  ( 1301): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
D/ProcessManager( 1301): executeProcess(): waiting for child process ...
D/ProcessManager( 2873): executeProcess(): in child process ...
D/ProcessManager( 2873): executeProcess(): in child process, after dup2()
D/ProcessManager( 2873): executeProcess(): in child process, after closePipes()
D/ProcessManager( 2873): executeProcess(): in child process, after fcntl()
D/ProcessManager( 2873): closeNonStandardFds(): skipFd=[161]
D/ProcessManager( 2873): closeNonStandardFds(): after getrlimit(): RLIMIT_NOFILE
=[7], rlim_max=[1024]
D/ProcessManager( 1301): executeProcess(): read child status count=[0], result=[
15909224]
I/global  ( 1301): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
D/dalvikvm( 1301): GC_FOR_MALLOC freed 15232 objects / 2089384 bytes in 111ms
D/WidgetView_Card( 1451): handle message: 9006, message parameter: 0
D/ProcessManager( 1301): executeProcess(): waiting for child process ...
D/ProcessManager( 2874): executeProcess(): in child process ...
D/ProcessManager( 2874): executeProcess(): in child process, after dup2()
D/ProcessManager( 2874): executeProcess(): in child process, after closePipes()
D/ProcessManager( 2874): executeProcess(): in child process, after fcntl()
D/ProcessManager( 2874): closeNonStandardFds(): skipFd=[161]
D/ProcessManager( 2874): closeNonStandardFds(): after getrlimit(): RLIMIT_NOFILE
=[7], rlim_max=[1024]
D/ProcessManager( 1301): executeProcess(): read child status count=[0], result=[
5528784]
I/global  ( 1301): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
D/ProcessManager( 1301): executeProcess(): waiting for child process ...
D/ProcessManager( 2875): executeProcess(): in child process ...
D/ProcessManager( 2875): executeProcess(): in child process, after dup2()
D/ProcessManager( 2875): executeProcess(): in child process, after closePipes()
D/ProcessManager( 2875): executeProcess(): in child process, after fcntl()
D/ProcessManager( 2875): closeNonStandardFds(): skipFd=[161]
D/ProcessManager( 2875): closeNonStandardFds(): after getrlimit(): RLIMIT_NOFILE
=[7], rlim_max=[1024]
D/ProcessManager( 1301): executeProcess(): read child status count=[0], result=[
5528784]
I/global  ( 1301): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
D/WidgetView_Card( 1451): on Query Complete: android.content.ContentResolver$Cur
sorWrapperInner@4762ad88
D/WidgetView_Card( 1451): status: 2
^C

[kyhwana2]

So clearing the superuser data in manage applications lets me run a single root app, it asks for super user permissions and works fine, but then it crashes again when I run a second.

That is, I clear the data, run adfree, which works. Close it and then run TI backup and su crashes.. Any ideas?

[Abra Cadabra]

Thanks for the update Paul.

A couple of issues. Getting SU force closes as mentioned by others.

Also unable to install ROM manager off market. Downloads but won't install.

Otherwise all seems ok so far.