Assert Failed Error - HTC One X

Hi!
I have the International Version of the HTC One X.
Today I tried to install Paranoid Android. Originally, I had installed the version 1.99. I did this successfully. However, I saw that 2.00 is available. So I tried to reflash a new rom. I got an error as follows:
assert failed: getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru"
I tried a clean rewipe first using a nandriod backup of the stock sense UI, but I couldn't start up after. I then proceed to use the RUU for a complete wipe back to stock. This worked.
When I tried installing again, both 1.99 and 2.00 are giving me the assert failed error.
Would appreciate assistance.
Thanks!

Based on what I've read, the most similar thread I can find is http://forum.xda-developers.com/showthread.php?t=1836023&page=2
Short of editing the check script, I've followed every step in the last post of the thread multiple times. I'm trying to avoid editing the check script if I can.

Ive seen this happen a handful of times. The only way to really get down to this is see what getvar is returning.
If you could go into Recovery (CWM or TWRP) and open up adb shell and issue the command: grep -e 'ro.build.product' -e 'ro.product.device' /system/build.prop
you should see something like this...
~ # grep -e 'ro.build.product' -e 'ro.product.device' /system/build.prop
grep -e 'ro.build.product' -e 'ro.product.device' /system/build.prop
ro.product.device=endeavoru
# ro.build.product is obsolete; use ro.product.device
ro.build.product=endeavoru

koppen_kf said:
Hi!
I have the International Version of the HTC One X.
Today I tried to install Paranoid Android. Originally, I had installed the version 1.99. I did this successfully. However, I saw that 2.00 is available. So I tried to reflash a new rom. I got an error as follows:
assert failed: getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru"
I tried a clean rewipe first using a nandriod backup of the stock sense UI, but I couldn't start up after. I then proceed to use the RUU for a complete wipe back to stock. This worked.
When I tried installing again, both 1.99 and 2.00 are giving me the assert failed error.
Would appreciate assistance.
Thanks!
Click to expand...
Click to collapse
see this (ro.product.device) & this (ro.build.product) this is reading from your build.prop file. make sure those two lines are outputting endeavoru. Maybe some dev changed it to there Rom name or some ****. Also don't go deleting assert checks in that script unless you want a very nice & shiny paper weight

As mentioned, my nandroid backup of stock rom is not working (it'll just hang at HTC One X boot screen).
I can't seem to access ADB on recovery mode (I'm on CWM 5.8.2.4).
I can't mount USB either.
So it seems that RUU is the next best solution for me to recheck what getvar is really printing.
What baffles me is that I clearly managed to install Paranoid Android 1.99 once, it was only when I tried 2.00 did this assert failed error occur. After which, both 1.99 and 2.00 throw the assert failed errors.
I've dragged out this round of flashing too long and now its under 30%, so I'm just charging the phone in recovery mode. Do I have any other options for now?

that is an extremely old cwm, why don't you flash 5.8.4.0?
5.8.4.0 has fixes for charging in recovery, adb and usb mounting.

Do you have any custom themes installed via theme manager?

I looked more into the issue, it looks s though ClockworkMod 5.8.2.4 had a typo in the build.prop and that is why your assert is failed.
ro.build.product=endeavouru
ro.product.device=endeavouru
they should be
ro.build.product=endeavoru
ro.product.device=endeavoru
The solution is to go into fastboot mode and flash 5.8.4.0 cwm

Thanks!
I've flashed the new CWM and it worked!
The thing I don't understand is how my first install even worked in the first place.
Thanks all

the older paranoidandroid may have had that script checking either endeavoru or endeavouru. Glad it is working.

Squirrels said:
I looked more into the issue, it looks s though ClockworkMod 5.8.2.4 had a typo in the build.prop and that is why your assert is failed.
ro.build.product=endeavouru
ro.product.device=endeavouru
they should be
ro.build.product=endeavoru
ro.product.device=endeavoru
The solution is to go into fastboot mode and flash 5.8.4.0 cwm
Click to expand...
Click to collapse
Worked Thanks.... :good::good::good::good:

Related

Can't install zips in recovery

I've got a nasty problem on my Sprint Gnex. Every time I boot into recovery and tell it to flash a .zip file, it returns this:
Code:
-- Installing (whatever).zip
Finding update Package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "toroplus" || getprop("ro.build.product") == "toroplus"
E:Error in (whatever).zip
I have this problem in CWM and CWM Touch as flashed by ROM Manager. I've tried to edit my build.prop file to say either toroplus or torospr, but neither setting works. It doesn't matter what zip I use, they all die here.
I can back up and restore using nandroid, so what's broken and how do I fix it?
Try flashing the toroplus CWM image via fastboot: http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.3.1-toroplus.img
That did it! Thanks!

