Related
I'm very confused as to what happened, and feel like I'm only making things worse so decided to come here. I've been rooted for about 2 months now after using Unrevoked Forever, and until last week everything was fine.
Using Rom Manager I attempted to flash Salvage Mod coming from Cyanogen 6.1.2. After wiping Data/Cache, when going to open the Zip Clockwork told me that the Rom did not exist in my SD card?
I redownloaded and tried again several times with no luck. I tried downloading other ROMS through my computer and putting them directly on my card and now I'm getting an error saying the Zip files are "(bad)"
Flashed RA Recovery through Rom Manager, the same errors, and now flashing back to Clockwork won't work. Any ideas what the problem maybe? Any solutions would be greatly appreciated
Have you tried booting to recovery directly and flashing a rom? I personally use CWM 2.6 and prefer to do all the work myself through recovery instead of hoping RomManager gets it right.
Yes I've tried booting into Recovery myself, keep getting the error that the zip. is bad
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?
Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem
meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?
moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418
Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.
moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.
moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
riazrahman said:
Hi guys, I'm freaking out!
I'm proposing to my girlfriend this weekend and the PacMan ROM I was using (4.4.2 I believe) was lagging/running out of storage, so I decided to flash to the newest 4.4.4 ROM I could find. I wanted to make sure my phone was in tip top shape for the big weekend. I booted into TWRP and took the normal steps to flash (wipe ROM,dalvik,cache) but this time I also decided to delete internal storage because I was running out previously and just kind of wanted a fresh start. I decided to try the MerkMod ROM (4.4.4) w/PA 4.4.4 micro GApps, and everything worked great (fast, no reboots) after flashing....until I tried the camera maybe a day later. I got the 'Can't connect to Camera' error, and freaked out immediately because I need to snap some selfies of the big moment this weekend! I then tried deleting the camera thru Titanium Backup and flashing PA's Google Camera module, which didn't work either.
So then I went through all of the steps to go to ND8 stock from MerkMod as outlined by CNexus in this thread. I also switched to Philz recovery. Unfortunately, the camera would also freeze up/not start on the stock ND8 ROM as well (no explicit 'cant connect to camera error' but the screen was all black and the phone froze up). TW + samsung bloat was literally about to make me throw up, so then I decided to try SlimKat 4.4.4 w/Slim GApps, and I'm still getting the camera error. I deleted the Camera2.apk in SlimSettings and downloaded Google Camera, and that didn't work either.
I have no idea what happened! I don't think there was any physical/water damage to the phone, so I don't think it's a hardware issue. Should I try to go back to an older version of the stock ROM? Did this happen because I deleted my internal storage, or used PA Gapps (I've read that both might have contributed)? If so, how do I fix this!? PLEASE HELP!
Click to expand...
Click to collapse
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Higgs_Boson said:
Right now, I think the best first step for you would be to try flashing the ROM and GAPPs package with a different recovery.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Navigate to the above link and download the latest zip (not md5) file to flash in your current recovery. Your current recovery will simply flash the zip file and overwrite your current recovery with PhilZ.
I personally can't see a GAPPs package causing that sort of issue, as it is not replacing code, changing libraries, or messing with the kernel. The GAPPs package is simply flashing system apps to the /system folder of the Android OS. Additionally, I use the PA GAPPs package when I flash CM11 nightlies.
A recovery can make all the difference of making sure that the correct files are being flashed to the correct areas and I, personally, find PhilZ to be the most bug-free and user-friendly.
When you boot into PhilZ, make sure you have all the files that you intend to flash on your device.
In PhilZ, the Wipe Data/Factory Reset option actually has an option to wipe the device to install a new ROM. Use that option
Install your ROM of choice and your GAPPs package. Reboot and see what happens.
Also, just had a passing thought: Did you flash a custom kernel? Did you not make a backup of your last working setup?
Click to expand...
Click to collapse
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
riazrahman said:
Thanks for your prompt and detailed reply! I did switch to Philz recovery after Odining to ND8, but I'll try again using the link you provided. Unfortunately I never made a backup, my mistake. I never explicitly tried a custom kernel, could my initial flash to MerkMod have changed the kernel?
Click to expand...
Click to collapse
Sorry. After re-reading your post, I do see where you mentioned switching to PhilZ. However, please make sure that you have the latest version of PhilZ (which can be found at the link I previously provided).
After reading up on MerkMod, I have no reason to believe that ROM to be the cause of your issues. It is OMNI ROM-based and I have run OMNI ROM on my device without any issues. I, personally, use CM11 as my daily driver. But, as long as you are using the latest PhilZ recovery and flashing D2LTE ROMs to your device, there should be no issue. Also, make sure the GAPPs package you are using matches the Android version of the ROM you are flashing (e.g. 4.4.4 GAPPs --> 4.4.4 ROM)
If you download the .MD5 version of PhilZ, you can flash that via ODIN. Good luck to you.
Also, forgot to mention it in my previous post, but congratulations in advance on your engagement!
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
CNexus said:
I don't think there's much to help here with. You said you odined to stock ND8 and still had the error. At that point, it definitely sounds hardware related and I would say that something is wrong with the device itself.
Click to expand...
Click to collapse
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
riazrahman said:
Ah that's what I was afraid of :crying: I reflashed Philz and installed CM11 nightly with PA micro gapps 4.4.4 and am still getting the same issue. I did read a thread that mentioned something that Gummy ROM was the only one to work for someone in a similar situation, so I may try that. Then I think I'll try Odin to ND8 one more time just in case, and then just give up. I guess I can try to borrow a digital camera from a friend. I do still have a TEP plan with sprint so maybe they can replace the camera module at my local store without me having to pay the ridiculous $100 deductible.
One last thing, if this was kernel related, what's a good kernel for me to try?
Thank you both for your time and insight.
Click to expand...
Click to collapse
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Higgs_Boson said:
Not likely that it's kernel related if the standard kernel with CM11 didn't work. You can always try the DKP kernel, which I use, found here in the Sprint S3 development forum.
Click to expand...
Click to collapse
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
riazrahman said:
Ah understood, well I just tried GummyROM and Odined to ND8 again and still no dice, so I gave up on blaming the kernel. I just don't get it...if it's a hardware issue would both of my cameras go out? Shouldn't I still be able to access the front camera if theres a short or something in my rear camera? I feel like my phone just doesn't know theres cameras attached to it because I deleted something I shouldn't have while flashing the first time around.
One last question before I try the Sprint store tomorrow...while I was using Odin I saw the re-partition option. Now I know I shouldn't touch that unless I have a .pit file, so I left it unchecked this time. However, if I did track down a pit file, could repartitioning potentially solve this issue?
Click to expand...
Click to collapse
The only thing that repartitioning will do is restore the memory partitions in your phone in the event that one of the partitions became corrupted.
This is essentially what a PIT would be restoring:
Code:
sprint # cat parted.txt
cat parted.txt
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 30777344s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 8192s 131071s 122880s modem
2 131072s 131327s 256s sbl1
3 131328s 131839s 512s sbl2
4 131840s 132863s 1024s sbl3
5 132864s 136959s 4096s aboot
6 136960s 137983s 1024s rpm
7 137984s 158463s 20480s boot
8 158464s 159487s 1024s tz
9 159488s 160511s 1024s pad
10 160512s 180991s 20480s param
11 180992s 208895s 27904s ext4 efs
12 208896s 215039s 6144s modemst1
13 215040s 221183s 6144s modemst2
14 221184s 3293183s 3072000s ext4 system
15 3293184s 28958719s 25665536s ext4 userdata
16 28958720s 28975103s 16384s ext4 persist
17 28975104s 30695423s 1720320s ext4 cache
18 30695424s 30715903s 20480s recovery
19 30715904s 30736383s 20480s fota
20 30736384s 30748671s 12288s backup
21 30748672s 30754815s 6144s fsg
22 30754816s 30754831s 16s ssd
23 30754832s 30765071s 10240s grow
Info credit: http://androidforums.com/virgin-mob...ameleon-some-efs-imei-info-brick-backups.html
Hence, I have no reason to believe this would help you.
I tried flashing a nightly of CM12 on my M919 after no problems for almost 2 weeks. After flashing, my phone was stuck in boot with the CM logo. I tried flashing previous versions of the rom wiping and clearing each time. All I got was the CM logo. I finally decided to start from scratch and reinstalled stock(4.4.4) with ODIN 3.07. Phone booted right up. Rooted the phone with CF-Auto-Root (KTU84P.M919UVUFNH7) with no problems. Ran it for the day to make sure no issues. After feeling comfortable, I downloaded and tried flashing CM11 Snapshot M12 since it's based off 4.4.4. Boot loop again. I tried CM12 with the same results. I'm using CWMR 6.0.4.7. I've tried newer versions of both CWMR and TWRP(I don't remember what versions they were). I'd like to go back to using 5.0, if possible. I'm not sure if I've missed a step in rooting, since it's been so long that I rooted/flashed this phone. Right now it's running stock 4.4.4/M919UVUFNK2 and rooted. Any suggestions as to what I could try?
That nightly may have borked some files causing a problem, the nightlies are usually full of warnings about possibly causing boot loops or lockups and always recommend a nandroid b/u before flashing.
A nightly is a way of trying something out on other people's phones to see if it works well enough to add it as an update to the regular rom build.
If your that desperate for a nightly you need to follow the thread for a couple of days and see how others do with it.
If all you see is "I flashed the nightly and boot loops all over the place, don't bother, otherwise you find yourself in this thread.
Try a factory reset and flashing again,
also get a newer CWM recovery 6051 (if not mistaken) but stay away from the nightlies.
If you really need a reliable phone that works all the time and doesn't windup dead, just keep your stock rooted rom. And lollipop will be here soon as an update, probably by mid-march, the you'll have all the lollipops you want.
Pp.
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.