I have updated my rom to CM12 a while ago and after that my recovery (TWRP) stopped working. Yesterday, I finaly decided to fix it, so I flashed CWM (it worked!) and I tried to update my rom to the latest CM 12 nightly build. When it booted into the OS, I get a bunch of error for Text-to-speed, Google play service, UI System, etc. I tried to wipe, reflash, reinstall gapps... same thing. Then, I tried to only install the os : Wipe, install the rom, boot still get the errors.
Anyone, has any idea on how to fix this?
I have a SGH-M919 (Samsung galaxy S4 - T-Mobile), I downloaded the JFLTETMO version of CM12.
You should start over.
Factory reset, reflash a stable version of cm12 and stay away from the nightlies.
Nightlies are experimental changes that are put out so you can try them on your phone. They don't always go well and your left with a phone that doesn't work.
If you need your phone to function properly you may consider stable CM11 or a stock rom.
Pp.
PanchoPlanet said:
You should start over.
Factory reset, reflash a stable version of cm12 and stay away from the nightlies.
Nightlies are experimental changes that are put out so you can try them on your phone. They don't always go well and your left with a phone that doesn't work.
If you need your phone to function properly you may consider stable CM11 or a stock rom.
Pp.
Click to expand...
Click to collapse
Thanks for the reply, I downloaded a Stable build of CM11 and flashed it, but my phone kept rebooting in Recovery. I noticed that the sdcard/ folder is empty like if nothing was installed in the phone. I decided to flash TWRP. And when i flash the rom I get an error:
"E: Unable to open zip file."
"Error flashing /sdcard/rom3.zip"
Edit : Forget about the error I think the file was corrupted during transfer. Still getting the boot into recovery thing.
Try removing your SDCARD from the phone.
Turn phone off, remove SD card and start over. This may allow you to flash without errors.
Afterwards if successful tryout phone and then reinsert SD card.
Pp.
Related
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
eduardo_b said:
I have one S3 that's stock and another that's rooted, so I decided to try CM9 first on rooted S3 because CM10 didn't seem quite ready for daily use. Flashed ROM and Gapps, and things were fine until wi-fi ceased functioning. Worked, then didn't ever again. Nothing I found in searching this helped. And I couldn't get to PlayStore because there was no connection. Tried many things to reset wi-fi, but despite excellent signal, the phone wasn't connected to Internet. I reflashed CM9 (same most current release) but it didn't help.
So, having not actually done anything other than adding ROM Manager, I decided to flash latest CM10 nightly with CWM recovery via ROM Manager. Everything was fine, except of course I forgot I needed to install newer Gapps. However, when I went to do so, ROM Manager was no longer there and manually trying to get recovery only resulted in download mode, which meant I couldn't install Gapps or do much of anything.
I spent time trying to figure out how to get recovery, but having run out of options, I thought it perhaps best to flash back to stock using desktop Odin. I have the MD5 for 4.1.1 LK3. So I did this, but now once past the Samsung and AT&T animations, the phone stops with a Samsung logo. And that's where I'm at.
I know I've seen threads on fixing this, but I can't find them and I would like rectify the softbrick circumstance. What to do.
Click to expand...
Click to collapse
Did you remember to factory reset (wipe /data) when flashing the stock ROM? That's the most common cause of soft-bricking in this scenario.
If not, boot into recovery (Vol Up + Home + Power) and do so, then try booting the phone again.
Do I do factory reset from desktop Odin in download mode?
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
smelenchuk said:
That's one possibility, but if you don't want to go through the Odin process again, you can just do the reset from recovery as I outlined above.
Click to expand...
Click to collapse
Ah...volume UP. But wipe data/factory reset didn't help. If I select update from external storage, would that be MD5 or...?
Okay, I wiped cache partition and I'm in business. No more softbrick. Thanks!
Hey -
First of all, thanks in advance for any help. I never thought I'd be one of the folks posting a "help, I killed my phone" thread, but I don't have a choice!
I was running AOKP JB Milestone 1 and CWM, and decided to flash TWRP 2.3.something and the new AOKP JB MR-1 build. I did a backup in TWRP, ran Ti Backup, and installed the new build and gapps that I dl'ed from GooManager. I wiped dalvik and cache. When I booted, every app crashed and the phone was unusuable, so I went back to TWRP recovery and did a factory reset (after googling to confirm that it would not delete my GNex's sdcard, so I should still have my backup images).
Now, I get past the AOKP boot animation, but the Setup Wizard appears, then stops. Clicking "ok" leads only to another "Unfortunately Setup Wizard Has Stopped" box. Infinite loop. Bad news.
What is scaring me is that I can't find any recovery images to flash in TWRP, and don't see them even in the /0 folder on the SD card. Now I'm thinking I somehow erased my backups, and have a version mismatch. I thought I had TWRP 2.3.3.0, but the recovery says 2.3.1, so I'm wondering if I have an ICS/JB issue.
Anyway, I'm clearly stumped. Do I need to start from scratch and load CWM and a stock image via my PC? I don't think I can load anything any other way, but can't try that until later today.
Thanks again for any advice...
Ok, not sure what is going on, but after multiple reboots I could at least access my roms via TWRP and was able to reflash and get past where I was stuck. I'm hoping a new flash of the current gapps package will at least clear this up enough to see if my data is gone...
What gapps version were you using?
Sent from my i9250
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?
Ok I've been reading and reading these threads and have found a lot of great info. Right now my phone is useless so I guess I'm asking for a little more specific info for my current situtation. I used mskip's toolkit to root my phone then followed wwjoshdew's video on how to use goomanager to flash CyanogenMod 10.1.2. Everything seemed to be going fine when I got the spinning blue circle screen then came the "Unfortunately, setup wizard has stopped" and "Unfortunately, the process com.google.process.gapps has stopped". Over and over and over. I can get to download mode and recovery mode but not sure what my next coarse of action should be. This is on an AT&T galaxy s3 originally running 4.1.1. Thanks in advance to any and all help....
I wouldn't use goo manager to flash anything!! U should have flashed straight from recovery, be it cwm or twrp. Did u perform a nandroid backup before u flashed cyan? If so, I would wipe, factory data reset, and install your backup.
Have you tried reflashing Google Apps?
Reboot to recovery, clear cache/dalvik, reflash GApps, clear cache/dalvik again to be sure all is tidy.
Also be sure you have the correct version of GApps; that has messed me up at least once.
Other than that you can always retry the whole process i.e. CM and Apps
Thanks for the replies. I'll try and figure that stuff out. Only reason I've gotten this far was because I was following the toolkit prompts and did the steps in the video as he did them. This is the first time I've tried anything except updating to JB so...
Well, I can't say I've made any progress. I googled correct gapps for cm 10.1.2 and downloaded it but it's like a big collection of stuff that odin won't put in the PDA file spot. I'm not even sure if its the right one. I'm so lost right now. I see all these cwm and twrp recovery files in the toolkit files but not sure if they would help me or not. I know this is fixable since I can still get into recovery and download mode. At this point I would even just go back to stock at least that way I could get rooted again through the toolkit. I'm guess I'm such a noob that I need step by step. I feel like my right arm is missing not having a phone...
Ok I have 2 different versions of gapps that claim to be the right one. I would love to try flashing them to try them out but odin doesn't see them. What am I doing wrong?
Which recovery do u have installed on your phone?
For one dont use odin to flash any custom roms, first download the latest cyanogen mod and gapps, if you need the latest gapps you can get them here. Next you are going to want to boot to recovery and do a factory reset/full wipe then wipe cache/dalvik cache, next go to the top and select load zip from sd card, install cyanogen mod and gapps and reboot the phone.
Ok something different happened this time when I went into recovery. TWRP v2.3.3.1 showed up. I wiped the cache/Dalvik and did the factory reset from there. I have cm-10.1.2-d2att and gapps-jb-20130301-signed ready to copy somewhere. I opened the internal card and saw 8 or so icons that said local disk. so I created a new folder and put the cm and gapps files in there. Does that sound right?
Well that seems to have worked. Rebooted and went through all the google stuff. I'll test everything and see how it works
Glad u got it working!! I usually download Roms straight from my phone, over WiFi of course, and place on the root of the SD card, not in a folder, and flash from there...
Hey Guys,
I just got a new Samsung Galaxy S3 SGH-I747 in the mail and I immediately started to install Cyanogenmod. I have installed it on two S3's in the past, but this time I had no idea about the new bootloader problems after Android 4.3 (I think?). I got CWM touch installed with no problems via Odin, but when I tried to use the Unified Android Toolkit thing to root and stuff I got stuck in a boot loop. The phone would not boot past the Samsung logo, not the animated one with the purple light, but the one that shows the phone model.
I have tried everything I could think of and all that I tried to google for the past couple hours to no avail. I stupidly did not make a backup of my stock ROM, and I couldn't find a stock 4.4.2 ROM except this one that says it is stock but with root. I flashed that ROM and then it booted past the Samsung logo and the animated one, but is now stuck on the AT&T logo. I looked up that problem and couldn't find any real information on that problem except one thread where it said I should install Kies and let it do the Firmware Upgrade and Initialisation option. That failed and then my phone would only turn on straight to download mode.
I reflashed CWM and that worked so I thought that if I tried to install Cyanogenmod 11 it might work because that ROM is 4.4.1 or higher (Again, I think?). Now it's back into the loop where it makes it past the samsung stuff but then gets stuck on the AT&T logo. Is there anything I can do?
Thanks,
Jemimacakes
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
audit13 said:
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
Click to expand...
Click to collapse
Yes, I have tried clearing stuff in both CWM and stock recovery. Im not sure about the Dalvik one though, unless that is cleared when you do factory reset and clear cache I didnt do it. I can try flashing CM10.2 ( which I would prefer to have over 11), but my understanding is that my boot loader will not let me install anything that uses any lower versions of android, but I'll give it a shot and let you know.
Ok guys,
I tried to install Cyanogenmod 10.2 and when I put it on my sd card and tried to install it with CWM It threw and ton of errors that look like this.
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG3" || etc etc.
Im not super experienced with programming, but im guessing that CM10.2 can find any bootloader it can use? Im not sure what my bootloader is if that is the case, but I can boot into recovery so I must have something, right?
Anything I can do?
Thanks
Jemimacakes
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Hey,
I did have the latest version of CWM, but I tried it on TWRP and got the same errors
audit13 said:
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Click to expand...
Click to collapse
Hey,
I have now tried both custom recoveries and gotten the same errors on both, and I made sure I had the latest version of each. Can I flash the firmware from 4.3 and then install CM10.2? Will that work? I really don't want to hard brick my phone.
EDIT: I installed ADB to find out what my bootloader was, and it returned that I had the NE4 version. Is there a way to get the MJB version safely so I can install 10.2?
At this point I just want it to boot up to anything, so if that is easier to do than get CM to work then im completely open.
You cannot go back to MJB from NE4.
How did you try to install CM the first time? Did you use the install manager or a custom recovery?
The last time I installed CM on a i747 was back when the phone was on 4.1.1. The second phone I installed it on was the international version of the phone, also on 4.1.1. I used a custom recovery both times. I bet if I would have used the new installer on this phone it would have worked, but I was trying some other stuff because I was curious and ended up breaking it.
IT BOOTED!
I reflashed the stock firmware + root, reinstalled stock recovery and wiped everything I got it to boot into its stock ROM. From this point, where do I go? Will the CM installer work or will it just brick it again?
Thanks
Jemimacakes
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
audit13 said:
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
Click to expand...
Click to collapse
Which version of CM11 should I get. On the site I see that the last version of CM11 for the I747 (d2att) was released on feburary 16, is this one based on 4.4.2?
EDIT: Also, I should copy CM11 to both the internal and external storage? Why is this?
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
audit13 said:
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
Click to expand...
Click to collapse
Alright, but I have the at&t version of the phone. Are they both compatible with one another?
EDIT: OK, correct me if im wrong, but my new understanding is that CM now has releases for general versions of phones, so the most recent update of CM for my phone is the d2lte, not d2att?
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
audit13 said:
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
Click to expand...
Click to collapse
Hello again,
Thanks a ton Audit, my phone is up and running with the latest cyanogen nightly! A recap for anyone who might come across with a similar problem.
1. I installed a ROM using an older version of android onto a phone with the new bootloader (NE4), softbricking it.
2. I installed the stock ROM + root from this link using Clockworkmod
https://www.androidfilehost.com/?fid=23501681358550126
3. Installed the stock Recovery from this link and did wiped my data and both caches
https://www.androidfilehost.com/?fid=23681161096070493
4. I rebooted the phone and waited at the AT&T logo for a while, and it booted up normally!
5. I installed the most recent version of Philz Touch Recovery for the d2lte, made a nandroid for safety, and then install the latest nightly of CM11 for the d2lte.
6. It works!
Thanks again to Audit for helping me out!
Jemimacakes
I'm glad it all worked and I was able to help in some way.
It's great that you posted your solution in case it helps other people in a similar situation.
I think i'm in a similar place - a few questions. You used cwm to install the stock ROM? I thought you needed to use odin. Also, why did you need to install the stock recovery (and did you just flash the .zip in cwm)? Also, that stock rom you linked to is 4.4, right? Would that work if I was on 4.3?
Before flashing anything, I suggest you confirm your bootloader and modem. Flashing the wrong combination of modem and bootloader could hard brick your phone.
If your phone does not boot, try flashing Philz Touch for the d2lte and flash the latest cm11. Hoepfully, this will get your phone running so you can confirm the bootloader and modem. CM11 does not flash a modem or bootloader.