"Status 7" error in CWM while installing ROM

Hey everyone,
I'm currently trying to install the latest CM10 FXP131 ROM on my Arc S Lt18i. I flashed my phone to the first ICS Stock ROM by Sony and rooted it to install CWM Recovery.
Now, the next step was to flash the ROM. So I downloaded the Anzu version of the ROM, copied it to my SD and changed into Recovery mode. I picked "install zip from sdcard" and chose the ZIP I've just downloaded.
But instead of installing the ROM I got a error every time. It says
E:Error in /sdcard/cm-10-20120731-UNOFFICIAL-anzu.zip
(Status 7)
Installing aborted
Can someone help me to finally install the ROM?
Thank you so much,
Max
You also need to install the kernel.
Something like this a few lines above?
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18I" || getprop("ro.product.board") == "LT18i"
T-119a said:
Something like this a few lines above?
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18I" || getprop("ro.product.board") == "LT18i"
Click to expand...
Click to collapse
Nope, this is the full protocol:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
E:Error in /sdcard/cm-10-20120731-UNOFFICIAL-anzu.zip
(Status 7)
Installation aborted.
Just for information. The first thing I've done after installing CWN was straight installing the .zip . I did not flashed the kernel or wipe. Maybe that has something to say?
EDIT: Oh, and after every try to install the ROM my phones hangs up at the "SONY" logo and won't boot. I always have to flash the original sony .ftf to make it run again :/
Thank you,
Max
Open the cm-10-20120731-UNOFFICIAL-anzu.zip with a zip viewer, extract the boot.img and flash it via fastboot. Then perform a Full Wipe and try to flash the ROM again.
T-119a said:
Open the cm-10-20120731-UNOFFICIAL-anzu.zip with a zip viewer, extract the boot.img and flash it via fastboot. Then perform a Full Wipe and try to flash the ROM again.
Click to expand...
Click to collapse
I will try that, but I need a unlocked bootloader for that all, right? Or isn't that necassary at all?
maexjen said:
I did not flashed the kernel or wipe. Maybe that has something to say?
Click to expand...
Click to collapse
Yep.
maexjen said:
I will try that, but I need a unlocked bootloader for that all, right? Or isn't that necassary at all?
Click to expand...
Click to collapse
If you want to flash cyanogen you have to unlock your bootloader. An unlocked bootloader is recommend for flashing custom Roms and kernels.
Thank you for your clarification! It's working now! =)
T-119a said:
Something like this a few lines above?
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18I" || getprop("ro.product.board") == "LT18i"
Click to expand...
Click to collapse
Hello... I'm flashing new ROM and facing Status 7 error with what you said at the front... Here's the error message:
assert failed: getprop ("ro.product.device") == "c8812" | | gerprop ("ro.build.product") == "c8812" | | getprop ("ro.product.device") == C8812 "| | getprop (" ro.build.product ") ==" C8812 "
E: Error in / sdcard/C8812_20120822005.zip
(Status 7)
Installation aborted.
Can I know the cause of this and how to overcome that? Please & Thanks!
I'm getting this exact same problem on my Arc S except with cm10 Fxp138. My bootloader is unlocked, im rooted, i flashed the kernel first and STILL i get Status 7 error installation aborted. If someone could help, that'd be great
I am also getting the same error but on Sony LWW with Pacman JB ROM.
I also got this status 7 error with the code "Status 7 - symlink: some symlinks failed".
After deleting the first line (before the ; sign) I could get the rom to install.
I would like to know, why / how this can happen... Maybe flashing a false kernel or other things?
I think maybe binary and script don't match each other; or maybe there's error in text of script
(sorry for my bad english)
try to flash the kernel lupus
Firstly, give us recovery log. Secondly, I had such an issue with CM7.1 quite long time ago. I've fixed it by changing phone's ID from LT18i to LT15i via fastboot. There's a proper command for it.
1. Go to CWM
2. Plug phone
3. "adb pull tmp/recovery"
WHAT ?
Try a full wipe ( data , cache )
CM10 on my ARC
I have the same, install new baseband upper then 70 or official ics 4.0.4 then use flashtools to install kernel and flash rom
You have unlocked bootloader ??
i have "Status 7 - symlink: some symlinks failed" when i try install Jelly-v4.zip. anyone help me, i have downloaded that rom 3 times but it can't help
meinmain said:
Hello... I'm flashing new ROM and facing Status 7 error with what you said at the front... Here's the error message:
assert failed: getprop ("ro.product.device") == "c8812" | | gerprop ("ro.build.product") == "c8812" | | getprop ("ro.product.device") == C8812 "| | getprop (" ro.build.product ") ==" C8812 "
E: Error in / sdcard/C8812_20120822005.zip
(Status 7)
Installation aborted.
Can I know the cause of this and how to overcome that? Please & Thanks!
Click to expand...
Click to collapse
I had a lot of frustration with this. Had many attempts. The only thing that seemed to work for me was to flash the doomlord kernel. Then it worked perfectly.

