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.
mnemonic_br said:
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.
Click to expand...
Click to collapse
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
atifsh said:
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
Click to expand...
Click to collapse
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.
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
Related
Hi Guys. This problem has me beat and i have been searching around for an answer but cant seem to figure it out
Running the LG E975 - 4.1.2 stock rom on build e97510b. This phone was from ebay and as far as i can tell its from taiwan (has taipei set as default timezone)
I rooted my phone successfully (checked using root checker)
Used freegee to unlock the bootloader and install CWRecovery 6.0.3.0
I Have tried an AT&T Rom, International rom and a rom from the "android development" section also
None of these roms will flash (always says fail)
The error is;
Assert failed: getprop("ro.product.device") == "e975" || getprop(ro.bui
E:Error in /sdcard/Roms/"rom name".zip
Status 7
I have read it could be due to the first line in the updater-script file. i have tried deleting it, saving it however notepad wont let me just save over it. i need to save it as a new file, and replace it in the zip but when i try to replace the file in the zip it says it cant do it due to invalid or corrupted file (surely not every rom ive downloaded is actually corrupted)
Any help with this would be much appreciated. Thankyou in advance
Have you considered they are called e970 roms for a reason?
Use kdz updater to flash stock e975 rom,then root and unlock. After,flash e975 roms. Id you want e970 roms,buy an e970.
Sent from LG E975 pwd by CM 10.2
Really this is something i can't understand.
Means, you have a e975 so why the heck you flash roms from at&t? And that for the first time you flash a rom on this phone. Why not choose a rom for e975 to be sure that nothing happen. Or maybe you like it more dangerous)))
You should better inform yourself (reading helps) before start flashing roms.
A rule of thumb: flash only that, what is made for your phone(modell)
The at&t rom was an accident, and once i realised it i downloaded a proper e975 rom. The international one and the regular one are boh e975 and they do not work. I think you missed the point im trying to make here, no rom including 2 types of e975 rom will flash due to the error i am receiving
Can you tell what roms aren't working?
Btw. the error you get is only when you flash a rom from a different modell, it's the updater script.
Sure. I have tried Pacman, CM10.1 Nightly and beanstalk
all give me the same error
I am bout to try to flash the "geehrc_unsigned_stock_rom_E975_INTL.zip" rom which is version 10E, my current is version 10B. if this works i will try to flash from that rom to a custom.
Ok i was just able to flash the "geehrc_unsigned_stock_rom_E975_INTL.zip" with no problems in CWRecovery so i did a backup and tried to flash the CM10.1 Nightly and it failed again. im not sure whats wrong
bikerboi85 said:
Ok i was just able to flash the "geehrc_unsigned_stock_rom_E975_INTL.zip" with no problems in CWRecovery so i did a backup and tried to flash the CM10.1 Nightly and it failed again. im not sure whats wrong
Click to expand...
Click to collapse
Wat error yu r getting...??
Sent from my LG-E975 using xda premium
It was the same error as in my original post. I worked out what was wrong just now. Even though i selected CWM recovery in freegee it for some reason still installed TWRP. I did a nandroid restore to the original rom, used freegee again and selected CWM recovery. this time it installed it correctly and roms are flashing properly now. thanks for the help anyway guys
Problem solved and thread closed...
I've observed that quite a few people with the model number E988 have been having trouble in the modding(?) process. Mostly from due to unlocking and flashing a custom recovery via FreeGee (no offense intended to the maker of FreeGee)
So out of curiosity, before I have to unecessarily attempt the dreadful Recovery process again, have any of you guys managed to flash a custom ROM on your E988? If so, how?
(sorry mods if this is in the wrong forum).
I have flashed and used almost all the roms available in the original dev section.......no problems what so ever...... only one rom was problematic....... that is the PA port........ though not mandatory, keep the modem zip handy.......
Sent from my LG-E988 using xda app-developers app
Install cwm and disable lg security via freegee...and install rom without flashing modem is ok...working..only change apn..
But you can't back to stock rom without flashing kdz..
Once you reboot you can install rom via cwm but can not enter stock rom...
Sent from my LG-E988 using xda app-developers app
BauhausPen said:
I've observed that quite a few people with the model number E988 have been having trouble in the modding(?) process. Mostly from due to unlocking and flashing a custom recovery via FreeGee (no offense intended to the maker of FreeGee)
So out of curiosity, before I have to unecessarily attempt the dreadful Recovery process again, have any of you guys managed to flash a custom ROM on your E988? If so, how?
(sorry mods if this is in the wrong forum).
Click to expand...
Click to collapse
I concur especially the 10.2 cm rom (not the at&t version one) the one for e98X devices... always gives me error
any idea how to go back to stock rom ? I get various errors by lg flash tool ... device not detected mid way through or low battery error !!!
BauhausPen said:
I've observed that quite a few people with the model number E988 have been having trouble in the modding(?) process. Mostly from due to unlocking and flashing a custom recovery via FreeGee (no offense intended to the maker of FreeGee)
So out of curiosity, before I have to unecessarily attempt the dreadful Recovery process again, have any of you guys managed to flash a custom ROM on your E988? If so, how?
(sorry mods if this is in the wrong forum).
Click to expand...
Click to collapse
Looks like freegee does not work anymore. E986 or E988. Alternatives? Thanks.
demax123 said:
Looks like freegee does not work anymore. E986 or E988. Alternatives? Thanks.
Click to expand...
Click to collapse
FreeGee works fine on E988. I own one (Indian variant) and I can vouch for it. All you have to do is select "No" on the disable LG security option. CWM will get installed just fine. And since the FreeGee recovery is lokified, you are good to go for any rom including 4.3 ones. Like I said in my previous reply, I have used almost all the roms available in the Original DEV section. Only the PA port causes issues with the signal reception. Rest all work fine. If you are facing problems, be specific and I will try to help.....
bhoyonkor said:
FreeGee works fine on E988. I own one (Indian variant) and I can vouch for it. All you have to do is select "No" on the disable LG security option. CWM will get installed just fine. And since the FreeGee recovery is lokified, you are good to go for any rom including 4.3 ones. Like I said in my previous reply, I have used almost all the roms available in the Original DEV section. Only the PA port causes issues with the signal reception. Rest all work fine. If you are facing problems, be specific and I will try to help.....
Click to expand...
Click to collapse
I own G Pro e988 and want to flash Cyanogenmod 11.
Can you describe the steps of using the FreeGee app? And what stock firmware should I use with the freegee app. Should I flash stock Jellybean, root and the install FreeGee?
For know I am on stock kitkat (e98820c_twn_XX) and freegee don't work.
Thank you!
Hi guys, please help me
I was trying to flash my S3 tmobile with CM 11, but I got an error "assert failed: getprop("ro.bootloader")"
I search on xda and flash the bootloader then I turn off the phone.
Now I cannot power up my phone, can't get into recovery mode or anything.
westlife2206 said:
Hi guys, please help me
I was trying to flash my S3 tmobile with CM 11, but I got an error "assert failed: getprop("ro.bootloader")"
I search on xda and flash the bootloader then I turn off the phone.
Now I cannot power up my phone, can't get into recovery mode or anything.
Click to expand...
Click to collapse
What Firmware were you running before you flashed CM 11?
FcHsChilD said:
What Firmware were you running before you flashed CM 11?
Click to expand...
Click to collapse
I don't remember. Before flashing CM 11, I didn't touch anything except rooting it by using this guide on android central (sorry, I can't post the link)
I think it will be the original
What exactly did ypu you flash? You can copy the link on your post, just put a few spaces in it. I have a feeling I know what happened but I cant be certain without knowing exactly what you flashed.
Did you ever update by taking any of the OTA's?
DocHoliday77 said:
What exactly did ypu you flash? You can copy the link on your post, just put a few spaces in it. I have a feeling I know what happened but I cant be certain without knowing exactly what you flashed.
Did you ever update by taking any of the OTA's?
Click to expand...
Click to collapse
Yes I did update to 4.3 from T-mobile OTA
I rooted though this guide http://androidcentral .us/2014/04/root-t-mobile-samsung-galaxy-s3/
I flash this firmware http://forum .xda-developers.com/showthread.php?t=2282603
westlife2206 said:
Hi guys, please help me
I was trying to flash my S3 tmobile with CM 11, but I got an error "assert failed: getprop("ro.bootloader")"
I search on xda and flash the bootloader then I turn off the phone.
Now I cannot power up my phone, can't get into recovery mode or anything.
Click to expand...
Click to collapse
westlife2206 said:
Yes I did update to 4.3 from T-mobile OTA
I rooted though this guide http://androidcentral .us/2014/04/root-t-mobile-samsung-galaxy-s3/
I flash this firmware http://forum .xda-developers.com/showthread.php?t=2282603
Click to expand...
Click to collapse
I don't consider myself an expert but did you read that post for what you flashed and how it says in big bold red letters DO NOT flash this if you are running latest 4.3.If I can make any assumptions on it you bricked due to flashing a previous bootloader(Doc correct me if I'm wrong..still learning)
Yup. If you flash those MD5 bootloaders on 4.3 you're bricked. You'll need to use the debrick thread stickied in development.
Okay thank you, I will try this thread http://forum.xda-developers.com/showthread.php?t=2439367
Btw, how can I fix the error "assert failed: getprop("ro.bootloader")" ?
You first need to know what firmware build you are on. Then edit the updater-script and replace one of the ones listed in the assert lines with yours.
Use caution though. There are reasons for these and only fo this if you are 100% certain it is safe to flash.
Hi there! I've just tried to flash the latest nightlie to my device (LG Optimus G E-975) and got this error (Screenshot). Any idea how could I fix it? Thanks for your help
PS: I'm using the latest version of TWRP (Official) you could see that in the screenshot.
the second one here is the latest https://mirrors.c0urier.net/?dir=android/Dadi11/Required files/Recovery
also flash this https://mirrors.c0urier.net/?dir=android/Dadi11/Required files/Bootloader Update
Hi! Thanks for the revovery and bootloader, I flashed both of them, but still got the same error when trying to flash the ROM. I think it has something to do with the device's name "This package is for device: e975; this device is geehrc4g." Do you know how to fix that?
http://forum.xda-developers.com/opt.../geehrc-resurrection-remix-lp-v5-4-0-t3068937
Flash this room
Sent from my Optimus G using Tapatalk
Lenin_g18 said:
Hi! Thanks for the revovery and bootloader, I flashed both of them, but still got the same error when trying to flash the ROM. I think it has something to do with the device's name "This package is for device: e975; this device is geehrc4g." Do you know how to fix that?
Click to expand...
Click to collapse
you must on e975, flash e975 stock or rom that base on e975.
Recently I got my Note 5 and have been enjoying it, unlocked and custom ROM and everything with the latest TWRP. But recently I've wanted to flash a different custom ROM and everytime I do so, I get the error message:
E10001: Failed to update system image.
Updater process ended with Error 7: Error installing zip file xxx (xxx is just the filename)
No matter what ROM I flash, whether it is the Xiaomi.eu ROM or any other custom AOSP/LOS ROM, I get the same message.
I need help as I have no idea what to do at all and am worried that the phone might be messed up permanently.
Download notepad++ and 7zip. Unzip the file, go to meta.inf/com/google/android and open updater script with notepad++. Select and delete the assert lines, and make sure to remove the empty space. Zip the file and flash it.
ensure your phone is note 5 pro, not note 5
BlackHawk580 said:
Recently I got my Note 5 and have been enjoying it, unlocked and custom ROM and everything with the latest TWRP. But recently I've wanted to flash a different custom ROM and everytime I do so, I get the error message:
E10001: Failed to update system image.
Updater process ended with Error 7: Error installing zip file xxx (xxx is just the filename)
No matter what ROM I flash, whether it is the Xiaomi.eu ROM or any other custom AOSP/LOS ROM, I get the same message.
I need help as I have no idea what to do at all and am worried that the phone might be messed up permanently.
Click to expand...
Click to collapse
Could you solve the error?
Same issue here. If you updated to the most recent firmware, then it's impossible to flash anything using the TWRP recoveries available. I get the same E1001 error. I don't think it has anything to do with the model or the ROM. Be careful, because trying to reflash a firmware package will result in a hard brick, and you need to use an ARB authorisation bypass to be able to restore your phone.
For now I have to stay on the latest Global ROM, nothing else I can do.
wrathking said:
Download notepad++ and 7zip. Unzip the file, go to meta.inf/com/google/android and open updater script with notepad++. Select and delete the assert lines, and make sure to remove the empty space. Zip the file and flash it.
Click to expand...
Click to collapse
I tried this with the Xiaomi.eu ROM - no luck, same error. It's not about the ID of the device (TWRP reports that my device is indeed whyred), it's something else.
Mi rom
stephendt0 said:
Same issue here. If you updated to the most recent firmware, then it's impossible to flash anything using the TWRP recoveries available. I get the same E1001 error. I don't think it has anything to do with the model or the ROM. Be careful, because trying to reflash a firmware package will result in a hard brick, and you need to use an ARB authorisation bypass to be able to restore your phone.
For now I have to stay on the latest Global ROM, nothing else I can do.
I tried this with the Xiaomi.eu ROM - no luck, same error. It's not about the ID of the device (TWRP reports that my device is indeed whyred), it's something else.
Click to expand...
Click to collapse
Have you tried using miflash tool?
wrathking said:
Have you tried using miflash tool?
Click to expand...
Click to collapse
Yes. This triggers a hard brick.
Hey I have the same issue on a redmi 5 plus; does anyone found a solution for this? I updated to the last firmware too, and the only rom that works now is evolutionX.
i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........
deepinsys said:
i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........
Click to expand...
Click to collapse
I'm alive
deepinsys said:
i think i have a solution for this problem, i solved it on my redmi note 3, if anyone is active here, give reply, i will help u........
Click to expand...
Click to collapse
Hi, I'm facing the same issue. Can you help me bro? Thank you.
Check whether you are using latest twrp or Orange fox recovery. If not ,then update it. I guess this should solve the problem.