Hey guys.
I've been using CM10 M2 for a while now and I decided I should reflash it.
So I made a wipe ( cleared all cache and everything ), installed cm10 m2 and Tantrum's Aroma Gapps installer to install my gapps and other stuff, and rebooted.
Problem is, once I reboot my phone will not boot and it is stuck on a black screen with LED's flashing.
Tried a few times and it the problem persists.
Any word of advice for me?
-Anton
EDIT: Tried flashing latest nightly with tantrums gapps, same problem.
EDIT V2: Flashed same nightly WITHOUT Tantrums gapps ( regular gapps ), everything boots normally. Problem was with Tantrums gapps.
Antonnzr said:
Hey guys.
I've been using CM10 M2 for a while now and I decided I should reflash it.
So I made a wipe ( cleared all cache and everything ), installed cm10 m2 and Tantrum's Aroma Gapps installer to install my gapps and other stuff, and rebooted.
Problem is, once I reboot my phone will not boot and it is stuck on a black screen with LED's flashing.
Tried a few times and it the problem persists.
Any word of advice for me?
-Anton
EDIT: Tried flashing latest nightly with tantrums gapps, same problem.
EDIT V2: Flashed same nightly WITHOUT Tantrums gapps ( regular gapps ), everything boots normally. Problem was with Tantrums gapps.
Click to expand...
Click to collapse
I'm not any pro user, but I think that the CM10 is too heavy for LGOB. I use the CM7.2 and works like a charm.
DFornazari said:
I'm not any pro user, but I think that the CM10 is too heavy for LGOB. I use the CM7.2 and works like a charm.
Click to expand...
Click to collapse
I have used nightly builds of CM10 from October 15 onwards with a problen
only on the 19th release when I couldn't install anything due to an issue with
the version of Clockworkmod Recovery. Once I found out how to downgrade
that version, it's all fine (touch wood).
Sam
@Antonnzr
Rather just use normal GAPPS. There was a release by tantrums that caused bootloop, but he fixed it now.
Use ADB to go back to recovery.
@DFornazari
CM10 isn't heavy at all. rmcc committed a lot of changes from TI's branch and I think it caused some instability with the some of the newer releases. I based that speculation from a comparison between nightlies before the changes was made and after the changes was made. I didn't look at the code so I can't be 100% certain since I don't know what they changed. rmmc is a great dev and should have all the device specif bugs sorted soon.
Yes its all working fine now with cm10 m2 and regualr gapps but I have a new issue.
Whenever I try to download an app from the Play Market ( nova launcher, for example ) it pops up with an error reading:
"Error: 'Nova launcher' could not be downloaded due to an error (927)"
or alternatively:
"Error: 'Nova launcher' could not be downloaded due to an error ( error retrieving information from the server )"
Tried to install apps via online Play Store both on my phone and my laptop but the download never starts. Help?
Disregard that, fixed after reflash.
Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
AllUsernamesAlreadyInUse said:
Hey guys. I've been using CyanogenMod on my Galaxy S for quite a long time. Few days ago my battery died and phone wouldn't pass the CyanogenMOD logo. I've decided to go back to stock rom and then upgrade to one of the new roms.
So I flashed the stock rom using Odin 3.07, rooted, went to recovery mode and tried to flash: Mackay ROM, Beast ROM ( black and white as well as beastxl), Avatar ROM, Slim Bean, Tsunami, CyanogenMOD but none of the above worked.
It starts the installation and after few seconds phone restarts itself and gets stuck on new boot logo.
The only thing that gets installed is the CWM which won't let me do the factory reset, wipe data, wipe dalvik cache etc. Keeps saying can't mount /data, /cache, /system.
The only time I can do factory reset is when I install stock rom.
I only succeeded installing Franzy ROM once but after reboot gets stuck on boot logo.
Sometimes even the stock ROM is giving me issues like process com.android.phone has stopped unexpectedly (does it for dialer, calculator, market, launcher)
Another weird thing is that even when I go back to stock rom and open up for instance a picture with bright background or web browser I can see transparent battery and CyanogemMod in the middle of the screen even tho phone's not charging and running on stock rom not CyanogenMod.
I think I've tried everything from fixing permissions, flash and re-partition using Odin and 512 pit file.
Even rang my Mom like advised in xda's video, didn't help either
Is there anything else I can try to get my phone in "shape"?
Any suggestions?
Click to expand...
Click to collapse
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable from here : http://get.cm/?device=galaxysmtd&type=stable
then install any costum rom you want
The Tox said:
try to flash stock rom again via odin , root , then flash cm 9 ( to not loose you IMEI ) , then flash CM 10.1 stable
then install any costum rom you want
Click to expand...
Click to collapse
Thanks for your reply. Installing CM 9 worked but trying to install CM 10 throws up this error:
assert failed: run_program("tmp/updater.sh") == 0
E: Error in sdcard/cm-10.1.zip
(Status 7)
Installation aborted.
Flash this one :
http://get.cm/get/3Fb
then install this one :
http://get.cm/get/9aJ
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
AllUsernamesAlreadyInUse said:
Thanks for your help. CM 9.1.0 installs fine, same error for 10.1.2 :/
Click to expand...
Click to collapse
did you tried to install other costum roms , like slimbean ?
There MIGHT be a problem with your internal SD card. Slight chance :/
did you tried to install other costum roms , like slimbean ?
Click to expand...
Click to collapse
Yes I did and only Franzys installed successfully but then stopped working after phone reboot.
There MIGHT be a problem with your internal SD card. Slight chance :/
Click to expand...
Click to collapse
I think that might be the case. I get encryption unsuccessful with my sdcard in and CWM doesn't see any files with sdcard out.
I found an article here on forum that explains how to use your external sdcard as the internal one. Will give it a try and see if it works.
For now I don't mind using CM 9.1.
Thanks for your help guys and let me know if you have any other suggestions.
UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff
Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.
CM 10.2 Build removed due to errors.
jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.
@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4
I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.
Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.
Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.
motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.
When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2
Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.
I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.
It works with the xt902 too. Thanks!
What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!
I'm not sure if I'm the only one experiencing this but every time I try to flash a custom kernel on CM11 and PA4 with cwm 6...4.8 camera app freezes like usual but then freezes again after 5 secs which is not usual.
Not only does this happen on custom kernals but stock CM11 and PA as well e.g. when I was in the science museum using PA taking pics everything was working well, then phone froze so I did a reboot in fact 5 reboots and camera displayed same symptoms as explained above. Also on CM11 stock kernal I did a regular reboot to apply full theme and bam camera stopped working all AF a sudden.
To fix I had to reflash ROM. I even did a full wipe( including format system) and still had same symptoms.
Pimped kernal just breaks camera straight from reboot no matter how many times I reboot it doesn't fix the problem. Only fix seems to reflash ROM (no need to wipe). Restoring stock/original ROM kernel fixes it but WiFi does not work.
Any way to get custom kernels to work without breaking camera?
..just an advice, do not use CWM, is recommended to flash with TWRP because is more efficient. I had many problems with CWM.
eclyptos said:
..just an advice, do not use CWM, is recommended to flash with TWRP because is more efficient. I had many problems with CWM.
Click to expand...
Click to collapse
Thanks for the reply. I have no option but to use cwm cause all my back ups where done on cwm.
As for the problem I found the solution in this thread:
http://forum.xda-developers.com/showthread.php?t=2505973
yup owns Z1 and stuff.
Hey guys. I finally got my P880 working again.
I had it on Stock 4.1.2 which I really don't like. I want to upgrade it to KitKat 4.4 (Cyanogen 11)
However whenever I try and flash the 'cm-11-20141224-NIGHTLY-p880.zip' with 'TWRP 2.8.3.0' I get:
E:Error: executing updater binary in zip
Click to expand...
Click to collapse
This is apparently due to something to do with how permissions or something were changed in 4.4 and that TWRP (for our P880) doesn't apparently work for flashing KitKat.
I don't understand this as other people have complained that CWM doesn't work for flashing KitKat 4.4 but the latest TWRP does work.
Any ideas?
Currently I have the P880 now without ANY firmware installed :/ and I will no longer have access to a computer after tomorrow for about a month
I had the P880 working with Stock 4.1.2 like I said, but it's pretty bland vs. KitKat 4.4 which my S5 is rocking.
So...
Is there an easy way to get Cyanogen 11 KitKat 4.4 working on my P880? I've been trying to get this done for days after flashing PhilZ Recovery that bricked my phone (even though it was for my Model (P880)).
I just got TWRP 2.8.3.0 installed on my phone and it seems to be the ONLY recovery that actually works. CWM 6.0.4.5 doesn't work on my phone. It installs fine, but whenever I try and press something, or select an option like (Install .zip) nothing works. Absolutely nothing works. Because I have no firmware installed now, I'm also at a bit of a loss as to risk installing a different Recovery in case it also has this problem. As both PhilZ and CWM have not remotely worked and I have been unable to perform any action what-so-ever with either of them. Only TWRP seems to work.
Please help me get Cyanogen 11 on my phone
EDIT:
I flashed SlimKat 4.4 instead of Cyanogen 11. I've never really liked Cyanogen anyway and I loved SlimBean on my S4.
Downloaded and flashed the 24th December UNOFFICIAL build and it worked perfectly.
However I got a little issue with /storage and /data not mounting properly so I had to flash again by wiping /data (using the 'yes' wipe, not standard factory wipe). I think I had this problem because the phone was mounted to my laptop when I did the .zip install from TWRP.