[Q] HTC One X, boot loop problem.

Alright, so after the latest HOX update I had some issues with Sense so I decided it was about time to root my phone and flash some custom ROM. I successfully rooted it, picked my ROM (CyanogenMod), did everything according to instructions, did a backup, wiped everything, started flashing.. and the flashing failed. I've got an error saying:
assert failed: getprop("ro.bootloader") == "1.28.0000" || getprop ("ro.bootloader") == "1.31.0000" || getprop ("ro.bootloader") == "1.33.0000" || getprop ("ro.bootloader") == "1.36.0000" || getprop ("ro.bootloader") == "1.39.0000" || getprop ("ro.bootloader")
The installation was aborted, so I decided to restart my phone and just leave it for later. What a surprise, phone got stuck on the 'HTC quietly brilliant' screen. I went to recovery mode, tried to restore the data, but that didn't do anything.
I'm quite a beginner, and I'm worried that I might not be able to fix this without help. What should I do? Right now I'm unable to even turn it off, it always turns on and remains on the startup screen. Any advice would be greatly appreciated
You have to open the updater script file in the aroma installer and replace the 1.39 with your bootloader number. Probably 1.72 or 1.73
Mr Hofs said:
You have to open the updater script file in the aroma installer and replace the 1.39 with your bootloader number. Probably 1.72 or 1.73
Click to expand...
Click to collapse
Thank you!

[Q] Samsung Galaxy S3 (Tmobile) T999 - Root Access Possibly Lost. Fix?

