assert solved but not more updates

[mnemonic_br]

Hi people, after a crash I was unable to again update my ROM. So I needed to remove the 1st line (assert) and not it works. The problem is newer version will always fail. Just that exact ROM I changed the update script will work, automatically, if I need to update I will need to again remove the line.

I understand what assert will do, so if getprop("ro.product.device") differs from my device check it will fail. I think the right side from that statement has been lost, I mean, the script will check somewhere (sys var?) to ensure my device is that expected, and that variable is wrong, how to fix that part, so I will no longer need to edit the script.

Thank you for help.

 

[atifsh]

Hi people, after a crash I was unable to again update my ROM. So I needed to remove the 1st line (assert) and not it works. The problem is newer version will always fail. Just that exact ROM I changed the update script will work, automatically, if I need to update I will need to again remove the line.

I understand what assert will do, so if getprop("ro.product.device") differs from my device check it will fail. I think the right side from that statement has been lost, I mean, the script will check somewhere (sys var?) to ensure my device is that expected, and that variable is wrong, how to fix that part, so I will no longer need to edit the script.

Thank you for help.

Simple, don't make it difficult for yourself.
You don't have e975 but flashing e975 requires your device to show it is e975 or you have to delete the assert every time.
Example my f180 if rooted, unlocked and flashed custom recovery without convering to e975 will be same as above.

Sent from my Nexus 7 using Tapatalk

 

[mnemonic_br]

Simple, don't make it difficult for yourself.
You don't have e975 but flashing e975 requires your device to show it is e975 or you have to delete the assert every time.
Example my f180 if rooted, unlocked and flashed custom recovery without convering to e975 will be same as above.

Sent from my Nexus 7 using Tapatalk

Thank you, but It becomes to happen yesterday just before I tried a new version of Kitkat. I ever need to do such thing, so I know that there exists a way to fix that. With all ROM I tried with my 977 (Avatar, CM, Pacman, and even previous kitkat) that procedure was never necessary.

Fist time I moved from the stock ROM, my e977 "became" a e975, so I suppose it's now a e977 again.

 

[atifsh]

No i think it's the recovery you changed for kitkat, that required mako recovery.
Try changing the recovery first, if that fails flash e975 kdz and start over

Sent from my Nexus 7 using Tapatalk