[ROM] [LOLLIPOP] [LMY48G] [Synman's GwT ROM for Tilapia] [carcosa] [2015/07/03]

H

hitony

Member
Apr 14, 2013
5
0
0
Apr 16, 2013 at 9:37 PM
Synman said:
If you would try just installing RC3 and allow your N73G to fully boot at least once before installing Google Apps. Also ensure you have a valid userdata partition prior to performing the RC3 install. The easiest way to do this is perform a factory reset of your N73G prior to installing RC3 or by using fastboot to flash userdata from the google binaries.

In all cases, ensure you have a fully functional install (at least one full boot) prior to proceeding to the next step.
Click to expand...
I still cannot start up after installing RC3 from JDQ39 factory image (4.2.2). Here are my steps:

1) Enable USB debug mode
2) Download RC3.zip in my SD card
3) Factory Reset my Nexus 7
4) Connect the Nexus 7 to my laptop
5) Install CWM recovery on Linux
i) ./fastboot devices
ii) ./fastboot flash recovery recovery-clockwork-touch-6.0.2.3-grouper.img
6) Enter recovery mode
7) Flash zip from SD Card
8) Reboot after successfully install RC3
9) Stuck in colorful X animation...

Thanks for your help in advance.
 
H

hitony

Member
Apr 14, 2013
5
0
0
Apr 17, 2013 at 5:00 AM
Synman said:
Have you tried using TWRP? I'm grasping but it does appear that you are using a grouper recovery... Would like to know the results you get with a recovery built specifically for tilapia.

Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
I apologize for my mistake. That command is that I copied from a post on CWM recovery. In fact, what I used was recovery-clockwork-touch-6.0.2.3-tilapia.img. I wonder whether someone has installed RC3 ROM on Nexus 3G from stock 4.2.2.

I have a few concerns about TWRP. Although TWRP comes later than 4.2.2, there is no proof that TWRP supports 4.2.2. On the other hand, TWRP has a issue to enter recovery mode. I also suspect that there will be painful for future OTA updates, just as it happened from 4.2.1 to 4.2.2.

Btw, this xda post said that we may use native dialer (phone.apk) over skype to perform phone calls on Nexus 3G, by modifying framework-res.apk and bools.xml entry to name="config_voice_capable">true. I wonder could you integrate such hack into your ROM. There is a tool to ease your modification of framework-res.apk.

Thanks.
 
A

azanor

Member
Apr 19, 2013
6
0
0
Apr 23, 2013 at 5:04 PM
hitony said:
I still cannot start up after installing RC3 from JDQ39 factory image (4.2.2). Here are my steps:

1) Enable USB debug mode
2) Download RC3.zip in my SD card
3) Factory Reset my Nexus 7
4) Connect the Nexus 7 to my laptop
5) Install CWM recovery on Linux
i) ./fastboot devices
ii) ./fastboot flash recovery recovery-clockwork-touch-6.0.2.3-grouper.img
6) Enter recovery mode
7) Flash zip from SD Card
8) Reboot after successfully install RC3
9) Stuck in colorful X animation...

Thanks for your help in advance.
Click to expand...
Synman said:
Have you tried using TWRP? I'm grasping but it does appear that you are using a grouper recovery... Would like to know the results you get with a recovery built specifically for tilapia.

Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
I have the same problem as Hitony above.

I rooted my 3G Nexus 7 using Wug's Nexus Root Toolkit and it installed TWRP as the recovery option. I wiped my device and flashed the ROM from zip and afterwards wiped the cache and Dalvik as was prompted after flashing but when I rebooted my device was stuck on the X animation screen.

Did I do something wrong?
 
U

UnicornKaz

Senior Member
May 5, 2007
1,204
139
0
Southern Ontario
Apr 26, 2013 at 3:44 PM
hitony said:
I apologize for my mistake. That command is that I copied from a post on CWM recovery. In fact, what I used was recovery-clockwork-touch-6.0.2.3-tilapia.img. I wonder whether someone has installed RC3 ROM on Nexus 3G from stock 4.2.2.

I have a few concerns about TWRP. Although TWRP comes later than 4.2.2, there is no proof that TWRP supports 4.2.2. On the other hand, TWRP has a issue to enter recovery mode. I also suspect that there will be painful for future OTA updates, just as it happened from 4.2.1 to 4.2.2.

Btw, this xda post said that we may use native dialer (phone.apk) over skype to perform phone calls on Nexus 3G, by modifying framework-res.apk and bools.xml entry to name="config_voice_capable">true. I wonder could you integrate such hack into your ROM. There is a tool to ease your modification of framework-res.apk.

Thanks.
Click to expand...
actually, If you go back to that post where you'd posted the "issue"... the problem is already "SOLVED"

http://forums.androidcentral.com/ne...oted-difficulty-booting-twrp.html#post2700879

It was NEVER an issue... it has always been PILOT ERROR/USER ERROR !! LOL :laugh:

I am living proof of using SynMan's RC3 since day one due to must have fully functional MMS feature - ( been on his RC1 and now RC3...skipped RC2 because it was not stabled)- and TWRP ( v2.5.0.0 latest ) combination. ;)

~~~~~
 
Last edited:
A

azanor

Member
Apr 19, 2013
6
0
0
May 3, 2013 at 3:16 PM
I've updated my TWRP to version 2.5 and retried installing RC3 but my N7 still gets stuck at the Boot animation.

I followed all the steps but I really don't know what I'm doing wrong:(
 
Synman

Synman

Recognized Developer
Nov 2, 2010
826
547
0
Outside Philadelphia
www.shellware.com
Jul 26, 2013 at 6:17 AM
I've got all the basics working (SMS/MMS/SIP) ... having an issue with Location Services... exactly like the problems I had very early on with 4.2.1 but I'm sure I'll figure it out again.

The system app notification bar now works out of the box and Google finally fixed the APN editor's layout so that the edit and discard buttons are present. Sadly they didn't fix the SIP Providers layout. Root cause here is that the dialog layout they use for them doesn't size properly at our DPI setting.

I haven't found a version of Wallet I can get to work but I still have some build.prop changes to make that might help there.

4.2.2 Gapps does not work. It crashes the AOSP keyboard. However there are experimental versions of it available that are working fine, just not as feature rich as some of the existing ones.
 
  • Like
Reactions: shevich, iBuzman, zard and 3 others
T

tschork

Member
May 20, 2007
27
8
0
Jul 26, 2013 at 11:14 AM
Synman said:
I've got all the basics working (SMS/MMS/SIP) ... having an issue with Location Services... exactly like the problems I had very early on with 4.2.1 but I'm sure I'll figure it out again.

The system app notification bar now works out of the box and Google finally fixed the APN editor's layout so that the edit and discard buttons are present. Sadly they didn't fix the SIP Providers layout. Root cause here is that the dialog layout they use for them doesn't size properly at our DPI setting.

I haven't found a version of Wallet I can get to work but I still have some build.prop changes to make that might help there.

4.2.2 Gapps does not work. It crashes the AOSP keyboard. However there are experimental versions of it available that are working fine, just not as feature rich as some of the existing ones.
Click to expand...
This rom is the reason I buyed my nexus 7. I tried a lot of sip dialer, but the bluetooth integration is lacking in all of them.
Thanks for your efforts to bring us the stock sip dialer, I really appreciate it.
 
  • Like
Reactions: Synman
A

azanor

Member
Apr 19, 2013
6
0
0
Aug 1, 2013 at 10:15 AM
Synman said:
I've got all the basics working (SMS/MMS/SIP) ... having an issue with Location Services... exactly like the problems I had very early on with 4.2.1 but I'm sure I'll figure it out again.

The system app notification bar now works out of the box and Google finally fixed the APN editor's layout so that the edit and discard buttons are present. Sadly they didn't fix the SIP Providers layout. Root cause here is that the dialog layout they use for them doesn't size properly at our DPI setting.

I haven't found a version of Wallet I can get to work but I still have some build.prop changes to make that might help there.

4.2.2 Gapps does not work. It crashes the AOSP keyboard. However there are experimental versions of it available that are working fine, just not as feature rich as some of the existing ones.
Click to expand...
Thanks for the good work you're doing. Looking forward to the new release of your ROM.

Also, I was able to sort out the problem with installing your ROM on my Nexus 7, turns out I mixed up some of the steps which was why it didn't proceed past the boot animation.:laugh:
 
Synman

Synman

Recognized Developer
Nov 2, 2010
826
547
0
Outside Philadelphia
www.shellware.com
Aug 11, 2013 at 5:31 PM
finally have found a couple minutes to work on this. Fixed location services today... I'm gonna put this snippit right here for the next time I forget to add the fused provider into the device config.

Code: 
<string-array name="config_locationProviderPackageNames" translatable="false">
        <!-- The standard AOSP fused location provider -->
        <item>com.android.location.fused</item>
        <!-- The Google Network Location Services location provider -->
        <item>com.google.android.location</item>
</string-array>
Just might have something out there today.
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone