[Q] Real difficulties installing CM11 - Galaxy S Advance I9070 Q&A, Help & Troubleshooting

I currently am on CM 10.2, which installed fine and is working nicely. I decided to try out CM11 and ran into a bunch of problems.
First off, following the instructions, I booted into recovery, wiped/reset, and attempted to flash the current cm11 zip file. I tried this several times because each time I got an error message saying some changes failed. Dead in the water. I restored 10.2 and tried again, this time following a suggestion to first extract boot.img and flash that with UKF, then flash CM11 and the KK apps from recovery. I was able to do those steps, but when it came to rebooting to system, the whole thing hung up for about 10 minutes, then rebooted. At that point I thought all was good, and I was up and running on CM11. I noticed the camera was FCing, so I thought I'd better reboot. But when I try to shut down or reboot, the phone gets stuck (in either process). The only way to close the phone is to pull the battery. So, now I don't know what to do to get this phone running on CM11. Any suggestions?

http://forum.xda-developers.com/showthread.php?t=2582060 use this to install cm11

shadytarek_97 said:
http://forum.xda-developers.com/showthread.php?t=2582060 use this to install cm11
Click to expand...
Click to collapse
This is true!
This description must be used and all will work if you follow this sequence to!

Related

HELP! - Stuck booting to Recovery after trying to flash CM10 :(

Hi,
I flashed my GT-i9000 (Firmware was Gingerbread BUJVY) using CF Root (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar) through ODIN.
All worked fine and I was able to boot into Recovery using the regular Volume Up+Home+Power.
I then proceeded to flash CM10 nightly (23/9/12) (from my external Micro SD card) by wiping data, wiping cache and wiping Dalvik Cache.
I then navigated to the zip file for CM10 and run it. It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4).
From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
I'm hoping someone may be able to help, I would really appreciate it!
TIA!
zim_zimmer said:
It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4). From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
Click to expand...
Click to collapse
Do you know what version is your Firmware? is it 2.3.3 or 2.3.6?, IF its 2.3.3 your boot loader needs to be updated to 2.3.6 for you use , If its already 2.3.6, than you should be able to use CWM recovery to reinstall the CM 10 from your SD card. (But by doing this you may lose your IMEI as you should do a progressive upgrade , like from GB 2.3.6>ICS CM9>JB) or flash a semaphore JB kernel
Easiest way out would be for you to use a JVU ROM to recover, safe your EFS, than proceed to CM 9 and than to CM 10...
you can get a rescue kit or JVU+CFRoot from My Android Collections and or a solution from My Android Solutions
Hi there,
I was on Gingerbread 2.3.6 before I ran the above.
I have gotten a bit further than the above. I managed to mount the phone as a USB whilst in CWM and put the CM10 zip file on the actual phone memory. I then wiped data/cache/dalvik and rerun the install. It installed but didn’t reboot itself, so I rebooted manually and then the Cyanogenmod logo started up and it booted into CM10. Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Rooting this phone and flashing ROMS is more difficult than my Galaxy S3!!
Cheers
zim_zimmer said:
Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Click to expand...
Click to collapse
Since you are already on CM 10, you need to solve your home button problem, try doing a wipe in recovery, if fails, flash again the CM 10
Hmmm, it didn’t work.
What I’ve done since though is try to flash another ROM.
I’ve flashed the ‘xBean’ ROM with success, however, I did encounter the exact same problem when flashing the ROM as mentioned above
I wiped data/cache/dalvik and run the install for xBean. It stopped after the first install attempt and rebooted itself, however it just brought me back to the CWM screen (although this time different from the CM CWM).
So I wiped data/cache/dalvik, then run the install again. This time it went through the full install but again (like with CM) it didn’t rebooted automatically. I manually rebooted and then the xBean logo came up and booted in.
This time the home button is working, and pretty much everything else is too by the looks of it. So far so good!
I guess my question would be, why does the ‘ghost installs’ keep happening???

