• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile] Problems fix so u can flash on twrp

mobclan

Android Enthusiast
Oct 15, 2013
356
49
assert failed: getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"

You do this with 7-Zip/WinRAR

Note: DO NOT EXTRACT ROM!
In the ROM go to:

/META-INF/com/google/android/updater-script

1)Open updater-script with a script editor such as notepad/notepad++ (makes things 10x easier), or gedit if you use linux

2)Delete the first line of code (all the way up to the first semicolon you see) and delete the first semi-colon as well

Do not go past the first semiclon when deleteing and DO NOT forget to delete the first semicolon.

Cheers!
 
Sorry for not understanding, but why on Earth would you want to purposely remove the safety check of the device assert check?

It is expressly placed there to keep one from flashing something on the wrong device.

:thinking: :thinking: :thinking:


Our devices are the same exact ones as Sprints SG3's. Any Sprint rom will work on our phones, provided assert lines are removed.
 
  • Like
Reactions: scary alien
Upvote 0
Our devices are the same exact ones as Sprints SG3's. Any Sprint rom will work on our phones, provided assert lines are removed.

Would it not be better to change the "thunderc" reference in the

getprop("ro.product.device") == "thunderc" || getprop("ro.build.product") == "thunderc"

to your specific device's name (i.e., whatever is reported by your getprop ro.product.device)?

That way, you keep the safety of the assert (it should certainly work if you change it to check the proper/expected value).
 
Upvote 0
Would it not be better to change the "thunderc" reference in the



to your specific device's name (i.e., whatever is reported by your getprop ro.product.device)?

That way, you keep the safety of the assert (it should certainly work if you change it to check the proper/expected value).

You certainly could do that, but either way, you're removing the safety check that the assert line provides. Functionally there's no difference between removing the asserts entirely, or adding in your own devices name.
 
  • Like
Reactions: scary alien
Upvote 0
You certainly could do that, but either way, you're removing the safety check that the assert line provides. Functionally there's no difference between removing the asserts entirely, or adding in your own devices name.

Well, I'm guessing that the assert line that the OP mentioned that the ro.product.device (of "thunderc") is not what you guys have?

Changing it to be your specific, proper device would be harmless and in fact, the assert command would evaluate to "true" and the updater-script would continue on as desired.

I'm just not a fan of a casual user finding a flashable .zip file and removing the assert without really understanding that it's there to protect them from flashing something potentially harmful (i.e., files on/for the wrong device).

Thanks!
 
Upvote 0
I'm just not a fan of a casual user finding a flashable .zip file and removing the assert without really understanding that it's there to protect them from flashing something potentially harmful (i.e., files on/for the wrong device).
!

What's the difference between adding your device to an assert, or removing the assert completely? Either way you risk flashing something that's not made for your device.
 
  • Like
Reactions: scary alien
Upvote 0
What's the difference between adding your device to an assert, or removing the assert completely? Either way you risk flashing something that's not made for your device.

I suppose the only risk / downside would be sharing that modded .zip with someone else that does not do the due-diligence of checking that it's a proper flashable for their device.

I get what you're saying, just wanted to express care and caution regarding this.

:)
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones