[Q] not going in cwm recovery after miui rom instalation - Galaxy S II Q&A, Help & Troubleshooting

I have installed [ROM] MIUI V5 v 3.9.6 [06/09][Update: Full ROM ]!! from http://forum.xda-developers.com/showthread.php?t=2401232 in samsung galaxy s2 i9100g by Temp CWM6 . But now holding down (volumeup+power+home) not taking me in recovery mod. Now who to go in recovery mod to install GAPPS(for same rom) or to install any other other ROM. Also Now it is showing "only emergency calls" not registered on network.

Does the ROM boot normally? Did you complete the initial setup (as per the ROM isntructions)?

thanks for reply
immortalneo said:
Does the ROM boot normally? Did you complete the initial setup (as per the ROM isntructions)?
Click to expand...
Click to collapse
Yes i have completed all set up completely without skipping any step. Rom is working fine now. After one reboot call functioning is also working fine. And I have installed now play store apk file(downloaded from internet somewhere). Now i have play store so I installed many gapps and other apps from store. But I cant go in recovery mod/download mod with any hardware button combination.Is flashing GAPPS from given zip file is necessary. If not, then only thing is-- Is there any other way to get recovery mod again.
My last rom was [ROM] [ROM][i9100G] X-TremExD JB ROM V9 [AOSP|GS4|XZ] by ICS_XD which is AOKP rom. BUT i did all wipes data/facetory reset, dalvik, format data, format system every thing. I have already installed many times other rom. So i think i have not made any installation mistake.
I have one other issue with this phone that any music app(music players or video players, stock or third party) not working properly. Sometime they all work smoothly and sometime all are getting some disturbance while running. They are not getting fc but sometime audio and video not comes smoothly i.e., zigzag type. I have tried 3-4 roms and getting same issue in all roms. I think it is some hardware problem. Remaining everything is fine. Now i an stuck with this MIUI rom.
I have tried holding down (volumeup+volumedown+power), but nothing happening there also. Any suggestions please.

latest ota update solved the issue
latest miui3.9.27 update soved the issue. Now holding down(volumeup+power+home) takes it to Philz touch 5 cwm base version 6.0.3.3.
Should I flash GAPPS now as said in rom installation instructions? But i have installed play store .apk and many other apps from internet. I mean Are Gapps necessary for rom functioning.
Can I install other rom from Philz touch 5 recovery.

siwach said:
latest miui3.9.27 update soved the issue. Now holding down(volumeup+power+home) takes it to Philz touch 5 cwm base version 6.0.3.3.
Should I flash GAPPS now as said in rom installation instructions? But i have installed play store .apk and many other apps from internet. I mean Are Gapps necessary for rom functioning.
Can I install other rom from Philz touch 5 recovery.
Click to expand...
Click to collapse
Yes, you can install other ROMs as long as you follow the instructions given by that ROM's dev. And you can avoid flashing gapps as long as you have no issues using any Google apps. :0

Thanks
immortalneo said:
Yes, you can install other ROMs as long as you follow the instructions given by that ROM's dev. And you can avoid flashing gapps as long as you have no issues using any Google apps. :0
Click to expand...
Click to collapse
Thanks a lot.:good:

Related

[Q] Flashing Rom without trackball!

I was able to flash to GSB 2.4 without a trackball using Rom Manager. After the reboot I flashed gapps and installed the google apps.. all seems fine. Question: was I just lucky that GSB 2.4 had Rom Manager or did Rom Manager stick around from the flash before? My trackball finally went and rolling on white paper doesnt work. Gapps worked fine even after the reboot of the rom - Rom Manager only lets you flash one at a time, then a reboot because I dont have a working trackball. Why does GSB say you need to flash Gapps before the first reboot?
You probably want the version of Amon_RA that doesn't require the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html - use Scenario 3 in the first post.
You need to flash the google apps because CyanogenMod ROMs are not distributed with Google's proprietary applications, especially the market. If you want the market, you need to flash the gapps package.
blacksmithjim said:
I was able to flash to GSB 2.4 without a trackball using Rom Manager. After the reboot I flashed gapps and installed the google apps.. all seems fine. Question: was I just lucky that GSB 2.4 had Rom Manager or did Rom Manager stick around from the flash before? My trackball finally went and rolling on white paper doesnt work. Gapps worked fine even after the reboot of the rom - Rom Manager only lets you flash one at a time, then a reboot because I dont have a working trackball. Why does GSB say you need to flash Gapps before the first reboot?
Click to expand...
Click to collapse
Also, it is quite commonly recommended with any ROM to flash the GAPPs before rebooting. I seem to recall a long time ago that a ROM I flashed didn't even work right if I waited to flash GAPPs until after rebooting and then going into recovery again, which is probably why they just all say to flash it before rebooting.
FYI you can still download ROM Manager free off the market.
If you were inclined you could just add YOUR *wink wink* gapps package into the GSB zip. You would need to have some basic upgrade-script knowledge though.

CM9-stable - google play, gmail and clock issue

Hi, yesterday, I updated my S2 from CM7.2 to version 9 (stable ofcourse). I installed everything from internal SD so instalation was thru the recovery.
All was fine, until i tried to open Gmail app ar Google Play app or clock app. Notihng happens. It didnt start, just blink. No error messege or anything. So I made factory reset. Gmail app was not included, so i downloaded it as an apk. Instalation was succesful, but when I tried to run it again, same problem appears.
Do you have any experience with this issue?
I restored my CM back to 7.2.
Thanx for any advice
codeworkx said:
If you're a bloody noob and getting confused by following simple instructions, go down and read about using the noob-proof ODIN method.
First time installing CyanogenMod 9 to your Galaxy S II, or coming from another ROM:
- READ FAQs: http://teamhacksung.org/wiki/index.php/Experimental:GT-I9100:Frequently_Asked_Questions
- Make sure you're running ICS bootloaders lower than LPH! (if you're unsure, flash the CM9 Resurrection Edition)
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM9 ZIPs to your internal SDCard
- Boot into Recovery
- Flash CM9 zip
- Flash GApps zip
Click to expand...
Click to collapse
Hint: look at the text in bold.
Also, the thread for questions is here: http://forum.xda-developers.com/showthread.php?t=1419102
Did you flash GApps after CM9?
Tried all of it
Made a factory reset on 7.2 and then installed 9.0 stable and gapps. After startig the phone, I get only to the starting screen where I should touch the android to continue (tried to change language, but it doesnt react. Only able to get to emergency call). after touching it says: application stops working. tried to restart phone and make factory reset egain, but its pointless. I cant get thru this instalation.
I´ll try to dowload CM9.2 nightly build. And i will see what I can do with that
OK, got it. I was installing wrong package of gapps.
Wark like a charm now

[Q] CWM/Previous ROM wont let me install any new Roms

I installed JellySnap about a week ago just to try it out and decided that I didnt like it. Alot of force closing of apps going on and that was just annoying. Also couldnt view any pictures in the messenger app or a third party messenger app without the apps force closing. "Google search has unfortuantely stopped." I got around that by installing a new launcher.
Anyway, whenever I go to install a new ROM the installations always abort immediately after the installation begins. I got a status 7 error with one of the roms. A thread I viewed a little earlier advised me to edit one of the scripts to remove the cert verification, alas, that did not help either. So I am at a loss as to what to do. I could have sworn that when I first installed JellySnap it actually went through and overwrote my CWM with an older version it had in its zip package. I could have sworn that I had an earlier version of CWM. The touch version. Now I have to use the volume and home buttons. Version 6.0.1.2-siyah.
Any ideas on how I can fix this and start installing some new roms? Ive tried the latest updates of cyanogenmod, revolution, omega and resurrectionremix so far.
Thanks
What kernel are you on? Try installing philz kernel and reboot recovery. I think that worked for me when I had similar problem a while ago.
Edit. You probably have Apolo kernel, if jellysnap has the option for Dori you could reinstall your ROM and choose Dori in aroma. Good luck.
Sent from my GT-I9100 using xda premium
Try flashing Stock room with odin (sammobile.com) and then flash the room you want
Sent from my TF101 using XDA Premium 4 mobile app
flash a new recovery . and reboot recovery ..you are done . happens with many custom ( kitkat in particular ) as these roms are still in development . flash a new recovery ( 6.0.4.5) reboot recovery and flash the new rom . no need to flash stock via odin or anything else . simple as that .
here's to help you - http://forum.xda-developers.com/galaxy-s2/general/cwm-kit-kat-compatible-t2546597

