Develop Bugs

Installed the wrong rom?

Hi, i followed the instructions on http://forum.xda-developers.com/showthread.php?t=1614827 and it has a video in it to show you how to install jelly bean. Unfortunately, the directions were to install a verizion rom (the one that has gsm or whatever) and so now i have gsm.
I then put my phone into recovery, did a factory reset and cache wipe and then tried to install Are You Jellin m1 and then m2. Neither of those seem to work. The error reads:
assert failed: getprop("ro.product.device") == "toroplus" || getprop("ro.build.product") == "toroplus"
E;error in /sdcard/download/Are-You-Jellin-M1.zip
(Status 7)
Installation aborted
What do i do now??

You start by posting in the correct section.
Sent from my AOSP Android 4.1.1 Galaxy Nexus

mastermind1234321 said:
Hi, i followed the instructions on http://forum.xda-developers.com/showthread.php?t=1614827 and it has a video in it to show you how to install jelly bean. Unfortunately, the directions were to install a verizion rom (the one that has gsm or whatever) and so now i have gsm.
I then put my phone into recovery, did a factory reset and cache wipe and then tried to install Are You Jellin m1 and then m2. Neither of those seem to work. The error reads:
assert failed: getprop("ro.product.device") == "toroplus" || getprop("ro.build.product") == "toroplus"
E;error in /sdcard/download/Are-You-Jellin-M1.zip
(Status 7)
Installation aborted
What do i do now??
Click to expand...
Click to collapse
look for the sticky thread in this section on how to return to stock using odin and follow those directions

You also posted in the wrong place!
2 for 2
Thread moved
FNM

kennyglass123 said:
You also posted in the wrong place!
2 for 2
Thread moved
FNM
Click to expand...
Click to collapse
KENNY!!!
Sup bro?
Sent from my AOSP Android 4.1.1 Galaxy Nexus

mastermind1234321 said:
What do i do now??
Click to expand...
Click to collapse
You go to that same toolkit thread and ask questions there. Better yet, go here first, and then here. Read it all. I think you should.
jakdillard said:
look for the sticky thread in this section on how to return to stock using odin and follow those directions
Click to expand...
Click to collapse
ODIN is not supported by Google and AOSP, not even by Samsung. Don't recommend such a tool when there is a official tool for the kind of procedure you are suggesting: fastboot.

[Q] Installing 4.2 failure-- help, please

Tried to install 4.2 via CWM (Method 1, without deleting the Recovery folder), and got the following error:
assert.failed getprop ("ro.product.device") == "maguro" || getprop ("ro.build.product") == "maguro"
E: Error in /sdcard/e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13.zip (Status 7)
Installation aborted.
I followed the instructions to a T, or so I thought. Can anyone point me to what I did wrong, and how I can fix it? My phone's build is JZO54K.
Thanks in advance
mudge

do you have a CDMA phone? if so, it will never work and you need to wait for a custom rom or the factory images/OTA

Zepius said:
do you have a CDMA phone? if so, it will never work and you need to wait for a custom rom or the factory images/OTA
Click to expand...
Click to collapse
Nope, it's a GSM phone, purchased directly from Google's Play Store. So it should work, right?

did you modify any system files, specifically your build.prop? are you on the stock rom?

Zepius said:
did you modify any system files, specifically your build.prop? are you on the stock rom?
Click to expand...
Click to collapse
Stock ROM and I don't think I ever modified build.prop (I used Mark Skippen's Galaxy Nexus Toolkit to unlock the bootloader and root the phone, but that's all).

Zepius said:
did you modify any system files, specifically your build.prop? are you on the stock rom?
Click to expand...
Click to collapse
Okay, I found something interesting. Looking through build.prop I found a comment saying "ro.build.product is obsolete; use ro.product.device"
BUT I don't see any ro.product.device line anywhere. Should I insert it? No, I take that back. I found the ro.product.device line. It's in there.

