I tried installing the new cyanogenmod 12.1 nightly from their website and i am stuck in Patching system image unconditionally....
Please help me out thanks!!:crying:
What is the model # of your phone? Bootloader version?
SGH-i747M and for bootloader i dont know?
Did you install a custom recovery in order to install CM? What was the last stock ROM on your phone?
audit13 said:
Did you install a custom recovery in order to install CM? What was the last stock ROM on your phone?
Click to expand...
Click to collapse
I already had CM 12.0 unofficial and now i tried to install the 12.1 from CM website... i also have the error that says failed to mount /system
Are you installing CM with a custom recovery?
audit13 said:
Are you installing CM with a custom recovery?
Click to expand...
Click to collapse
Yes i am
In that case, you may need to do a full wipe. I had trouble going from 5.02 to 5.1.1 on my old HTC One XL.
audit13 said:
In that case, you may need to do a full wipe. I had trouble going from 5.02 to 5.1.1 on my old HTC One XL.
Click to expand...
Click to collapse
I just tried installing the UNOFFICIAL 12.1 and it worked, why is the 05/19 from Cyanogen causing issues?
I've read posts from other owners of phones with the msm8960 chip that also had issues. The latest nightly may have resolved some of these issues.
spiritblastt said:
I just tried installing the UNOFFICIAL 12.1 and it worked, why is the 05/19 from Cyanogen causing issues?
Click to expand...
Click to collapse
The last time MatrixZone updated the Unofficial Cyanongenmod 12.1 was on 05/01. The last update would have been based on nightlies from the day prior to that (or earlier). So, my guess is that there is something in the newer releases that does not agree with your device.
OTOH, in his thread you will find reports of those who have random reboots with MatrixZone's releases for over a month prior to his last release, others never had a reboot with any release; official or unofficial.
Related
Here is my dilemma, I recently unlocked and rooted my HTC One M7 for Verizon. I may not have performed a backup but I am oblivious to what the problem may be. I am a newb to rooting and unlocking so please spare me any negative feedback. S-off was successful using firewater. Phone is unlocked in bootloader. Phone was rooted through TWRP v2.7.0.0 and SU. After root was successful I did a factory reset then flashed CM11 with TWRP. CM11 installation was successful except for one problem. My mobile network is not available and a message appears on the screen(You need to refer to the SIM card instruction that came with your phone.) The CM11 file that I installed is: cm-11-20140407-NIGHTLY-m7.zip and after reading that the "Nightly" roms are not the most stable, I then flashed this one: cm-11-20140405-SNAPSHOT-M5-m7.zip. Here is what the Installation looked like in Recovery:
Updating partition details...
Full SELinux support is present.
Formatting Cache using make_ext4fs function.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing ' /sdcard/Download/cm-11-20140405-SN
APSHOT-M5-m7.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details..
Successful.
Following the successful flash, I then installed gapps-kk-20131208. Please be detailed in how I can fix this issue. Thanks so much in advance.
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
KK firmware
cmlusco said:
Have you ever updated to kk firmware? If your using a kk based rom, you also need kk firmware.
Click to expand...
Click to collapse
I don't understand. What is KK firmware? This may seem like a stupid question but I really don't know.
kk
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Zacb01 said:
I am going to feel really stupid if you meant kit kat and if you did then yes I have installed the version for kit kat 4.4.2
Click to expand...
Click to collapse
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Mobile service
Crawshayi said:
No he doesn't mean it has to do with the rom. Firmware is flashed separate from roms. Once you flash it, you don't have to worry about it unless a newer firmware gets released. Go to this thread: http://forum.xda-developers.com/showthread.php?t=2485319 and follow the instructions on the 2nd post. Use 3.11.605.1 NO Boot.img firmware.zip since you'll be doing custom roms.
Click to expand...
Click to collapse
I installed this successfully but I still can't make or receive calls. I am wondering if the version of cyanogenmod that I flashed might not be compatible but I did not get a status 7 error when installing. I am also wondering why I got the sim card message when first installing cm11. The version that I installed is stated above on my first post but cyanogenmod has m7 and m7vzw, I can install m7, which I believe is for GSM but I have a Verizon HTC One. When I try to flash the m7vzw version I get the status 7 error code. I tried to do a fix for it but I may have done this incorrectly since I got a status 6 error code. Plz help. I need this phone for work.
You want the m7vzw, the regular m7 is gsm. Status 7 refers to an error in the update script or an incompatible update binary. Does it give a specific error with that status 7? You should also update your twrp to version 2.7.0.4b-santod. http://www.androidfilehost.com/?fid=23329332407584851
Last i heard cm11 is only in preview and data and calls do not work. That may have changed though.
Error
I updated the twrp to v2.7.0.4b-santod, did a factory reset and tried to flash cm11 for m7vzw and was given this mssg...E:Error executing updater binary in zip ' /sdcard/Download/cm-11-20140124-NIGHTLY-M7VZW.ZIP' Setting performance mode OFF. Error flashing zip....etc.....
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Compatible
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Recommendation
cmlusco said:
Why are you flashing an old nightly, and not the one from yesterday? http://download.cyanogenmod.org/?device=m7vzw&type=nightly
I think your issue is that your trying to flash an older nightly with a newer recovery. The newer recoveries have updated binaries that older roms arent compatie with. So either flash a newer nightly, or and older recovery.
If you want a stable rom, i would not use cm11, i would go with cm10.2.
Click to expand...
Click to collapse
I decided to go with cm 10.2.1. Thanks for everything!
Zacb01 said:
The twrp version you recommended and the yesterday's nightly don't work together. Do you have a recovery and a cm11 that are compatible that you can recommend?
Click to expand...
Click to collapse
Hmm thats strange, mabey cm11 just dosent like twrp or something. Glad you got something figured out.
Upgrading to lollipop
Someone should please help on how to upgrade to lollipop 5.0 on HTC m7 complaining of md5 file not found
I got my htc one back in January and immediately rooted it with s-off and installed twrp, since then I have been using this rom and it has worked just fine. But recently I got quite sick of sense and when I tried in stall this rom the phone would not work, I tried cm11 after but it would not flash at all giving me an error every time. I read that I need to update my firmware but Im not really sure what that means, or how to tell what firmware I am on(I thought firmware was the same thing as a rom?)
sorry if this is a stupid question, Im not really that good with technology :L
thewaffleninja said:
I got my htc one back in January and immediately rooted it with s-off and installed twrp, since then I have been using this rom and it has worked just fine. But recently I got quite sick of sense and when I tried in stall this rom the phone would not work, I tried cm11 after but it would not flash at all giving me an error every time. I read that I need to update my firmware but Im not really sure what that means, or how to tell what firmware I am on(I thought firmware was the same thing as a rom?)
sorry if this is a stupid question, Im not really that good with technology :L
Click to expand...
Click to collapse
There were some recent changes to CM11 that require a new recovery. Have you tried the latest version of TWRP?
Where you using the CM11 nightlies or M releases?
durgis said:
There were some recent changes to CM11 that require a new recovery. Have you tried the latest version of TWRP?
Where you using the CM11 nightlies or M releases?
Click to expand...
Click to collapse
I used the most recent nightly at the time, this was on Wednesday. Im on twrp 2.6.3.3, could you or someone link me how to update twrp? goomanager does not work for some reason and those are the only tutorials i can find.
thewaffleninja said:
I used the most recent nightly at the time, this was on Wednesday. Im on twrp 2.6.3.3, could you or someone link me how to update twrp? goomanager does not work for some reason and those are the only tutorials i can find.
Click to expand...
Click to collapse
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
durgis said:
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
Click to expand...
Click to collapse
thank you
durgis said:
Looks like you're a few versions behind, the latest version (2.7.0.8), and fastboot installation instructions are available at the link below.
http://forum.xda-developers.com/showthread.php?t=2416431
Click to expand...
Click to collapse
I just updated and it still didn't work :C
thewaffleninja said:
I just updated and it still didn't work :C
Click to expand...
Click to collapse
Where there any errors while installing the rom in TWRP? You might try one of the CyanogenMod snapshots instead of a nightly, they're a bit more stable and well tested. Also, make sure that you backup and wipe when switching between different roms.
http://download.cyanogenmod.com/?device=m7vzw&type=snapshot
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
MM MaD said:
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
Click to expand...
Click to collapse
You can do either but ensure two things for avoiding a possible bootloop. One is the TWRP and the other is wiping all except internal storage before flashing the ROM.
You should have the modified TWRP 3.0.2-23.
Wipe, flash ROM and flash TWRP before booting as the existing TWRP is likely to be overwritten by the stock recovery. Speaking from experience!
Though I was going from 3.2.7 to 3.2.8, TWRP was overwritten which I found only after booting and when I tried to get back into recovery.
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
jfodra said:
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
Click to expand...
Click to collapse
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
lekronop said:
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
Click to expand...
Click to collapse
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
jfodra said:
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
Click to expand...
Click to collapse
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
lekronop said:
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
Click to expand...
Click to collapse
Oh okay. Thanks a lot for the clarifications.
jfodra said:
Oh okay. Thanks a lot for the clarifications.
Click to expand...
Click to collapse
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
lekronop said:
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
Click to expand...
Click to collapse
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
jfodra said:
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
Click to expand...
Click to collapse
Yes it does.. That's the reason I unlock the bootloader as soon as I get a new device
i was on freedom os . i am back on stock oxygen os but i have 2 issues.
1) when i got an update to 3.2.7 it showed in german that there is an update even though the language i chose was english
2) The boot animation shows the freedom os splash screen and then the boots into stock. Ihave got the boot animation of stock os but need instructions on how to flash the zip.
Can someone throw light on the above 2 issues?
Hello, I find now we have 2 latest TWRP recoveries, one is built by dianlujitao, the other one is the official build.
Which one do you choose? Why?
microwaveoven said:
Hello, I find now we have 2 latest TWRP recoveries, one is built by dianlujitao, the other one is the official build.
Which one do you choose? Why?
Click to expand...
Click to collapse
Use the official. If you have issue with it, the use blu_spar v14 twrp.
And read FAQ #9 in this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Use the official one.
abhibnl said:
Use the official one.
Click to expand...
Click to collapse
I flashed the official one, but the phone auto rebooted each time after the splash screen of the recovery appeared......
microwaveoven said:
I flashed the official one, but the phone auto rebooted each time after the splash screen of the recovery appeared......
Click to expand...
Click to collapse
I was using the official 3.0.3 and now I am on 3.0.4-0 by jcadduono. For me both work without issues.
Try the 3.0.4
I love the one blu_spark provides. Never had serious problems with it, but I disliked the fact that TWRP provided an outdated build all the time which loved to make serious problems.
microwaveoven said:
I flashed the official one, but the phone auto rebooted each time after the splash screen of the recovery appeared......
Click to expand...
Click to collapse
I am using the 3.0.4 version for official TWRP thread and it's working wonderfully for me. Maybe your flashing procedure is wrong or something is messing with your recovery.
abhibnl said:
I am using the 3.0.4 version for official TWRP thread and it's working wonderfully for me. Maybe your flashing procedure is wrong or something is messing with your recovery.
Click to expand...
Click to collapse
Since the flashing procedure is really simple and easy, only a "fastboot flash recovery xxx.img", I think there may be something messing with my recovery, but I flashed it after fully decrypted (wiped) the device. Anyway, I always encounter weird problems, I don't mind these problems now.
tnsmani said:
I was using the official 3.0.3 and now I am on 3.0.4-0 by jcadduono. For me both work without issues.
Try the 3.0.4
Click to expand...
Click to collapse
So many versions of TWRP...
Thank you, I'll try.
emuandco said:
I love the one blu_spark provides. Never had serious problems with it, but I disliked the fact that TWRP provided an outdated build all the time which loved to make serious problems.
Click to expand...
Click to collapse
Yes! I also think so! :good:
I've been out of the ROMing game on the V500 for quite a while. I last flashed a pre-rooted stock ROM back in 2015 when Lollipop was released. I would like to update to the latest version of Lineage OS. I currently have a "bumped" version of TWRP installed, 2.8.6.0. I believe the bump is so it passes the bootloader check when the device is powered on. Is it safe to update TWRP to 3.1.1.0 using TWRP's official app or will this cause problems since it isn't bumped? Is it even necessary to update to the newest version of TWRP to flash LineageOS?
I looked around in the threads and saw posts about installing TWRP from scratch, but nothing about updating TWRP or a "bumped" version of the newer version of TWRP.
oesjmr said:
I've been out of the ROMing game on the V500 for quite a while.
Click to expand...
Click to collapse
Download twrp (credits: fefiform) from here: https://dl.twrp.me/v500/
Install it using flashify or your current twrp by installing the image. Don't use twrp app since some users often get bugs with it
No need for bump since v500 is already unlocked
I suggest to try crdroid since lineageOS has battery problems & bugs like WiFi