Bootloop into cwm, no Idea what to do

So first of all, hello
I'm pretty new to this whole universe of custom roms, rooting etc.
My main problem is that I tried to install a custom rom (2 to be exact,
http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
and http://forum.xda-developers.com/galaxy-s3/development/5-1-x-cyanogenmod-12-1-t3066864)
So, the whole rooting process was on this side:
http://www.techverse.net/root-samsung-galaxy-s3-android-4-3-jellybean/
I did everything and it worked like a charm
now I wasn't really sure about the crossfire recovery so I wanted to get cwm (because I had that one on my s2)
I downloaded it here:
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
flashed it via odin 3.07 and everything worked fine
now I just wanted to install a custom rom:
Trying to install the cyanogenmod 12 resulted in a status 7 installation aborted error. I figured that this may have something to do with my
cwm version so I left it alone. The bootloop started on this try. I wiped Dalvik, Cache and Data
I thought that the bootloop resulted because I didn't have a single firmware installed so I tried to install a second rom. This time it was Archidroid. The Aroma launcher started, everything started, I chose my stuff etc. The installation began and I thought it would work. I was dead wrong. Some things failed on the installation but it still resulted in a finished message. This didn't help the bootloop tho. I made a factory reset, wiped dalvik, wiped cache and data, but nothing helped so far.
The only options I haven't tried are restoring my stock firmware and flashing another recovery (most like CF auto root).
Can somebody help me? I should mention that my phone is a samsung galaxy s III gt-I9300
Things u should consider:
Are u 100% sure U have the international galaxy S3 gt-i9300?
Are u sure ur download of the rom was completed? Sometimes the download can end up generating a corrupt zip.
I don't know which CWM versions comes by default, but it may not be updated, in this case u should use the recovery update option inside Aroma from Archidroid 3.1 as in the post (http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859)
If u r a new user maybe u could try an older version of Archidroid, cause the last version is a bit buggy, there is no CM12.1 running perfectly yet, maybe u can try Oldstable: "ArchiDroid 3.0.2 GitHub | XDA Direct | XDA Torrent" from the same post.
About recovery the Philz Touch recovery is easier to use, BUT is no longer updated, the last version i found is philz_touch_6.48.1-i9300-JustArchi.zip in http://d-h.st/users/Archi/?fld_id=34646#files or u may find a newer version here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 (but I'm unable to resolve the DNS for the moment for this link)
TheRuan said:
Things u should consider:
Are u 100% sure U have the international galaxy S3 gt-i9300?
Are u sure ur download of the rom was completed? Sometimes the download can end up generating a corrupt zip.
I don't know which CWM versions comes by default, but it may not be updated, in this case u should use the recovery update option inside Aroma from Archidroid 3.1 as in the post (http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859)
If u r a new user maybe u could try an older version of Archidroid, cause the last version is a bit buggy, there is no CM12.1 running perfectly yet, maybe u can try Oldstable: "ArchiDroid 3.0.2 GitHub | XDA Direct | XDA Torrent" from the same post.
About recovery the Philz Touch recovery is easier to use, BUT is no longer updated, the last version i found is philz_touch_6.48.1-i9300-JustArchi.zip in http://d-h.st/users/Archi/?fld_id=34646#files or u may find a newer version here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300 (but I'm unable to resolve the DNS for the moment for this link)
Click to expand...
Click to collapse
I'm about 90% sure that my s3 is the international version (I'm not really sure how to check that)
as for the recovery update option in Archidroid. I'm actually really afraid that the update could somehow damage the recovery. Is it a safe process?

[ROM][GT-I9190/I9192/I9195][Unofficial Test Builds][8.1.0] LineageOS 15.1 for S4 Mini