Similar problem
I have a very similar problem with my non-rooted GSM Gnexus, stock recovery.
After I sideload the 4.2 update i get the following on the recovery:
assert failed: File_getprop("/system/build.prop". "ro.build.fingerprint") =="google/takju/maguro:4.1.2/JZO54K/485486:user?release-keys" ||
and it just kinda repeats that and says installation failed.
I used QBking77's instructions to installing the SDK (I can't post links but hes on youtube, all we did was follow the Google given SDK and installed the platform tools and SDK)
I'm pretty sure I am running takju ever since I manually installed 4.1.1, then got the OTA to 4.1.2.
dunno what to do...

iCurmudgeon said:
Tried to install 4.2 via CWM (Method 1, without deleting the Recovery folder), and got the following error:
assert.failed getprop ("ro.product.device") == "maguro" || getprop ("ro.build.product") == "maguro"
E: Error in /sdcard/e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13.zip (Status 7)
Installation aborted.
I followed the instructions to a T, or so I thought. Can anyone point me to what I did wrong, and how I can fix it? My phone's build is JZO54K.
Thanks in advance
mudge
Click to expand...
Click to collapse
Flash system.img and radio-i9250...img from stock JZO54K Then try to flash OTA again.
Sent from my Galaxy Nexus using xda app-developers app

