Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!
Related
Hey guys,
Recently I flashed
ClockWorkMod recovery - v 6.0.1.9
Cyanogenmod 12.1 nightly -cm-12.1-20150706-NIGHTLY-mako.zip
It all worked out (with great difficulty) and the phone works fine.
However, I have no google apps. Coming from stock factory setting to a rom with no google apps is quite difficult.
So, i tried flashing the gapps along with the rom but i keep getting a status 7 error message and the installation gets aborted, the result being when i reboot my phone i get a plethora or error messages of all the google apps which stop working (i.e none of the gapps work).
I have tried flashing the following (file names) gapp zip files with no luck.
gapps-5.1-2015-06-02-15-21
gapps-5.1-2015-07-03-13-41
gapps-L-4-21-15
gapps-lp-20150211-signed
BaNkS-dynamic-gapps-L-6-21-15
pa_gapps-modular-mini-5.1-20150315-signed
Even the gapps link on the cyanogenmod wiki page does not work. ( i think i included that filename in the above list)
On reading other forums, members say that the recovery must be updated.
Quite honestly i am quite apprehensive to do anything to the recovery as i got stuck into a bootloop once and it took me a day to get out of it.
P.S i am a complete amatuer in this process, this is the first custom rom i flashed after staying on stock factory images for 2 years.
I really do need help, as no other rom works well except the cm 12.1 and itwould be absoutely brilliant if i have the google apps too!
Thanks in advance.
solution found
Hey there, I have the s4 (GT-i9505)
I had the same problem until today and I have found the solution to it,
I updated my cm12.1 nightly to 20150706,
Downloaded slim gapps 5.1.x mini latest (20150706), [I searched for it on Google]
Tried flashing the cm and then the gapps but it didn't work, and gave me all the errors of apps that have stopped which was very annoying.
So then I did a little research and figured out that I was using twrp v2.6.0.0 which was quite old , so I never gapps after the root. So then I updated it to the latest version by connecting my phone to the PC in download mode and downloaded the twrp v.2.8.0 (latest) and recovery booted my phone.
Factory reseted my phone, installed both the cm12.1 and gapps by selecting the zip files and then flashing them. Wiped the dalvik cache. Finally rebooted my phone.
And to my surprise it actually worked. Thank god that now I have the play store and all the other apps without any annoying popups.
I'm on my phone so I can't seem to be able to upload any links .
I'm sorry you gotta have to search on Google for the download links.
Have fun buddy. Hope it works on your nexus 4. Enjoy !!
Got it working!!
So, followed some forums ( including mehsan23) and updated my custom recovery. The most surprising thing is that you can do this by downloading zip files of the latest cmw recovery and flash them on to your existing recovery and the recovery automatically updates.
Then flashed the gapps on cm12.1 wiki page and it worked! So relieved! However the Google app crashes but its alright I can do without it.
Thanks guys!!
P.s thanks again mehsan23
Hi,
I very much hope you can help me with this issue.
I wanted to flashTemasek's CM 12.1 v. 14.9 on a N9005 running stock Lollipop (N905XXUGBOE9_N9005DBTGBOF1). After much reading, I believed it would be best to first downgrade to stock 4.4.2 (N9005XXUENB4_N9005DBTENB1_DBT). I then flashed TWRP 2.8.7.0 hlte 4.4. Could this be the reason? I later read that for Kitkat 4.4.2 without updates I should have rather used the 4.3 version of TWRP. I did a backup of the system including efs. After that I flashed Temasek's CM 12.1 v.14.9 doing a clean install by following the steps outlined in the thread:
Clean Installation
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM.
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Flashing went fine, but the phone did not recognize the SIM card. Initially believing that this might be an issue with the ROM, I downgraded to Temasek's CM 12.1 v. 14 only to find that I was having similar issues. I then tried to restore the backup I created earlier but basically only got a black screen and a ton of notifications that apps had stopped working. I then tried to flash back stock kitkat (N9005XXUENB7_N9005DBTENB2) hoping that this would work with my version of TWRP but have had no success. Before causing any further trouble, I was hoping that some kind soul would be capable of and willing to help me with this. How can I recover my efs from the backup created with TWRP? And how can I finally restore my phone and hopefully end up with the ROM I was trying to flash? Any help is very much appreciated!
Thank you!
django e said:
Hi,
I very much hope you can help me with this issue.
I wanted to flashTemasek's CM 12.1 v. 14.9 on a N9005 running stock Lollipop (N905XXUGBOE9_N9005DBTGBOF1). After much reading, I believed it would be best to first downgrade to stock 4.4.2 (N9005XXUENB4_N9005DBTENB1_DBT). I then flashed TWRP 2.8.7.0 hlte 4.4. Could this be the reason? I later read that for Kitkat 4.4.2 without updates I should have rather used the 4.3 version of TWRP. I did a backup of the system including efs. After that I flashed Temasek's CM 12.1 v.14.9 doing a clean install by following the steps outlined in the thread:
Clean Installation
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM.
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. WIPE DALVIK/CACHE (for good measure).
10. Reboot Device.
Flashing went fine, but the phone did not recognize the SIM card. Initially believing that this might be an issue with the ROM, I downgraded to Temasek's CM 12.1 v. 14 only to find that I was having similar issues. I then tried to restore the backup I created earlier but basically only got a black screen and a ton of notifications that apps had stopped working. I then tried to flash back stock kitkat (N9005XXUENB7_N9005DBTENB2) hoping that this would work with my version of TWRP but have had no success. Before causing any further trouble, I was hoping that some kind soul would be capable of and willing to help me with this. How can I recover my efs from the backup created with TWRP? And how can I finally restore my phone and hopefully end up with the ROM I was trying to flash? Any help is very much appreciated!
Thank you!
Click to expand...
Click to collapse
Who said you need 4.4 to update to cm12.1? You need 5.0 bootloader. That's what you had.
Maybe use another version of twrp. I use 2.8.5? And it's fine.
In twrp go to back up and restore. Restore by navigating to location of your back up.
kenny1991 said:
Who said you need 4.4 to update to cm12.1? You need 5.0 bootloader. That's what you had.
Maybe use another version of twrp. I use 2.8.5? And it's fine.
In twrp go to back up and restore. Restore by navigating to location of your back up.
Click to expand...
Click to collapse
Thanks! I managed to restore the imei flashing stock lollipop. I initially downgraded because it seemed to me that all instructions were based on kitkat and not much information was available on lollipop. Just wanted to make sure I followed the instructions to the letter. Stupid me...
I tried to restore efs the way you describe it, but it didn't work out for me. Thankfully, things are back to normal now and I will flash cm12.1 directly from stock lollipop now.
Thanks for taking the time to help!
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
1. Use TWRP, CWM is outdated.
2. "Nightly" realeases are testing firmwares. CM13 for GT-i9505 is in early releases too. They have lot of bugs still.
3. - Download the latest stable CM firmware: HERE and copy it to your SDCARD external + Gapps (ARM+ android 5.1 + nano).
- Go to DOWNLOAD MODE and flash TWRP. Boot in TWRP - Select Wipe - Advanced Wipe and wipe all (less usb-otg and external memory).
- Flash CM12.1 firmware and GApps then. Reboot and enjoy.
Use TWRP. Google for s4 twrp. On that page you will also have various install instructions. Afterwards you can flash pretty much any custom rom.
Well, tried exactly these steps, I only skipped gapps for now. I installed following version: cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx. However the phone still hangs while booting... I will let it for a while and see if it boots, but I think it's still stuck... The stock Samsung Kitkat flashes properly from Odin and can be booted... Really strange. Is there anything I can do to see what's going on? I only get the Cyanogenmod Bootscreen, but no adb access...
Well, I am getting some errors: unable to mount /efs... This seems to be the problem, no idea why this is happening... I will keep looking around for a fix... I still don't quite understand why a stock KitKat works...
mschmiedel said:
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
Click to expand...
Click to collapse
Try dowloading the rom from a thread here on the forum.
You didn't mention what phone model you got so I assume it is a GT-I9505. You can find the official thread in the I9505 original android development section. The maintainer is AntaresOne.
It is the GT-I9505, I now was able to install a stock Kitkat, and it now is allowing me to update via OTA, (first time I got a message that I had a "changed" phone and OTA was disabled). I will let it install this way and see what happens.
Last time I tried with TWRP I was getting the error "unable to mount /efs", but after flashing an ODIN ROM the phone works, I have LTE Data and can place and receive calls, IMEI is there, so I am now confused about what can be wrong.
When this OTA update works, I will try to reflash TWRP via Odin (and not mess around with heimdall anymore), and see if then I can install CM12...
I downloaded the version from the Cyanogenmod site, the latest stable CM12.1 release, so I guess it should be as good as downloading it from an xda thread...
I don't know. It's worth a try.
If you get errors about efs,be careful.The EFS partition contains the most important stuff like your IMEI.There are some backup/restore tools of EFS, you should check them out.Wipe everything,flash cm,then restore EFS backup.
Hi guys,
I have the standard note III 9005 and I had always installed CFWs on it.
I wanted to update to newer 6.0.1 Roms (had 6 roms before) but I seem to have a VERY annoying bug:
I tried to install Temaseks rom and resurrection rom but I had huge issues with it. I got bootloops although I got the newest 3.0.2.0 Team Win Recovery Project
I installed rom, GAPPS (correct version of course 6.0.1) , install rom again then delete cache and then it worked on both roms.
So a simple "install rom, GAPPS, then clean cache" didnt work. I tried to install multiple times until I got the installation! YAY! BUUUT!
Here is the fun part:
If I restarted the phone acidentally or on purpose I got stuck in a bootloop. After that the phone was unuseable again so the installation was useless.
Only solution is to completely wipe and reinstall and experiment with the order of installation until it works!
I did install STOCK rom because I was so freaked out and then went with ODIN the complete rooting guide for clean rooting, but still problem exists.
I tried two other roms but the problem was that while flashing the phone restarted automaticly and then TWRP said no installed rom? ???
Huge thanks for helping me!
New info:
I was able to make the rom work. I restarted and got stuck into bootloop!
I could boot normally after deleting dalvik cache!
But after rebooting I got into bootloop. Tried deleting cache again but this time it never booted properly.
How can I avoid by always deleting dalvik whenever I have to restart my phone (if battery dies or purpose)?
PPS: Stock Rom flash works flavlessly. I am waiting in stock rom until I find a proper solution :"(
Suggest you read the roms faqs and Q&A particularly with regard to TWRP .
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Nikodominiko said:
Hi friends! I really feel frustrated with this phone.
I began by using fastboot to flash TWRP (twrp-3.1.1-1-s2), used it to flash Lineageos 13.0, but IR BLASTER doesn't work, then I flashed 14.1 and IR blaster, Sim detection, flashlight and camera don't work correctly, I tried Resurrection remix and MIUI8 too but I gave up, neither of those Custom Roms works as I wanted them to.
So I went back to EUI and all was well until I wanted to update OTA, it gave me an error every time, tried to do it with update.zip but nothing, using stock recovery and nothing. I used TWRP and wipe everything again, now this thing won't start it just bootloops, I tried everything for two days and every time I use a stock ROM (5.8.020s) it gives me an error, or tells me it can't be read. When I factory reset and format everything it tells me I dont have an OS installed, so I'm completely lost I don't know what else to do and I can't return the phone because I'm overseas right now.
I really need to have it as when I got it the first time because at least it was functional but I just can't get it to work
I could really use some help right now :crying: thanks in advance guys!
Click to expand...
Click to collapse
So I managed to fix the problem. When you root this phone or in fact just flash a custom recovery like TWRP, it changes the model of the phone, If you unroot the phone you won't be able to receive OTAs anymore even if you are on stock ROM, you'll always get an error at the end of the update even if you do it manually, if you are dumb like me and didn't make a backup of your stock system, you won't find any help on the internet more than to install a custom ROM and learn to live with the errors and bugs. I did not want that so to be able to get the phone to its factory state, what I did was this:
1. Download: stock recovery image for Le s3 x522 (official, you can find it anywhere), LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip, twrp_s3.img (the chinese TWRP recovery) and S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
2. Save those zips to the root of the phone, obviously the .img files you are going to flash them through your PC
3. Put the phone in bootloader mode. command: fastboot flash recovery recovery.img (the official recovery)
4. fastboot boot twrp (the chinese one)
5. From this step what I did was pure luck
6. wipe cache and dalvik and install LeEco_X522_5.8.019S_OTA.zip
7. wipe cache and dalvik and install bootloader-20S-s2.zip
8. wipe cache and dalvik and install S2_X522-NA-OP-IFXNAOP5802102141S-5.8.021S.zip
9. Reboot
How and Why did this worked I don't know, I am a noob but please try if you find yourself in the same situation as I was, you don't lose anything with trying, if this doesn't work don't blame me, this worked for my phone.
Greetings friends!
Thanks for putting this guide together, I am in a similar situation in that I reverted to stock everything (1. Installed YDSS chinese twrp, 2. Installed S2_X522-NA-OP-IFXNAOP5802012141S-5.8.020S.zip. This flash was supposed to have installed the stock recovery and overriden the ydss twrp, but didn't, I had to manually flash that after. Everything came back smooth but my updates also failed at recovery.
I am wondering where you got the LeEco_X522_5.8.019S_OTA.zip, bootloader-20S-s2.zip & twrp_s3.img from?
Nice to hear you finally got it to work ! Aren't the X520 and the X522 the same phone ? Why official ROMs are not compatible ?