Hi experts!
I'm trying to install CyanogenMod on my Samsung Galaxy S3 Tmobile (T999) for the first time. I just rooted the device and then installed the One Touch Cyanogen App on the phone, completed the steps on the phone and then installed the s/w on PC. After everything's done and CyanogenMod is installed on the phone successfully I get this msg - root access possibly lost. fix?
I've tried all the 3 options I get on this screen - No, Yes & Go Back. But all of these push me back to square 1 and I have to redo everything again. I've tried at least 5 times but I'm still unable to get CM set up on my phone. Please assist.
Another thing I noticed after I rooted and did a factory reset is that I no longer have Google Contacts Sync available. Calender, Mail, Bookmarks etc all there but no Contacts Sync. When I click on "Contacts" app and click on Accounts I dont find Google listed.
This is my first time rooting & installing custom ROM on my Galaxy S3 (Tmobile). Pls help me.
Flash custom recovery, nandroid, full wipe, then flash cm from their site
Root access is missing
serio22 said:
Flash custom recovery, nandroid, full wipe, then flash cm from their site
Click to expand...
Click to collapse
Thanks for your response. What I did was Unrooted and loaded Stock ROM T999UVUENC2 from Sammobile.com
Then tried to follow the steps from their site get.cm and again everything until the end worked fine. The PC installer completed successfully but when the phone rebooted it showed "Root access is missing". When I select "Yes" here I'm back to square 1 again. This is so frustrating.
Pls, pls, pls, help!
I'm a newbie
Also I'm newbie to this. What is meant by -- Flash custom recovery, nandroid, full wipe, then flash cm from their site
I was only trying to follow the easy way by doing it from their website get.cm but apparently I'm unable to do so.
Please tell me how
Retried still failed
serio22 said:
Flash custom recovery, nandroid, full wipe, then flash cm from their site
Click to expand...
Click to collapse
I entered ClockworkMod Recovery v6.0.4.5 and did the following:
1. Wipe data/factory reset
2. Wipe cache partition
3. Mounts and Storage > format /system
4. Mounts and Storage > mount /system
5. Advanced > wipe dalvik cache
5. Install zip: cm-11-20140210-SNAPSHOT-M3-d2tmo.zip
But I get the following error:
assert failed: getprop ("ro.bootlooder") == "T999UVDLJA" || getprop ("ro.bootlooder") == "T999UVDLJC" || getprop ("ro.bootlooder") == "T999UVDMD5" || getprop ("ro.bootlooder") == "T999UVUEMJC" || getprop ("ro.bootlooder") == "T999VVLDLL1" || getprop ("ro.bootlooder") == "T999LUVAMB7" || getprop ("ro.bootlooder") == "T999VVLUEMK5" || getprop ("ro.bootlooder") == "T999LUVUBMK4"
E: Error in /storage/sdcard1/CM-sd/cm-11-20140210-SNAPSHOT-M3-d2tmo.zip (Status 7) Installation aborted.
sandeeppotdar said:
I entered ClockworkMod Recovery v6.0.4.5 and did the following:
1. Wipe data/factory reset
2. Wipe cache partition
3. Mounts and Storage > format /system
4. Mounts and Storage > mount /system
5. Advanced > wipe dalvik cache
5. Install zip: cm-11-20140210-SNAPSHOT-M3-d2tmo.zip
But I get the following error:
assert failed: getprop ("ro.bootlooder") == "T999UVDLJA" || getprop ("ro.bootlooder") == "T999UVDLJC" || getprop ("ro.bootlooder") == "T999UVDMD5" || getprop ("ro.bootlooder") == "T999UVUEMJC" || getprop ("ro.bootlooder") == "T999VVLDLL1" || getprop ("ro.bootlooder") == "T999LUVAMB7" || getprop ("ro.bootlooder") == "T999VVLUEMK5" || getprop ("ro.bootlooder") == "T999LUVUBMK4"
E: Error in /storage/sdcard1/CM-sd/cm-11-20140210-SNAPSHOT-M3-d2tmo.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
You are on the NC2 bootloader. The zip (which by the way is incredibly old...) will not install because you are on that boot loader (because the boot loader version is not in the allowed list). Get the latest CM that is for d2lte and try that. That should work.
GS³: CarbonROM + NeOcOrE™.hYbR!D edition
Put your Kitsune up!
what a fail ....
Just did the automatic install thinking must be easier but ... all I see is just a big fail ... installed all good until at the end remained at that "root access posibily lost ...." Just a waste of time right now ... pretty disappointed in Cyanogen.
How you want to be successful when this released now for a while not working .... going to sleep worked all night
Edit : Basically just factory reset my phone to the same 4.3 update from Samsung get the last CM from where ....
Its not necessarily cm's fault, it happens, you should just put no though when that message appears, it's caused some problems for some people. Get the latest cm from cm's site under d2lte and flash with custom recovery. You can flash custom recovery with Odin, or if you're rooted with an app like flashify
Hope my guide helps you!
ZeRo-c0ol said:
Just did the automatic install thinking must be easier but ... all I see is just a big fail ... installed all good until at the end remained at that "root access posibily lost ...." Just a waste of time right now ... pretty disappointed in Cyanogen.
How you want to be successful when this released now for a while not working .... going to sleep worked all night
Edit : Basically just factory reset my phone to the same 4.3 update from Samsung get the last CM from where ....
Click to expand...
Click to collapse
I've been through this several times past few weeks. Learnt my lessons the hard way! So I just wrote my own Beginner's Guide to Rooting, Flashing & Unrooting. HTH.
P.S. I tried many ROM's for my S3 including CM11, MIUI etc but nothing beats SlimROM's. SlimKat Stable 9.0 (Android 4.4.4) released on Dec 26 is lean, mean, fast & battery efficient yet offers you all the amazing features you expect from a custom ROM Try it and you can come back to thank me with a beer!!

[HELP] Unbricking Kindle Fire 1; stuck in TWRP v2.7.1.0 and can't flash any ROM

Hi XDA,
I have a Kindle Fire gen 1. I had tried to upgrade the OS to 4.x.x. But my KF was so lag, crash and really slow. After that, I installed TWRP 2.7.1.0 to go back to stock rom. But I got stuck in flashing any rom. I had downloaded stock rom from amazon, copied file "update.zip" to sdcard, and flashed it and everytime the result was:
Skipping MD5 check : no MD5 file found
assert failed: getprop("ro.product.device") == "blaze" ||
E :unknown command [err_string]
getprop("ro.build.product") == "blaze"
E :unknown command [err_string]
E :Error executing updater binary in zip ' /sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
I had tried to upgrade twrp to higher version but, whenever i flashed or install anything, the result was the same.
My KF was brick from 2014, today I found it in my closet, and made an effort to bring HIM back to life. Sorry about my terrible English.
Thank you so much.

Categories

Resources