Motorola Milestone A853 Major Issue!!!!

Hi all, my name is Daniel.
I am using a motorola Milestone A853 for the past one year and never faced any issue while rooting or installing custom roms right upto cm10.
from last two months the milestone has not been working properly. It so happened i had installed CM 9.0.1d and everything worked fine. but once the battery died the phone did not boot up and was stuck on moto boot logo and kept restarting from there. I tried to go into open recovery (fufu minimod) using the X+power key and it goes into recovery but after loading recovery it did not display any options and the other text was red in color and it showed the error failed to load menu.init. I replaced the update.zip file along with the open recovery folder, but still nothing worked. I then tried another open recovery but still open recovery never loaded. Then i SBF'ed the device and went back to stock and was able to use my phone again. But then when i try to root the device again i am not able to root using vulnerable SBF as it does not install though RSDLite shows pass. Then i used superoneclick to root and that did the trick. But still open recovery never installed or load. Luckily androidiani recovery which displayed an error cannot mount but still created the menu and i was able to install custom OS but only cm 7.2.4e and not cm9 nor cm10. I cannot reboot the phone as the phone never starts up. only after clearing dalvik and wiping cache phone boots up. After a certain time now i still cannot install cm7.2.4e as it does not load and gets stuck on custom bootscreen, so i installed MIUI rom which works and starts up but i still can never reboot my phone.
Errors Seen E: cant mount /cache/recovery/command
Kindly help as the phone is just barely working.
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Tried Everything
Erovia said:
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Click to expand...
Click to collapse
Thank you for your reply. I have tried flashing stock 2.2 and still I cannot reboot the phone without wiping cache and using the reset factory option in stock recovery. Using superoneclick I can root it and install androidiani recovery but I cannot use cm10 or cm 9. after installing cm9 the phone just restarts after cm9 boot screen and after installing cm10 the phone shows the stock android boot screen. cm 7.2.4e installs as well as miui but if battery dies or if I have to restart the phone if it gets sluggish and slow then I cannot...everytime for the phone to boot I have to wipe dalvik and cache for custom roms and for stock roms I have to wipe cache and factory reset.
SO basically I am stuck...have tried changing the sd card, repartitioning the sd card, but nothing worked
Open recovery cannot be used only andoidiani works after popping up some errors.
Kindly help.

[Q] Help my phone won't boot anymore