After nearly 3 months of work, it's time for the first test build of Lineage 15.1. The LTE variant is the first out, and the 3G variant will follow shortly. The dual-sim variant however might take a lot longer, or maybe never. This because we're now using source built radio interface library and blobs from flo/deb (Nexus 7) devices, and SIM detection is broken on the dual-sim variant with these.
To flash this, you'll need updated TWRP recovery:
serrano3gxx (I9190): https://twrp.me/samsung/samsunggalaxys4mini3gxx.html
serranodsdd (I9192): https://twrp.me/samsung/samsunggalaxys4minidsdd.html
serranoltexx (I9195): https://twrp.me/samsung/samsunggalaxys4minilte.html
Flash in Odin or through your existing TWRP.
Download Gapps: https://wiki.lineageos.org/gapps.html
MindTheGapps is recommended.
Download ROM:
serrano3gxx (I9190): http://www.mediafire.com/file/bgqukbvkerb9lh5/lineage-15.1-20191216-UNOFFICIAL-serrano3gxx.zip/file
serranodsdd (I9192): http://www.mediafire.com/file/iw9z7jvmzo71mrn/lineage-15.1-20191216-UNOFFICIAL-serranodsdd.zip/file
serranoltexx (I9195): http://www.mediafire.com/file/i7evrokeq1d4oqp/lineage-15.1-20191216-UNOFFICIAL-serranoltexx.zip/file
Link to all builds:
serrano3gxx (I9190): http://www.mediafire.com/folder/1ukcz0p7lgx9c/lineage-15.1
serranodsdd (I9292): http://www.mediafire.com/folder/fdgfo6ta1d13w/lineage-15.1
serranoltexx (I9195): http://www.mediafire.com/folder/dbqxvbdb53os3/lineage-15.1
Upgrading from 14.1 is not possible at this point.
Reserved for something.
Thanks a lot for your great work on our device - will try the build after downloading!
Edit: Rom works fine for my after some FCs at the Google Account setup (using micro gapps 08-11-2017).
Aweseome, thanks arco. I too experienced some Google crashes on first boot, but since then ROM works stable as one could wish, also battery life is good. Many settings are not accessable yet, but you wrote that in your post so I knew from the beginning. Gonna keep testing!
I installed the rom in my S4mini LTE. I faced some FCs at first boot (as the other members), but after that, everything is running smoothly.
I rooted the phone with Magisk as AddonSu is only for 14.1.
I am missing the option for "advanced restart", as well as the "buttons" menu options so as to change the long press of home and menu buttons etc.
Other than that, the rom is great. Congrats to the devs.
Similar FCs here (OpenGapps Nano), but no issues other than that. Installing APKs outside the playstore did not work for the standard filemanager and browser yet, but worked for Chrome.
Thats great NEWS!
Hope 3G serrano version is released soon arco!!
Thanks
Added build for 3G variant in first post.
arco68 said:
Added build for 3G variant in first post.
Click to expand...
Click to collapse
Thanks arco68 testing it.
Lineage still not update addonsu extras for Lineage 15
https://download.lineageos.org/extras
This is good to keep su during next updates
Problem to install
Hello Arco68:
Device: i9190 - 3G
I was using custom-twrp-3.1.1-0-serrano3gxx-TRYOUT-signed (attached)
Using this build on recovery i could navigate OK inside SDCARD, when i try to install LINEAGE15 shows an ERROR 7 during installation.
So, i use that recovery to install recovery.img of your first post, but after that, when i navigate to sdcard shows empty (nothing).
I have lineage15 and Gapps on sdcard to install as zip.
So i could not select them. Any ideas to solve this?
I think recovery.img for 3G is buggy. (i test lte recovery to see what happens, i could navitate OK directorties in sdcard, but when installing lineage15 shows device is lte and the firmware is 3g, correct error).
So i think there is something wrong with 3G recovery of post 1
THX @arco68 for your work.
The first look after flashing it on my Phone, really good ,smooth.
The most of my used Options are working.
Bluetooth, mobile Data, Wlan Camera, I will try more and give feedback.
Question: will the TWRP also work for LOS 14.x ?
droopyar said:
Hello Arco68:
Device: i9190 - 3G
I was using custom-twrp-3.1.1-0-serrano3gxx-TRYOUT-signed (attached)
Using this build on recovery i could navigate OK inside SDCARD, when i try to install LINEAGE15 shows an ERROR 7 during installation.
So, i use that recovery to install recovery.img of your first post, but after that, when i navigate to sdcard shows empty (nothing).
I have lineage15 and Gapps on sdcard to install as zip.
So i could not select them. Any ideas to solve this?
I think recovery.img for 3G is buggy. (i test lte recovery to see what happens, i could navitate OK directorties in sdcard, but when installing lineage15 shows device is lte and the firmware is 3g, correct error).
So i think there is something wrong with 3G recovery of post 1
Click to expand...
Click to collapse
First post updated with new recovery for 3G. Something must have gone wrong when building the first one.
bierma32 said:
Question: will the TWRP also for LOS 14.x ?
Click to expand...
Click to collapse
Yes, it will.
arco68 said:
First post updated with new recovery for 3G. Something must have gone wrong when building the first one.
Click to expand...
Click to collapse
THanks now WORKS PERFECT!!!
Thanks arco68
@arco68
I could install LIneage15 and runs OK, BUT when i install gapps 8.0 (micro, or pico for example), lineage starts to shows "google play services has stopped" error.
I have done a full complete WIPE (all advanced wipes on teamwin recovery and factory reset). Full clean of device.
Any ideas or compatibility problem with gapps?
Any alternative way of installing google play so i could install from there?
droopyar said:
@arco68
I could install LIneage15 and runs OK, BUT when i install gapps 8.0 (micro, or pico for example), lineage starts to shows "google play services has stopped" error.
I have done a full complete WIPE (all advanced wipes on teamwin recovery and factory reset). Full clean of device.
Any ideas or compatibility problem with gapps?
Any alternative way of installing google play so i could install from there?
Click to expand...
Click to collapse
Did you install gapps right after installing the rom, before rebooting?
arco68 said:
Did you install gapps right after installing the rom, before rebooting?
Click to expand...
Click to collapse
I try just after the ROM , and also after a complete reboot of the ROM (after). Both scenarios SAME problem. "google play services has stopped, gallery has stopped , etc."
I just re-install above the firmware one more time, and seems google play do a forced reinstall of google play directly from google and now seems working.
Maybe the gapps is outdated or has a bug, as google reinstall an updated version now.
Working version Google Play 8.4.|8-V-all FP 174072765
Google play store 11.7.46 (436-175121617)
Maybe GAPPS has OLD versions for 8.0 . I will check with them from the page
Solved after a second firmware rom flashing of lineage.. it keeps saying error, until google play was forced updated
@arco68 i sad about 19192 but i trust that you'll find a solution for this
After testing the ROM 24 hours seems all ok.
But i saw that on developer options the option to go root "root and applications" to have root access is missing.
How to be root from inside Lineage?
Or do i need to flash magisk?
Regards
droopyar said:
After testing the ROM 24 hours seems all ok.
But i saw that on developer options the option to go root "root and applications" to have root access is missing.
How to be root from inside Lineage?
Or do i need to flash magisk?
Regards
Click to expand...
Click to collapse
You are able to root your device with a extra root package (you can get it from the offiziell LineageOS download page).
droopyar said:
I try just after the ROM , and also after a complete reboot of the ROM (after). Both scenarios SAME problem. "google play services has stopped, gallery has stopped , etc."
I just re-install above the firmware one more time, and seems google play do a forced reinstall of google play directly from google and now seems working.
Maybe the gapps is outdated or has a bug, as google reinstall an updated version now.
Working version Google Play 8.4.|8-V-all FP 174072765
Google play store 11.7.46 (436-175121617)
Maybe GAPPS has OLD versions for 8.0 . I will check with them from the page
Solved after a second firmware rom flashing of lineage.. it keeps saying error, until google play was forced updated
Click to expand...
Click to collapse
Had the same problem when I installed the rom, than did a reboot and after first start flashed Gapps.
I did a clean install with Gapps flashed after the rom, only got some FCs (just ignore them) and it will work.

Categories

Resources