wisefreakz said:
Flash system.img and radio-i9250...img from stock JZO54K Then try to flash OTA again.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Nevermind, followed instructions on addictivetips.com (again can't post links) and it worked like a charm.
Thanks guys,

iCurmudgeon said:
Tried to install 4.2 via CWM (Method 1, without deleting the Recovery folder), and got the following error:
assert.failed getprop ("ro.product.device") == "maguro" || getprop ("ro.build.product") == "maguro"
E: Error in /sdcard/e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13.zip (Status 7)
Installation aborted.
I followed the instructions to a T, or so I thought. Can anyone point me to what I did wrong, and how I can fix it? My phone's build is JZO54K.
Thanks in advance
mudge
Click to expand...
Click to collapse
I was facing similar issue, to install 4.2 I downloaded 4.2 (JOP40C) from developers.google.com/android/nexus/images and followed the instructions.
It was pretty straight forward
boot your phone to bootloader
install bootloader
flash takju image to phone
I have outlined all the steps to resolve this at http://chandankumar.com/blog/2012/11/14/install-android-4-dot-2-on-galaxy-nexus/
- Ck

Unable to upgrade to cm-10.1.2-d2spr

I am currently running cm-10.1-20130304-EXPERIMENTAL-d2spr-m2 and trying to upgrade to cm-10.1.2-d2spr.
I have tried through the cynagenmod updater, through goo manager and directly through TWRP. All give me an error (status 7)
Here is my TWRP recovery log.
"
Installing zip file '/data/media/0//cmupdater//cm-10.1.2-d2spr.zip'
Installing '/data/media/0//cmupdater//cm-10.1.2-d2spr.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "L710VPBLJ7" ||
getprop("ro.bootloader") == "L710VPBMA6" ||
getprop("ro.bootloader") == "L710VPBMB1" ||
getprop("ro.bootloader") == "L710VPBMD4"
assert failed: getprop("ro.bootloader") == "L710VPBLJ7" || getprop("ro.bootloader") == "L710VPBMA6" || getprop("ro.bootloader") == "L710VPBMB1" || getprop("ro.bootloader") == "L710VPBMD4"
E:Error in /data/media/0//cmupdater//cm-10.1.2-d2spr.zip
(Status 7)
E:Error installing zip file '/data/media/0//cmupdater//cm-10.1.2-d2spr.zip'
I:Attempt to load settings from settings file...
I:Version number saved to '/data/media/0/TWRP/.version'
I:Switching packages (TWRP)
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
"
Cheers
Sent from my SPH-L710 using xda premium

How about updating your bootloader this is the md4 firmware AIO this should do it
http://db.tt/Qt6NcH0a
Just flash this in recovery reboot the phone then go back into recovery and flash your new rom.
Sent from the future via Tapatalk 4

So I do not need to flash back to stock first?
Your saying I can just flash the new boot loader then flash new ROM, and that is it?
Where does this boot loader come from? Are we sure it is compatible with my sprint gs3?
Will this effect my recovery (TWRP)?
Got any links to information on the new boot loader vs the old boot loader, and what it effects?
Cheers & Thanks
Sent from my SPH-L710 using xda premium

NO, YES, YES, NO,
This is the firmware update for md4 it's found on Freezas thread. This is the Sprint Galaxy S3 forum. So yes this is only for the sprint phone. If you noticed I am a recognized Contributor here on xda I'm sure I wouldn't be one if I was giving you bad information or links. But hey you can do your own research. That's why the #1 and #2 rules are search before asking or posting because this has been answered over and over. Your not the first to ask this very same question.
Do not forget to flash firmware update and BOOT Up first then go back into recovery and flash your rom.
Sent from the future via Tapatalk 4

Thank you, it worked perfectly. Funny the new boot loader also worked with the ROM I was running, then I updated to 10.1.2. All went well.
Not to doubt your credibility, just wanted to be sure, cause I need a phone.
Thanks again!!!!
Sent from my SPH-L710 using xda premium

edfunkycold said:
NO, YES, YES, NO,
This is the firmware update for md4 it's found on Freezas thread. This is the Sprint Galaxy S3 forum. So yes this is only for the sprint phone. If you noticed I am a recognized Contributor here on xda I'm sure I wouldn't be one if I was giving you bad information or links. But hey you can do your own research. That's why the #1 and #2 rules are search before asking or posting because this has been answered over and over. Your not the first to ask this very same question.
Do not forget to flash firmware update and BOOT Up first then go back into recovery and flash your rom.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Is this something that could work for a C Spire phone that is giving the same message?
Thanks for any help you can give.

edfunkycold said:
NO, YES, YES, NO,
This is the firmware update for md4 it's found on Freezas thread. This is the Sprint Galaxy S3 forum. So yes this is only for the sprint phone. If you noticed I am a recognized Contributor here on xda I'm sure I wouldn't be one if I was giving you bad information or links. But hey you can do your own research. That's why the #1 and #2 rules are search before asking or posting because this has been answered over and over. Your not the first to ask this very same question.
Do not forget to flash firmware update and BOOT Up first then go back into recovery and flash your rom.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
I tried this on my Sprint GS3 and it flashed okay, everything was good but then I went to reboot and now it won't turn on at all, not into download mode or recovery either. Do you know how to fix this/what would cause this?

pwnurface999 said:
I tried this on my Sprint GS3 and it flashed okay, everything was good but then I went to reboot and now it won't turn on at all, not into download mode or recovery either. Do you know how to fix this/what would cause this?
Click to expand...
Click to collapse
If you have an SGS3 which contains Knox then trying to change the bootloader with a firmware change is a huge no-no. I suspect this is what happened here. You should be able to use Odin to push the stock MK3 .tar file that CNexus provided in another thread. The only thing Knox is truly scared of is when it detects an attempt to replace it with another bootloader which is non-Knox, and it will then step in and disable your phone. Of course using Odin requires download mode, so I don't know what to tell you there.

Mr. Struck said:
If you have an SGS3 which contains Knox then trying to change the bootloader with a firmware change is a huge no-no. I suspect this is what happened here. You should be able to use Odin to push the stock MK3 .tar file that CNexus provided in another thread. The only thing Knox is truly scared of is when it detects an attempt to replace it with another bootloader which is non-Knox, and it will then step in and disable your phone. Of course using Odin requires download mode, so I don't know what to tell you there.
Click to expand...
Click to collapse
Oh wow TIL, my fault for not reviewing what KNOX was. Thanks for the advice!

Help with installing CM11 on T999l 4.3

So I'm a complete noob with these rooting and etc because I never really bothered. But after updating my s3 to 4.3 its been so slow and its pissing me off. I want to install cm11 on it but I have no idea how. I rooted it using some method that doesnt void warranty called safe root. In the past i've tried to do it using twrp and the roms I found online but when I tried to install it it said md5 not found. I also tried to get CWM but couldnt get the latest version for t999l and even when I did i couldnt figure out how to install cm11.
Can someone please guide me on doing this the easiest and simplest way? And please talk to me like a little kid cause im so confused Dx.

You can use ODIN to flash CWM. Make sure you flash the most recent version of CWM Recovery. If you search here on the forum, you will find plenty of tutorial on using PC based Odin. Best if you download the correct recovery for your phone first.
If that approach appears too cumbersome, you could use Mobile Odin (you don't have to but I recommend buying the pro version).
Once the recovery is successful, when flashing the Rom, make sure you uncheck "Check MD5".

Perseus71 said:
You can use ODIN to flash CWM. Make sure you flash the most recent version of CWM Recovery. If you search here on the forum, you will find plenty of tutorial on using PC based Odin. Best if you download the correct recovery for your phone first.
If that approach appears too cumbersome, you could use Mobile Odin (you don't have to but I recommend buying the pro version).
Once the recovery is successful, when flashing the Rom, make sure you uncheck "Check MD5".
Click to expand...
Click to collapse
I can't seem to find the correct CWM file to use in odin. I downloaded an img file from the cwm website but doesn't it have to be a tar file

Please use ROM Manager and it will point to the correct place to get a tar file. If you let Rom Manager to flash the recovery, it will do the job.

Perseus71 said:
Please use ROM Manager and it will point to the correct place to get a tar file. If you let Rom Manager to flash the recovery, it will do the job.
Click to expand...
Click to collapse
ROM Manager won't recognize my phone model. When I look to choose the phone model the only s3 model on there is a MetroPCS version.

cf3434 said:
ROM Manager won't recognize my phone model. When I look to choose the phone model the only s3 model on there is a MetroPCS version.
Click to expand...
Click to collapse
That makes sense because there isn't a special version for T999L. Try the one for D2TMO instead.

Perseus71 said:
That makes sense because there isn't a special version for T999L. Try the one for D2TMO instead.
Click to expand...
Click to collapse
That's the TWRP one right?

Yes. I believe there's one for CWM as well.

Perseus71 said:
Yes. I believe there's one for CWM as well.
Click to expand...
Click to collapse
Ok I flashed it thank you! Now when I'm going to install the cm11 and gaps how do I uncheck md5?

If you flashed TWRP, then under install menu you should see a checkbox for "Checking MD5". I don't use CWM so can't speak for it.

Perseus71 said:
If you flashed TWRP, then under install menu you should see a checkbox for "Checking MD5". I don't use CWM so can't speak for it.
Click to expand...
Click to collapse
I'm using CWM and I'm getting status error 7 when trying to flash. I tried to follow the directions of someone that said to delete everything with getprop in the updater script but that didnt work either it just says installation failed with that one. I have no idea what to do now..

Was that the most recent version of CWM ? The most recent version for T-Mobile is 6.0.4.5

Perseus71 said:
Was that the most recent version of CWM ? The most recent version for T-Mobile is 6.0.4.5
Click to expand...
Click to collapse
Yes that is the one I have.

If that's the case and you did download the correct Rom for SGH-T999 then you will have to comment the Asset Statements from within the updater script.

Perseus71 said:
If that's the case and you did download the correct Rom for SGH-T999 then you will have to comment the Asset Statements from within the updater script.
Click to expand...
Click to collapse
I went into the updater script and it said all this
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo" || abort("This package is for \"d2tmo\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");
and I deleted all of that and tried to install it again but it just says installation failed and thats it.

Do you think its because I dont have any of those bootloaders? My baseband is T999LUVUBMK4 and it isnt up there.

Perseus71 said:
Was that the most recent version of CWM ? The most recent version for T-Mobile is 6.0.4.5
Click to expand...
Click to collapse
I just wanted to say I actually had an old CM11 download that didnt support my broadband version but I got it now, Thank you for your help!

Glad you have got it working.

[Q] Assert Failed Error

so as this thread I go the same issue... but I couldn't understood how to fix it..
My English isn't the best ..
I did understood that this may happened from another Rom I tried to install..
I would very appreciate every attempt to help me
THANKS A LOT
http://forum.xda-developers.com/showthread.php?t=1858448
by the way this is the error I get..
getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru"
And i tired to flash new CWM and its didn't work out..
EDIT: solved.. I flashed an older version of CWM and its worked