So this morning I decided to get myself a new ROM on my optimus 2x. After 2years with CyanogenMod7, I was starting to get more and more problems, so I went for it... my 2nd lifetime rom installation.
I thought I understood it all good.. decided to go with ParanoidAndroid CM10 (http://forum.xda-developers.com/showthread.php?t=2097807). I followed pengus's instructions thoughtfully.
1. Copied the ROM .zip, the gapps .zip, and the kernel .zip.,
2. Factory reset, clear cache, dalvik, etc..
3. Booted the phone in recovery, and installed the 3 .zip package in the order I just mentioned (at step1)
After rebooting my phone would keep booting with a new and fresh version of Cyanogenmod 7.. for some reason. I remade the operation a couple times and it would always get my in cyanogenmod (wtf?). Now, after a couple hours of messing around, I installed back nvflash and tried other loaders : cwm 5.0, cwm 6.0, twrp 2.5.0..
Eventually after the usual clear cache / factory reset, unpacking zip files, my phone stoped rebooting in cyanogenmod7, but then it would just get stuck with the "LG" logo forever....
Now, I've taken my ENTIRE day off trying to figure this one now. I've been at it since 8hours more or less, and now I'm expecting calls and I'm out of phone. The whole experience has been very frustrating.... and I'm out of solutions here..
Hopefully this is just a newbie mistake (cuz I'm still kinda newbie in the whole rooting experience). Plz help...
something I don't understand :
when using twrp 2.5.0 as recovery, after I did a full wipe, and fresh installation, just after I click reboot now. it says that it appears my phone is not rooted, and that I can click yes to install SuperSU.. sometimes I click YES, sometimes I don't ... both action don't change the fact that my phone gets stuck at the LG logo.
So turns out I had a gingerbread partition and was trying to install an IceCreamSandwitch version of android.
With All-In-One-Toolkit, I was able to fix the partition and all.... wow all my day because of this ;(

[Q] Problems with custom rom HTC one

I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
iElvis said:
There is no need to flash the boot.img in fastboot. Just flash the rom from twrp.
Click to expand...
Click to collapse
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Switchback802 said:
right, i only did it to ensure that wasnt the problem....however my new problem...I Have a ROM finally installed...but my phone is rebooting a minute after it starts. I am able to use the screen and everything but it just shuts down and starts back up on its own...
Click to expand...
Click to collapse
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
iElvis said:
Download the rom again (might be a bad download), transfer to your sdcard, do a full wipe, and flash again. Something you flashed has created a conflict.
Edit: That's a Sprint ROM. Do you have a Sprint phone? If you've been flashing GSM roms, that's your problem there.
Click to expand...
Click to collapse
I do have a sprint phone. Trying to reflash the rom now.
Edit #2:
Installed Cyanogen Mod, looks great boots up but stil reboots my phone. Not only that but I have no service either.
Switchback802 said:
I do have a sprint phone. Trying to reflash the rom now.
Click to expand...
Click to collapse
Hi,
Maybe you'll have a better help here: Sprint HTC One ?
Switchback802 said:
I know there are a million posts about this, but I have been through them all trying to follow the guidance because the problems seemed to be the same as others have faced, but I feel differently now....
I unlocked my HTC one, following the htc dev site.
I installed TWRP (I cannot for the life of me get CWM to load into reovery, it only reboots the phone...)
loaded the roms/Super SU onto the SD card.
I know my phone is rooted (or i should assume?) because SuperSU is requiring me to grant access to apps and such.
I flash the custom ROM to the phone, install the package following Revolutions steps. Complete installation, return to fastboot menu. Flash boot.img, clear cache and reboot phone....Phone goes to the HTC Quietly Brilliant screen, with the development message at the bottom and continues to reboot over and over and over from there.
What did I do wrong?
I know pretty much have a phone that wont work because even after restoring it, it is ina boot loop after it fully boots up and nothing is loading correctly. Is there any way to start this from scratch?
Notes:
I tried doing an ADB sideload of Revolution HD.
I do a factory wipe before i load any rom....
Edit:
I have tried multiple ROMS...all the same effect....
I also get the message after installing the ROM from TWRP that "your device is not rooted, swipe to install superSU" so sometimes i swipe it, sometimes i dont...either way same result.
Update #2:
I flashed a ROM called 42ONE....it ended up successfully booting past the HTC screen and is currently updating the android system...However, it will operate for about 2 minutes then the phone reboots like it was before when i tried to restore....what the heck?!?
Click to expand...
Click to collapse
Revolution HD is not compatible with Sprint devices.
bigdaddy619 said:
Revolution HD is not compatible with Sprint devices.
Click to expand...
Click to collapse
problem resolved so far. REflashed stock rom, relocked device. its working for now.

GApps issues with CM 13

*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
BEDickey said:
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
Click to expand...
Click to collapse
I haven't flashed this rom for my turbo yet and this may not be the issue but in the past, dealing with other phones on CM, when you would 1st flash the rom, (& before rebooting the 1st time) you would then need to flash the gapps immediately after for everything to work properly. Try flashing the rom and gapps before rebooting.
I didn't see if the CM op instructions recommended this, just personal experiences from previous rom flashing.
I have had this happen twice after installing any CM13 on top of the March 31 nightly. I have not found a way around it yet besides doing a factory wipe after installing CM13, Open GApps and the latest radio code in this thread.

Categories

Resources