-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[SGS3-R530M] Metropolis Rom [4.3 Touchwiz]
- Thread starter Shabbypenguin
- Start date
ZOOLAHiSHKOBOB
Member
I currently just rooted and have twrp2 for my recovery. I tried flashing all the Versions of this Rom even from the first one. However, every time I flash it. It stays on the bootlogo of the Samsung Galaxy S3. What should I do?
nuttmeg
Extreme Android User
Sounds like you didnt wipe cache or dalvik cache, make sure to wipe them 2 before flashing.
After a month of random reboot under Chiwen AOPK ROM, I was ready for something different. I installed 1.0.5 and fell into a boot loop... Mercifully, TWRP was there to the rescue. I wiped and formatted DATA as well as a Factory Reset, re-installed 1.0.5 and this time it more or less started.
I keep getting a message of "Unfortunately, the process com.android.phone has stopped.", and I get a double vibration and able to move to the next screen. I also get an "Unfortunately, Gallery has stopped." at which point, after clicking Ok, it moves forward. Regardless of clicking OK, the warning message continues to continue with warning messages and locks up for then move forward.
Although it seem to be loading, I am just curious of whether this is the shape of things to come once it is up and running? It is just me, or has anyone run into this issue?
*** Update: Now what is strange is that although I have Factory Reset, wipe Cache/Dalvik, formatted DATA, etc. I just happened to see that some information, in this instance my Owner's Information came up. If I am not mistaken this is not something that would be retained in the google cloud (I don't think), so this should not be showing after a new install, correct. So maybe my phone is not as clean as I might have thought!
I keep getting a message of "Unfortunately, the process com.android.phone has stopped.", and I get a double vibration and able to move to the next screen. I also get an "Unfortunately, Gallery has stopped." at which point, after clicking Ok, it moves forward. Regardless of clicking OK, the warning message continues to continue with warning messages and locks up for then move forward.
Although it seem to be loading, I am just curious of whether this is the shape of things to come once it is up and running? It is just me, or has anyone run into this issue?
*** Update: Now what is strange is that although I have Factory Reset, wipe Cache/Dalvik, formatted DATA, etc. I just happened to see that some information, in this instance my Owner's Information came up. If I am not mistaken this is not something that would be retained in the google cloud (I don't think), so this should not be showing after a new install, correct. So maybe my phone is not as clean as I might have thought!
n4zty
Android Expert
Fix permission in twrp
So, do I fix permissions, then do a clean install of the ROM? Again, it seems like the phone wasn't thoroughly cleaned because now I am getting messages about ROM Control has stopped. Again that was something that was prevalent on AOPK, unless there happeds me be a ROM control under Metropolis.
Nope, that didn't do anything for me. I was excited because it did the updating for apps, although I was surprised to see that it was update 245 apps. Upon looking, I see that I don't have 245 apps available to me, so that confused me. Of course, once that was over, I was back to the FCS issues again, every couple of seconds.
Could it be some issue of me coming from AOPK? Like I said, I was very surprised when I saw my owner information come up although I had not entered that into the new ROM. Whatever the deal is, this is getting very frustrating!
ARocker
Android Expert
The issue is that the installer script for 105 doesnt do what its supposed to. It wont let you install after wiping system yourself but doesnt do a good job wiping system itself. This is a problem when comming from a non touchwiz rom like aokp.
Start from stock then flash 105 or if you feel youre able, you can swap out the meta folder from 105 with the meta folder from 104. This will let you wipe system youself before installing. Problem solved
106 will fix this issue.
Start from stock then flash 105 or if you feel youre able, you can swap out the meta folder from 105 with the meta folder from 104. This will let you wipe system youself before installing. Problem solved
106 will fix this issue.
n4zty
Android Expert
updating apps means the system apps also i would try what arocker suggested seems 1.0.5 didnt work for me coming from a aosp rom either so i instaled 1.0.3 then i installed 1.0.5 over that.
Shabbypenguin
Extreme Android User
this is correct, installing 1.0.3 should work then install 1.0.5 sorry for teh delay on teh update guys i didnt really want to push working on it if there was gunna be what i thought an ota released the within a day or so. but ill go ahead and get the next version up hopefully by tomorrow that should fix all these pesky install issues :/
sorry for teh delay on teh update guys i didnt really want to push working on it if there was gunna be what i thought an ota released the within a day or so. but ill go ahead and get the next version up hopefully by tomorrow that should fix all these pesky install issues :/
Shabbypenguin
Extreme Android User
Its coo. I didnt wanna have to badmouth ur script man
oh its terrible in its current form, ive never worked iwth smart edify before but so far its really cool. ideally i want to be able to have someone flash the rom and based off what it finds on the phone will determine if the flash is good, if they should wipe (and do it automatically) and so much more when im finally done
Martin714
Android Expert
well otas tend to take a long time bro especially from metro lol but i can confirm starting from 1.0.3 then flashing 1.0.5 worksthis is correct, installing 1.0.3 should work then install 1.0.5
Pappy62
Android Expert
^ X2
I've found that going back into TWRP after the first reboot and fixing permissions again will solve the issue.
Maybe it's just my phone, but often I can't fix permissions (or get them to stick) until after an initial reboot.
ARocker
Android Expert
lonestariot83
Well-Known Member
Having the hardest time installing this. Always get failed in big red letters after trying to flash .3 or .5. Currently on BB7.
mike28
Android Expert
Do this get back into recovery don't wipe anything flash 1.0.3 then flash 1.0.5 then wipe cache dalvik cache and factory reset and report back
lonestariot83
Well-Known Member
Okay. Give me a minute boss. Thnx for quick reply.
Okay. That worked. Will try for bit. I hate touchwiz. But the gf phone dont like any rom outside of stock. Her camera becomes useless. This way we can both get most out of having two of these. If anyone has fix for getting the camera to work on BB7 please let me know. I have played with it a bit but still get error abour camera not communicating.
Okay. That worked. Will try for bit. I hate touchwiz. But the gf phone dont like any rom outside of stock. Her camera becomes useless. This way we can both get most out of having two of these. If anyone has fix for getting the camera to work on BB7 please let me know. I have played with it a bit but still get error abour camera not communicating.
lonestariot83
Well-Known Member
And now I have metropolis on here with black bean keyboard and messaging. Hooray. Loving this thing.
THE W
Android Expert
im on blackbean and im gonna make the switch to this.
so i should just flash .3 without wiping anything, reboot, flash .5 without wiping anything, reboot, wipe everything, reboot?