Ive been trying to install cm10.1 on my E975 since RC2 and for some reason none of the zips will work. I am currently running Rootbox and using TWRP v.2.4.3.0. Every time i've wiped the device, factory reset and tried to flash the zip, I get a md5sum error. I've downloaded every zip from RC2 all the way up to the stable release and they all do the same thing. Am i missing something here? I can flash any other rom and by backups work just fine, but when it comes to CM10.1 it doesnt want to play nice at all. T_T can someone help me possibly?
jin-roh said:
Ive been trying to install cm10.1 on my E975 since RC2 and for some reason none of the zips will work. I am currently running Rootbox and using TWRP v.2.4.3.0. Every time i've wiped the device, factory reset and tried to flash the zip, I get a md5sum error. I've downloaded every zip from RC2 all the way up to the stable release and they all do the same thing. Am i missing something here? I can flash any other rom and by backups work just fine, but when it comes to CM10.1 it doesnt want to play nice at all. T_T can someone help me possibly?
Click to expand...
Click to collapse
Possibly wrong phone forum..if your downloading from sprint lgog forum on your e975 might be whyits not working the sprint version is lg-ls970
i beleive this is the forum you are wanting the lgog international version??
http://forum.xda-developers.com/forumdisplay.php?f=1838
Well I looked it up and it says on both here and cyanogenmod.com that the ls970 is the same as the e975. I rooted and downloaded rootbox using the xda forums for the e975 as well. I'm just at a loss a to what to do.
Sent from my LG-LS970 using xda app-developers app
Did you check the MD5 to make sure they match?
The 975 is nearly the same as the 970, but not exactly, at least software-wise. This can be a cause; also, updating your recovery to 2.5 can help. I would search through the threads for the 975 and look for recovery updates, and then try again, but with a 975 CM ROM.
LS970 is sprint cdma, where the E975 is intl gsm. Both have the same general hardware, but they difference in radio and E975 has fm radio.
Related
Has anyone still been getting these nightlies? Just checked this and had an update for cm10.1 which I thought was odd because it says the romantic was abandoned and I installed the update and now there is no service on my phone. Wifi still works though anyone else have this problem?
Sent from my Nexus 7 using Tapatalk HD
What Rom are you running? And where did you get it?
Sent from my Jelly Flavored Epic Touch
Double check to make sure you are not running a JB Modem??
btaylor545 said:
Has anyone still been getting these nightlies? Just checked this and had an update for cm10.1 which I thought was odd because it says the romantic was abandoned and I installed the update and now there is no service on my phone. Wifi still works though anyone else have this problem?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Are you talking about CMTeamEpic's CM10.1 nightlies? If so, I have flashed them as well. Once I do (regardless of a CM10 --> CM10.1 or Stock rooted GB/ICS --> CM10.1), I get the same problem with the modem. Under the about tab of settings, I see "Baseband Version Unknown". As seen in the attached screenshot. I'm going to continue to play around with the builds to see if I can find a workaround. Have you found one yet?
EDIT: I have also tried flashing the build then flashing the FF18 modem and then FL24 modem (both are ICS modems from rwilco) to no avail.
EDIT 2: You might want to change (or ask a moderator to change) the title of the OP to CM10.1, since that's what you're asking about.
EDIT 3: I figured out what the problem was. Some files leftover after flashing conflict with the 4.2.2 CM10.1 build. What I did to fix it was this: backup any important files on the internal memory, flash back to a stock ICS build (I chose FF18), factory reset from within the build (this clears everything on the internal memory), flash to a rooted ICS build (again, I chose FF18), flash a safe CWM bootloader, and flash the nightly you want. Hope this helps. Respond or PM me if you want more details.
dastin is using phantom freaks build bot and will be generating his nightlies. that's what your seeing. The other dev works was abandoned.
clean flash since its an entirely diff kernel now.
Sorry tried a couple different ways then gave up and went to CM 10.1 wild on the night. But what had happened was I was on CMTeamEpic's CM 10 4.1.2 and it sent me a CM 10.1 nightly in the CMupdater and I Installed it and the modem was crap but now that there is a work around for Netflix on Wild I'm sticking to this one. sorry I responded so late been crazy busy with work and what not.
Sent from my SPH-D710 using Tapatalk 2
I just flashed the new lifeless ROM for this phone v14 jellybean, I came from v11. Does it have to do with the radio updates or something? I remember reading on one of the post i need to update the radios but dont know where to get them or if the phone already as them.
Update them from the thread
Sent from LG Optimus Prime G
I had that problem too, but I put it on airplane mode and then switch it off. Wifi working ever since. Hope it works for you. It did for me
Sent from my LG-LS970 using xda premium
radios zip link
clice said:
I just flashed the new lifeless ROM for this phone v14 jellybean, I came from v11. Does it have to do with the radio updates or something? I remember reading on one of the post i need to update the radios but dont know where to get them or if the phone already as them.
Click to expand...
Click to collapse
flash through recovery just like a rom http://forum.xda-developers.com/showthread.php?t=2176186
I had this same problem the first time around because it didn't flash the radio update correctly. But I re-downloaded the radios and flashed again. It worked like a charm. Great work by the devs. It is truly amazing.
Greetings! This is the first time I've felt compelled to post in the forums, so I apologize in advance if this happens to be in the wrong section. I've been running CyanogenMod 10.1 on my Samsung Galaxy S3 SGH-T999VVLLH2 (Mobilicity) for quite some time now, and have only recently been interested in downloading and installing the nightly installments that are released.
I haven't had any issues installing the new nightlies at all, until seemingly after revision 20130513. It seems that after this installment, I receive an "assert failed, get prop, status 7" error, upon the attempt at installing any newer nightly revisions. Now, I did a tremendous amount of digging around before I decided to make the post, and discovered that within the newer revisions, the updater-script now seems to flag certain Baseband versions of the phone, and prior to revision 20130513 (currently have), it didn't, and I had no issues installing.
When I go into the CyanogenMod settings, all of the nightly updates are available, as usual, up to the latest at the time of the post (20130524) but none will install. In the latest revisions the updater-script does show a similar version (T999VVLDLL1), which I've come to understand is an update for the software.
Am I required to do another update before installing the latest CyanogenMod 10.1 nightlies? Or is there another solution I haven't discovered yet? Any help regarding this would be greatly appreciated. Thanks!
On a side note, I am running the latest ClockWorkMod Recovery as well.
Im surprised that it happened to you on an AOSP recovery. Usually it happens when its a modded recovery with a kernel.
Try TWRP. Or check for an update.
Sent from my GT-I9505 using xda premium
You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.
Edit : here read up on this before flashing http://forum.xda-developers.com/showthread.php?t=2290118
T999V VLDLL1 Bootloader + Modem (Flashable .zip)
Sent from my SGH-T999 using Tapatalk 2
TheLastSidekick said:
You need to flash a firmware update that will update the bootloader. Not the UVDMD5 one though for sure because that's for T-Mobile. Maybe the other one. Lemme try linking you to the thread.
Edit : here read up on this before flashing http://forum.xda-developers.com/showthread.php?t=2290118
T999V VLDLL1 Bootloader + Modem (Flashable .zip)
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Correct. Once I flashed this my random reboots completely stopped.
Sent from my SGH-T999 using xda app-developers app
yanikd said:
Correct. Once I flashed this my random reboots completely stopped.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I have same problem and same phone t-online Firmware is up to date but i rooted for first time with no problem but cyanagon wont instal status 7 error. Please help
The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.
Downgrade to LL1 firmware for now and it should flash.
Or change the asserts in the updater script
Sent from my SGH-T999V using xda premium
DocHoliday77 said:
The latest T999V firmware is VLDMF2. It's been out less than a week so many cm and aosp roms will not have added I to their asserts to allow install.
Downgrade to LL1 firmware for now and it should flash.
Or change the asserts in the updater script
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
I have 4.1.2
Dunno i live in europe. thought firmware is different than us or so
First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.
when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?
yotaxd said:
I have 4.1.2
Dunno i live in europe. thought firmware is different than us or so
First i used this i used "cm-10.1-20130716-NIGHTLY-d2tmo.zip" and "gapps-jb-20130301-signed" but Statuts 7 error than i tried : T999V_VLDLL1_noradio_v3 but there is also Status 7 error.
when i boot into recovery mods it says CWM-based Revovery v5.5.0.4 : : CF-v1.5 is this OK ?
Click to expand...
Click to collapse
Well first thing you should do is update that old recovery. May be that's all you need.
The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.
What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.
If yours is international, do not flash anything you find here!
Sent from my SGH-T999V using xda premium
DocHoliday77 said:
Well first thing you should do is update that old recovery. May be that's all you need.
The reason I mentioned the T999V firmware is because that's what the rest of the thread was for, so I assumed that's the model you had.
What model is your device? The T999 is a US only variant, the T999V is the Canadian variant. The European models should be the international ones, I9300.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
If yours is international, do not flash anything you find here!
i do not know if its internatianl oder t-mobile. but it should be t-mobile because starting the phone there is t-mobile logo and it is rent from t-mobile
anyway i installed new recovery 6. via google play but in recovery mode there is still Status 7. even its t-mobile. i can try every version because there is always status 7 so i can not damge phone installing wrong version i think. o the other hand i have always wipe chare/ factory before installing the cyanagenmod. i must restore data now and system setting by advanced backup thats kinda annoying. but next i should maybe try INT. now
If you don't know what model it is, don't flash anything!
Look under the battery.
Sent from my SGH-T999V using xda premium
They are adding the assert for T999VVLDMF2: http://review.cyanogenmod.org/#/c/45740/
[SOLVED!!]
i have this problem too when i want to install some roms like AOKP and JB 4.2.2 , i get same error !!
just go to recovery mode cwm then
go to mount and storage ---> unmount /system
now format /system and /data
try agian install cm rom , and it'l work :good:
HTC One
you guys got any ideas on the att M7 version of this problem. im almost positive i RUUd in order to flash CM but i couldnt get it to work. im on KitKat now cant get it to sideload or install from sd.
got any ideas?
Hey guys, right now im running CM 10 stable build, but when i flashed CM 10 i flashed the d2att, which worked fine for me. SO i decided to dirty flash CM 10.1 d2att since i flashed the att build last time, then i figured, maybe i got lucky last time, so i dirty flashed d2tmo and it still didnt work!
I dont wanna have to wipe everything and do a clean install all over again! SOMEONE PLEASE HELP!!!!!
Im with wind, so thats why the d2tmo made more sense, in case your wondering
Just to be sure, you do have the T999V model, correct?
If so, your answer is here:
http://forum.xda-developers.com/showthread.php?p=41701398
Sent from my SGH-T999L using xda premium
CM10 is 4.1.2 and CM10.1 is 4.2.2. You cannot dirty flash different Android versions, you have to wipe and start over, after backing up everything first of course.
Alright thanks!
Just a quick question before i flash, do i need to be on stock TW, cuz as i said im on CM10
And all i do is flash this, reboot and then flash CM 10.1 and gapps? right?
Nandroid backup first if you haven't. You will need to factory reset after flashing cm I'm pretty sure. Backup your internal sdcard too, just in case.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
Nandroid backup first if you haven't. You will need to factory reset after flashing cm I'm pretty sure. Backup your internal sdcard too, just in case.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
You don't need to wipe data from CM 10 -> 10.1.
PSA: Upgrading from CM10 to CM10.1
As you may have noticed, we started updating some devices from cm10 (Android 4.1) to 10.1 (Android 4.2) during the weekend. The upgrade process has been tested extensively for the older devices (manta and mako didn't have that problem since they started out with 10.1), so you should be able to update directly without losing any data.
The single application known not to work is the Clock: Our changes to 4.1's clock to add the Stopwatch and Timer in CM10 aren't compatible with Google's own implementation of those features in 4.2 (which we're using in cm10.1); If your clock starts crashing after upgrading to 10.1, simply go into the Settings -> Apps menu, choose Clock from the All tab, and hit "Clear data".
Click to expand...
Click to collapse
Can somebody please tell me if it is safe to flash this http://forum.xda-developers.com/showthread.php?p=41701398 on CM10 or should i be on TW!?!? Pleaseeee, i wanna use CM 10.1 and this looks like it would help, im just afraid of bricking my phone
Jaz-Crahh said:
Can somebody please tell me if it is safe to flash this http://forum.xda-developers.com/showthread.php?p=41701398 on CM10 or should i be on TW!?!? Pleaseeee, i wanna use CM 10.1 and this looks like it would help, im just afraid of bricking my phone
Click to expand...
Click to collapse
Thats why I linked you to it. Just be sure you have a T999V and not a T999 model S3. Provided you do, it is safe to flash. many have already done so.
You can flash it while on TW or CM.
The assert is already there to include that bootloader in the latest CM10.1 Nightlies. I would suggest to flash CM10.1 & Gapps, then wipe cache & dalvik, then check your Baseband under Settings and About Phone, it may already be VLDLL1, because flashing a ROM shouldn't change those files (modem, etc.).
DJ_SpaRky said:
The assert is already there to include that bootloader in the latest CM10.1 Nightlies. I would suggest to flash CM10.1 & Gapps, then wipe cache & dalvik, then check your Baseband under Settings and About Phone, it may already be VLDLL1, because flashing a ROM shouldn't change those files (modem, etc.).
Click to expand...
Click to collapse
Cm won't flash, which is most likely because the phone isn't on LL1. Even if it is, its not going to hurt it to flash that firmware package.
If you want to be sure first though, what is your current baseband? Its under settings, about device.
Sent from my SGH-T999L using xda premium
yea, it is LL1 (T999VVLDLL1)
Did you ever flash just the modem?
Or have you ever updated via ota or by odin flashing the firmware?
Sent from my SGH-T999L using xda premium
The error msg i get is " E : Error in /sdcard/CM10/cm-10. 1. 0-RC5-d2att. zip (status 7) Installation aborted "
Same goes for when i flash d2tmo
I think ive heard of that status 7 error somewhere, could that be the reason?
ALSO, i can easily flash carbon rom 4.2.1
I just prefer CM and i like not losing my data, so yea, the fact that i can flash Carbon but not CM 10.1 shows that theres no problem with my version of CWM
Update your CWM if you are not using the latest version. Whether or not Carbon flashed is not relevant.
Also, don't flash AT&T ROMs. Just because you can doesn't mean you should. Flash T-Mobile ROMs. With d2tmo CWM. Link to the Odin .tar is in my signature. You flash the proper CWM, and CM will stop hassling you. When you attempt to flash CWM, it checks your bootloader version and recovery version. If either don't match what it's looking for - installation aborted.
Jaz-Crahh said:
ALSO, i can easily flash carbon rom 4.2.1
I just prefer CM and i like not losing my data, so yea, the fact that i can flash Carbon but not CM 10.1 shows that theres no problem with my version of CWM
Click to expand...
Click to collapse
First, I never said there was a problem with CWM, though if you aren't using the latest, I'd suggest updating it.
Second, you never answered my questions in my last post.
Third, I don't know how old Carbon 4.2.1 is but they are now on 4.2.2. When cm went to 4.2.2 is when they started checking your firmware, so just because you can flash that doesn't mean you can flash something newer.
So if you please, do the following and tell me what it says.
Open Terminal Emulator
Enter the following line:
getprop ro.bootloader
Let me know what it says please.
Also, everytime I've ever seen a Status 7 error, its been caused by the firmware not being up to date. So at this point I still believe flashing that firmware pkg I linked earlier will be your fix.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
First, I never said there was a problem with CWM, though if you aren't using the latest, I'd suggest updating it.
Second, you never answered my questions in my last post.
Third, I don't know how old Carbon 4.2.1 is but they are now on 4.2.2. When cm went to 4.2.2 is when they started checking your firmware, so just because you can flash that doesn't mean you can flash something newer.
So if you please, do the following and tell me what it says.
Open Terminal Emulator
Enter the following line:
getprop ro.bootloader
Let me know what it says please.
Also, everytime I've ever seen a Status 7 error, its been caused by the firmware not being up to date. So at this point I still believe flashing that firmware pkg I linked earlier will be your fix.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
When i did the terminal thing, i got
"T999VVLALE6"
Ok, that's the problem then. Its scropted to not flash unless that reads VLDLL1. hou can either flash the firmware pkg I linked to, or odin flash the correct firmware. After that you should be able to flash cm.
The pkg I linked to would be the easiest to use.
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
Ok, that's the problem then. Its scropted to not flash unless that reads VLDLL1. hou can either flash the firmware pkg I linked to, or odin flash the correct firmware. After that you should be able to flash cm.
The pkg I linked to would be the easiest to use.
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Okay, will do, ill flash that pkg and get back to you when i attempt to flash CM 10.1 again
Jaz-Crahh said:
Okay, will do, ill flash that pkg and get back to you when i attempt to flash CM 10.1 again
Click to expand...
Click to collapse
Now this is gonna be awkward, but theres a couple of links there, which one exactly should i click?/:
Hello,
I am very new to rooting, and just rooted my Sprint LG G2 with 4.4.2 KitKat through IORoot 25 and then used AutoRec as my TWRP. I then downloaded Cyanogenmod11 from its website onto my phone, and tried to flash install it through AutoRec. However, when I try to install the CM11 ROM, I get the "MD5 not found" message, and when I try to reboot after this, my phone goes into what I think is Bootloop (the LG home screen continuously turns on for a couple seconds, then stops for a split second, and then turns back on for a couple seconds). Fortunately, I am was able to hard restart my phone by holding Power and Volume Up together while this screen is on, and I was able to restore my phone with the backup I made, and my phone is now working fine with the stock ROM. Has anyone else had this problem before, and if so is there a better way for my to install custom ROM, and/or fix that MD5 message? Does anyone know what that MD5 message means?
One other note, I have been doing some reading and I currently have ZVC radio. I'm not sure what this means exactly, but would this make a difference?
Thanks!
If you are on 4.4.2 cm won't work on that version yet
Sent from my LG-LS980 using XDA Premium 4 mobile app
secret.animal said:
If you are on 4.4.2 cm won't work on that version yet
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Interesting, thanks. Are there any ROMs that work for 4.4.2 that people have been using, or am I pretty much stuck with the stock ROM until CM is updated?
Cloudyfa has some in the G2 android development forum. There are some others that will work with sprint.
http://forum.xda-developers.com/showthread.php?t=2687613
[INDEX][REPO][AIO] LG G2 - ROMs | Kernels | MODs | Recoveries [UPDATED][9 June 14]
Has some info in it also
Sent from my Nexus 7 using Tapatalk
secret.animal said:
If you are on 4.4.2 cm won't work on that version yet
Click to expand...
Click to collapse
Hi, would you mind explaining further why it wont work, coz i have the exact problem that LGGuy83 is/was experiencing (i used autorec too and cm11 gives me an lg logo boot loop) and this is the closest thread to getting an answer
What radio are you on? Zv8 radio is required.
Sent from my AOSP on Grouper using Tapatalk
secret.animal said:
What radio are you on? Zv8 radio is required.
Sent from my AOSP on Grouper using Tapatalk
Click to expand...
Click to collapse
thanks for ur reply,
Im not sure what "radio" version, but i know its updated to VS980-26A
anyway i sorted the problem by using the cm11 version on this link
http://forum.xda-developers.com/showthread.php?t=2702958
i simply downloaded the one here and installed, (skipped all the steps and just put it in the internal memory and flashed it)
Now its working well. ill let you know if any problems arise.