Running CM9 alpha 4 and wanting to help test some of the nightlies. I have tried to flash several of them and always get the assert error like below:
assert failed: getprop("ro.product.device") == "
hercules" ll getprop("ro.build.product") == hercules
E:Error in /sdcard/update-cm-9-20120426-SNAPSHOT-hercules-alpha1-signed.zip
(Status 7)
Installation aborted
I have tried CWM hard 5.0.2.6 and .7 and Touch 5.5.0.14 beta 14. Same thing on all of them. I know it is trying to verify the model, just don't understand why it doesn't match. Help...
Thanks
Maybe bad download?
djintrigue808 said:
Maybe bad download?
Click to expand...
Click to collapse
Highly unlikely... tried 0614, 0615 and 0618. Lots of other people are able to install it, so has to be some weird setting for me.
roy.walker777 said:
Highly unlikely... tried 0614, 0615 and 0618. Lots of other people are able to install it, so has to be some weird setting for me.
Click to expand...
Click to collapse
Did you:
1. Wipe data/factory reset
2. Darkside super wipe
3. Kernel cleanser
4. Flash radio
5. Flash ROM
6. Flash gapps
7. Flash Darkside Cache Wipe???
Install a Hercules based CWM. Will fix the problem.
djintrigue808 said:
Did you:
1. Wipe data/factory reset
2. Darkside super wipe
3. Kernel cleanser
4. Flash radio
5. Flash ROM
6. Flash gapps
7. Flash Darkside Cache Wipe???
Click to expand...
Click to collapse
Wiping doesn't change what the recovery says his device is. Update to a new recovery yours is reporting a different device.
Tapatalked from my Galaxy S II.
pio_masaki said:
Wiping doesn't change what the recovery says his device is. Update to a new recovery yours is reporting a different device.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Will try and flash again... any chance you can give me a link to make sure. So far I have manually flashed, flashed from inside Rom Manager (told it the correct phone) and also flashed the touch recovery. Pretty sure they were all for T989.
Thanks
This happened to me also trying to flash the aokp nightly 610 and 615, not sure what the issue is. Downloaded from the PC and phone, still the same issue
Sent from my aokp_tenderloin using xda premium
The best recovery to be used can be found in this thread.
http://forum.xda-developers.com/showthread.php?p=27229604
Sent from my beastly Galaxy S 2.
JaylanPHNX said:
The best recovery to be used can be found in this thread.
http://forum.xda-developers.com/showthread.php?p=27229604
Sent from my beastly Galaxy S 2.
Click to expand...
Click to collapse
That was what I was using. I downloaded and flashed again just to be sure. Same thing. Is there a manual way to set the build.device and product.device variables? For some reason these recoveries are not setting it on mine.
Thanks,
Roy
Someone has to know how to fix this...
Anyone?
@roy.walker777 unmount/mount system then install. same thing happened to me and it worked fine after that
and im on CWM hard 5.0.2.7
Download CM9 for Hercules and not Galaxy S2.TMO S2 is called Hercules.
Sent from my SAMSUNG-SGH-T989 using xda premium
quest4fire said:
Download CM9 for Hercules and not Galaxy S2.TMO S2 is called Hercules.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Holy hell! Many thanks. I wrongly assumed that GalaxyS2 referred to the T989. On Cyanogenmod you need to use the URL name Hercules.
Damn I feel stupid now...
Related
I rooted my Bell Galaxy SIII this afternoon using Mr. Robinsons method.
All good. Have root. Installed CWM (LTE Variant and other newer listed on Mr. Robinsons thread. One at a time, same error)
Booted into recovery and tried to install CM10 after factory reset, dalvick wipe, yada, yada yada.
I get the error:
Assert Failed: getprop("ro.product.device*) =="E:Error in /SDCARD/cm-10-20120912-nightly-d2Att.zip (Status 7)
Might be some left out as not all of the error code is shown.
Tried multiple times to download CM using different browsers and directly on the phone.
I am able to restore factory rooted image no problem.
I then installed TWRP v2.2.2.0
Same error when trying to install CM10-current nightly
I'm assuming that this is related to device ID and I'm trying to install ROM's not suitable for it?
I've tried with AOKP version from Task and get same error.
http://forum.xda-developers.com/showthread.php?t=1766684
Pretty sure these are good for Bell version....
Any idea's or confirmation that these won't work with my phone.
Thanks
Mike
You need cwm 6.0.1.2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Not sure what the issue is but I can tell you that I have installed task aokp with twrp and cwm recovery versions back to 5.5.0.4 with no problems on my Bell phone.
liltitiz said:
You need cwm 6.0.1.2
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
Just so I learn something out of this...Why do I need this? I understand that both versions of CWM and TWRP I installed are used by people with the same hardware?
Just want to understand what I am missing.
Thanks,
Mike
EDIT: Okay, after doing some looking at the Build.prop file I see I have a D2Cann and the rom is listed as for D2ATT so the assumption I'm making is the older recoveries match that and won't proceed while CWM 6.012 doesn't? I'm downloading and going to install the latest CWM now to try and confirm this. Still not sure why this has worked for some people and not for me unless they are changing their build.prop but I haven't been able to find that to confirm it.
If you go in the cm10 thread in original developpenent, they specify which recovery to install with a link to download it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mikewestlake said:
EDIT: Okay, after doing some looking at the Build.prop file I see I have a D2Cann and the rom is listed as for D2ATT so the assumption I'm making is the older recoveries match that and won't proceed while CWM 6.012 doesn't? I'm downloading and going to install the latest CWM now to try and confirm this. Still not sure why this has worked for some people and not for me unless they are changing their build.prop but I haven't been able to find that to confirm it.
Click to expand...
Click to collapse
its not the recovery that does the actual check for the device. it's the assert in the updater-script of the rom that you're trying to flash. CM10 checks for "d2att" and if thats not what in your build.prop it will error out and refuse to flash. Either remove that line from the updater-script or edit your build.prop.
Also. you need to try your best to read the OPs of the roms you're thinking about flashing. In the CM10 thread they even give you the information of which recovery you need to use and where to get it.
task650 said:
its not the recovery that does the actual check for the device. it's the assert in the updater-script of the rom that you're trying to flash. CM10 checks for "d2att" and if thats not what in your build.prop it will error out and refuse to flash. Either remove that line from the updater-script or edit your build.prop.
Also. you need to try your best to read the OPs of the roms you're thinking about flashing. In the CM10 thread they even give you the information of which recovery you need to use and where to get it.
Click to expand...
Click to collapse
Thanks,
yeah, in this case, I thought I read everything and maybe got too much info. Still for coming from other devices (HTC DesireZ, Legend, couple of Asus transformers), having different device versions is a new step to tick off and learn.
Had the same issue with your rom too. Can I ask that you add a note to the OP about making sure Canadian versions change the build prop or only use CWM 6 cause I had the same issue with yours when trying to install. I'm not going to be the only guy that missed this.
Gonna install CWM 6 and change build prop to install your ROM. It looks good.
Thanks again.
Mike
mikewestlake said:
Thanks,
yeah, in this case, I thought I read everything and maybe got too much info. Still for coming from other devices (HTC DesireZ, Legend, couple of Asus transformers), having different device versions is a new step to tick off and learn.
Had the same issue with your rom too. Can I ask that you add a note to the OP about making sure Canadian versions change the build prop or only use CWM 6 cause I had the same issue with yours when trying to install. I'm not going to be the only guy that missed this.
Gonna install CWM 6 and change build prop to install your ROM. It looks good.
Thanks again.
Mike
Click to expand...
Click to collapse
Using ROM Manager helps you keep your CWM recovery up to date. You can find the app in the play store
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Sent from my SAMSUNG-SGH-I747 CM10 + KT747, 96-2106 MHz, noop, ktoonservative, undervolted, 3150mAh battery.
Thanks to: Ktoonsez, Task650 and Cyanogen for their amazing works!
I tried following some videos by QBKing77 and some other advice I found on threads here but am stuck and don't want to go any further in case I mess something up.
So far I have flashed back to a rooted EL26, installed CWM5.0.2.7, wiped everything, and tried installing the latest stable CM9 ROM.
When I go to flash the CM9 ROM, here's what I get:
assert failed: getprop....Installation aborted.
I have attached a screenshot. Please help! Naked without a phone!
nomaxtech said:
I tried following some videos by QBKing77 and some other advice I found on threads here but am stuck and don't want to go any further in case I mess something up.
So far I have flashed back to a rooted EL26, installed CWM5.0.2.7, wiped everything, and tried installing the latest stable CM9 ROM.
When I go to flash the CM9 ROM, here's what I get:
assert failed: getprop....Installation aborted.
I have attached a screenshot. Please help! Naked without a phone!
Click to expand...
Click to collapse
idk too much about this but i think you have the wrong rom downloaded. It LOOKS like youdownloaded the GT-I9000T version which is not the rom for our phone model. you probably want TeamEpics:CM9.1 Beta.
Try this: http://forum.xda-developers.com/showthread.php?t=1874374
DO NOT flash any ROM unless it says epic 4g touch you willbrick your phone if you try and flash a ROM for any other galaxy s II
Sent from my SPH-D710 using xda app-developers app
nomaxtech said:
I tried following some videos by QBKing77 and some other advice I found on threads here but am stuck and don't want to go any further in case I mess something up.
So far I have flashed back to a rooted EL26, installed CWM5.0.2.7, wiped everything, and tried installing the latest stable CM9 ROM.
When I go to flash the CM9 ROM, here's what I get:
assert failed: getprop....Installation aborted.
I have attached a screenshot. Please help! Naked without a phone!
Click to expand...
Click to collapse
That looks like the Rouge recovery. I'd stop using that to flash immediately.
If I were you, and provided that you can get to Odin mode on your phone, use a one click restore and then do some more research.
How not to brick - http://forum.xda-developers.com/showthread.php?t=1525495
The one click I'd use so you'll be rooted - http://forum.xda-developers.com/showthread.php?t=1877041
Flash calkulins rom. Really any gingerbread rom. Then try it again. I have had that happen to me before too. I fixed it by flashing the rom from el26 kernel. I did not wipe anything before hand. After cm9 flashed while still in the el26 kernel I factory reset the device. Worked fine.
sent from my BAD A$$ Epic touch
That makes sense because I went directly to the CM website and downloaded for the Samsung Galaxy S 2 because I could not find a link for Epic 4G Touch. I guess I don't know too much about this but I was hoping for something that was a final release and not a beta or alpha. Is that team epic beta my only option?
Btw for being a beta its damn near perfect. I am ru ning a nightly after the beta however. But I remember having no problems with it. Try it you won't be disappointed
sent from my BAD A$$ Epic touch
nomaxtech said:
That makes sense because I went directly to the CM website and downloaded for the Samsung Galaxy S 2 because I could not find a link for Epic 4G Touch. I guess I don't know too much about this but I was hoping for something that was a final release and not a beta or alpha. Is that team epic beta my only option?
Click to expand...
Click to collapse
its great.
MoHoGalore said:
That looks like the Rouge recovery. I'd stop using that to flash immediately.
If I were you, and provided that you can get to Odin mode on your phone, use a one click restore and then do some more research.
How not to brick - http://forum.xda-developers.com/showthread.php?t=1525495
The one click I'd use so you'll be rooted - http://forum.xda-developers.com/showthread.php?t=1877041
Click to expand...
Click to collapse
This is the recovery that was posted with QBKing77's video. Also, I didn't see any GI Joe type artwork in the recovery.
nomaxtech said:
That makes sense because I went directly to the CM website and downloaded for the Samsung Galaxy S 2 because I could not find a link for Epic 4G Touch. I guess I don't know too much about this but I was hoping for something that was a final release and not a beta or alpha. Is that team epic beta my only option?
Click to expand...
Click to collapse
That's because or phone is not officially supported by the cyanogenmod team. Both jellybean.ROMs look good but i can only speak on sbrissen's from personal experience
Sent from my SPH-D710 using xda app-developers app
Everytime that I try to flash the CM10 rom for d2att on my Samsung Galaxy S3 sgh i747m editon it says this.
assert failed: getprop("ro.product.device") == "d2att" | | getprop(ro.build.device") == "d2att"
E: Error in /sdcard/Roms/cm-10.0.0-d2att.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I am using ClockworkMod Recovery v6.0.1.5 can anyone help me fix this and get CM10 to flash
Thanks,
Max AKA DJ Stowaway
You are trying to flash att version cm10. But why aren't you using att version of the recovery? V6.0.1.5 is not for att!
tonymtl said:
You are trying to flash att version cm10. But why aren't you using att version of the recovery? V6.0.1.5 is not for att!
Click to expand...
Click to collapse
I know, but I can't get the right one. Could you let me know what to do to change what version of clockworkmod i am using so that I can use the right one.
Thanks
Flash this in recovery http://db.tt/te3vInsu. Reboot recovery and flash cm10...
tonymtl said:
Flash this in recovery Reboot recovery and flash cm10...
Click to expand...
Click to collapse
Thanks, it is now booting in CM10, but does it normally take forever to boot for the first time?
Try out TWRP. It's nicer than CWM. Install GOO manager from the play store, open it, then press the menu button and choose Install openscript recovery. It will then download and install TWRP for you.
Sent from my SGH-I747 using xda premium
Bootloop
djstowaway said:
Thanks, it is now booting in CM10, but does it normally take forever to boot for the first time?
Click to expand...
Click to collapse
Hi Unfortunately I think I am stuck in a boot loop can you help
I am having the same problem. Got everything installed correctly but when it boots for the first time it has the CyanogenMod logo spinning and has been doing it for over 5-10 mins now and won't stop.
How do I fix it?
Did you pull the battery, reboot back into recovery to re flash? Just be sure factory reset before flashing with TWRP.
Sent from my AoCP SGH-I747 using Tapatalk 2
peneoark said:
Did you pull the battery, reboot back into recovery to re flash? Just be sure factory reset before flashing with TWRP.
Sent from my AoCP SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I did that and it worked fine. Thank you. Is there an official CM forum for the AT&T Galaxy S3? Or even the Galaxy S3 US versions at all? When I go to CM website I only see forums for the S1 and S2.
No real forum there for d2att. The is a thread here at XDA that's quite nice.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
peneoark said:
Did you pull the battery, reboot back into recovery to re flash? Just be sure factory reset before flashing with TWRP.
Sent from my AoCP SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I rebooted into recovery and made sure that I wiped the cache and it worked thanks.
Good deal dude
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
disengage said:
Hi there,
I have a Galaxy SIII SGH-i747 from Virgin in Canada. As for as I know, its the same as Bell and every other SGH-i747. So tonight I tried flashing cyanogenmod 10.1 to no avail. I have rooted and installed CWM. When I try to install any ROM it comes up with the error "assert failed getprop status 7". I have searched around and have tried updating CWM recovery through ROM Manager from the play store, but the app doesn't allow me to select my phone model (says there is no official release of CWM for SGH-i747) and says the current version will do. This ROM does not want to install.
HELP!:crying:
Click to expand...
Click to collapse
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy cm10.1
http://d-h.st/8qP cwm
http://d-h.st/qft cwm touch
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
sending onalond
KorGuy123 said:
Status 7 is an out of date recovery or incorrect recovery.
You need a d2att recovery. The Canadian models are d2can. Same phone but it is a system fail safe.
Flash either one in recovery, reboot back into recovery, wipe and enjoy
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
disengage said:
Just to be clear: Load the CWM you linked onto SD. Reboot into CWM, flash new CWM, reboot and wipe?
Also to clarify, I have a Canadian model SGHi747
Click to expand...
Click to collapse
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Okay thanks, I will try later and reply with results.
KorGuy123 said:
Yup. After flashing that zip and rebooting into recovery it'll reboot into the updated recovery.
Make a backup first of course.
I'm on Telus which is also a d2can phone. I've been running twrp for d2att since I bought the phone in Jan.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Also should I flash with ODIN?
disengage said:
Also should I flash with ODIN?
Click to expand...
Click to collapse
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
No recovery.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Hi there, I tried flashing from recovery, choosing zip from sdcard, and I got the same exact error assert failed: getprop(" ro.product.device") == "d2att" || getprop( " ro.build.product " ) == "d2att" E:Error in /sdcard/CWM-recovery_ATT-6.0.2.3_2.zip
(status 7)
Installation aborted.
I tried exactly what you said, still nothing.
Bump.
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Did you have the most recent stock rom before flashing cyanogenmod? The newer versions of the nightlies require that you have the most recent bootloader. If you had ics, it'll fail to flash until you update your bootloader. The most recent build before the bootloader assert that you can flash is rc2.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think so. i have no idea how to check, forgive the noobness plz. My stock firmware is 4.1.1
Bump? Does anyone know how I can flash an updated recovery?
disengage said:
Bump? Does anyone know how I can flash an updated recovery?
Click to expand...
Click to collapse
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
The link I gave you is the most up to date recovery. There is a thread here for most recent stock roms. Quick search will assist you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but I cannot flash the updated CWM. What am I doing wrong?
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
So my question stands: I flashed an outdated recovery by accident, and I want to flash a new, UPDATED recovery. KorGuy provided me with instructions and a link to a new, updated recovery, however I cannot flash that from my current recovery.
What can I do to flash an updated CWM?
Can someone give me a hand?
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
disengage said:
Okay, so I see people are trying to help me but it's so vague. Every article or how to, or help page ive read on this site or others, suggest conflicting ways to perform these mods. Why can't anyone just tell me straight up, you do this, then this, then that? I feel it shouldnt be this much of a headache and before I've even started modding, I'm getting very turned off. I am already frustrated beyond comprehension. Like I said, I've searched, and searched and nothing is helping. Everything is too vague.
Can someone give me a hand?
Click to expand...
Click to collapse
If you can't follow a guide like this and figure things out, maybe flashing ROMs just isn't for you. I'm not trying to offend, but this isn't for everyone.
danieljordanmaddux said:
You need to flash the most recent STOCK firmware through ODIN so you will have the most recent bootloader, then flash your recovery of choice through ODIN, boot into recovery, not system as the recovery will be overwritten iirc. Then flash cm in recovery
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I understand that I need to flash with ODIN. However, don't I need a .TAR recovery? I can't flash .img through ODIN...
Correct. Find the .tar of the recovery. I think you can find the TWRP .tar on their website
Sent from my SGH-T999 using Tapatalk 2
Root your phone and install a custom recovery. Most root guides will include instructions for flashing a custom recovery. Next buy "ROM toolbox" form android market, I say by because you will love this app so much you will want to buy it eventually anyway.
Open ROM toolbox and select cyanogen mod. ROM toolbox will flash your phone for you! It can also flash the custom recovery if you did not do this when you rooted your phone.
Annnother must have root app is titanium backup.
Hope this helps.
Sent from my Nexus 4 using xda app-developers app
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?/: