Hey guys I'm having trouble updating my HTC desire. IM currently running 1.13 and when i click on HTC software update it'll bring up 1.50 and start downloading. Well after it's done downloading I click on install and it restarts my phone and starts installing. Well about %20 of the way on the progress bar the logo changes on the screen and shows a red phone with a triangle in the middle with an exclamation mark. Well i tried restarting the phone and I even went into recovery and tried clearing the cache. Well that didn't work so i decided to go into recovery from the installation screen and it showed an error that said something about assert failed /system/build.prop does anybody have any idea why this is happening? My phone isn't rooted or anything.
This is the full error message:
assert failed: file_getprop("/system/build.prop", "ro.aa.taskid") == "385463" || file_getprop ("/system/build.prop", "ro.aa.taskid") == "398306"
Installation aborted.
Write host_mode:0 done
might be
It may be a corrupted download I am not 100% sure what directory it downloads it to but you will need to find and delete it and try redownloading
What Phone Model (a5) do you have????
oakleyguy89 said:
Hey guys I'm having trouble updating my HTC desire. IM currently running 1.13 and when i click on HTC software update it'll bring up 1.50 and start downloading. Well after it's done downloading I click on install and it restarts my phone and starts installing. Well about %20 of the way on the progress bar the logo changes on the screen and shows a red phone with a triangle in the middle with an exclamation mark. Well i tried restarting the phone and I even went into recovery and tried clearing the cache. Well that didn't work so i decided to go into recovery from the installation screen and it showed an error that said something about assert failed /system/build.prop does anybody have any idea why this is happening? My phone isn't rooted or anything.
Click to expand...
Click to collapse
I had the same issue on Virgin Mobile USA a5_CHL. go here. http://forum.xda-developers.com/desire-816/general/ruu-t2952058 . Worked for me. Connected my phone with a USB, Flashed the stock recovery with fastboot. rebooted the phone and ran the RUU.exe on my PC. a5_CHL ONLY...
I have the a5 chl. Iended up manually installing which in turn did a data wipe. I Then got upset and decided to just root it and all that jazz.
Related
i followed the instruckions here to root my Evo
http://forum.xda-developers.com/showthread.php?t=838448.
When i get to step 5. I get a few errors but i continue as it says. When I finally get into recovery..(black background with green wording) i make my nandriod backup. (which now i find out didnt work) Then i go and do a full wipe. when i go to flash my rom it goes all the way through and errors out at the end. this is the error i get:
assert failed: write_rawimage("/tmp/boot.img","boot:
E:Error on /sdcard/fresh-evo-3.5.0.1.zip
(status 7)
Installation aborted
if i turn on the phone it stays at the scrren with the red triangle on it.
I really dont care about root at this point i just want to get it back up and running. can anyone help?
Thanks,
Try here http://forum.xda-developers.com/showthread.php?t=829045
I assume you got a new Evo?
Yes got it yesterday. tried to root and it failed. Im sorry but how does this help..I just want to get back to factory at this point. root is the least of my worries.
Desire bought from eBay. No branding at boot.
Came with 2.29.405.2 and OTA .5 is available on aiutomatic check.
Starts to work then after 1/4 green progress bar fails with £Error in /sdcard/download/OTA..... (Status 7) and leaves me at Warning triangle.
Tried factory reset.
Tried formating SD
Tried different SD.
Checked archive on laptop.
Why is this happening - perhaps a dodgy ROM image on the phone?
Pointers most welcome....
Thanks
You could just use an ruu instead. Will wipe and correct everything
Sent from CM7
I agree - RUU it would probably be best
http://forum.xda-developers.com/showthread.php?t=869048
Ok, this is my first post so forgive if this is in the wrong section...
I have a friend's Galaxy Note 2 ATT that was stuck on the Galaxy Note 2 Boot screen, and it wouldn't go any further.
Because I work for Samsung at the Samsung Experience Shop, I tried running it through our smart reflash tool
-----> This didn't work because it would fully download it onto the phone, but when it got to the Android with the thing spinning in its chest, it would stop and ALWAYS freeze halfway.
Next step I tried doing was going through Samsung Kies and downloading the stock OS and load that, but the same Android with the spinning thing in its chest would show up and it would freeze.
Due to this guy being my friend I told him I would try anything to get his phone to work again (root, to custom recovery, to custom rom)
My steps so far:
1. I have successfully rooted my device via ODIN 1.85 by using CF-Auto-Root
2. Afterwards, I loaded on a custom recovery via ODIN 1.85 which now is philz_touch_6.07.9
Here is my problem now, I've tried searching everywhere and I can't really find the answer...
Whenever I try to side load a rom through ADB through Android tools (its in the right directory and everything because it transfers over), I keep getting an error message "E: Error in /tmp/update.zip (status 7) Installation Aborted."
Now before I get that error I get stuff like getprop("ro.product.device")==t0lte" ||getprop("ro.build.product").... etc. and it goes on and on.
So far the ROMs that I have tried were Cyanogenmod 10.1 and the Pacman Rom, and yes, both are for the correct device like the model name/number match up. And now how I said I thought I rooted the device, whenever I try to reboot into recovery via Philztouch, it says at the top Root Access is missing. Root device, and I click yes. When it reboots into recovery and I want to turn the phone off again, it still says Root Access is missing.
I am open for anything really. My friend just wants his phone to work again. and I've literally exhausted all of my ideas as I keep running into the same issue.
What am I doing wrong? and is something like this possible to fix? Or is my friend SOL?
Thanks for all the help. It's much appreciated.
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
rangercaptain said:
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
Click to expand...
Click to collapse
+1 to this^^^^^
Look here»»» http://forum.xda-developers.com/showthread.php?t=1981198
And why not give him something stock instead of a CM Rom??[emoji37]
Plenty of stock 4.3 Rom's in the development section...
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Good advice ^^^^ for your friend.
Ok, thanks for the direct response. I've downloaded the latest TWRP recovery and when I try to push it through ODIN, I still have PhilZ Touch 6..? Sorry, I feel like I'm skipping something simple...
according to a guide, I have to make sure when I'm pushing a custom recovery through ODIN I have to leave Auto Reboot and F. Reset Time UNCHECKED. I made sure they were, and for some reason after it says PASS and thread successful 1 failed 0. When I disconnect the phone and turn it back on into recovery mode, I still has PhilZ Touch...
Use your recovery to flash TWRP. There's a zip version and an odin version.
Ok, I got stock recovery on there just by redoing the CF-Auto Root package through ODIN.
I figured well I can apply the ROM the adb through the stock recovery...
It was going well until I got this error. The last line before the error stated:
"Veryfying update package..."
Error:
E: failed to verify whole-file signature
E: signature verification failed
is that due to the fact that i'm using stock recovery?
In the mean time since that didn't work I'm going to flash TWRP and hopefully that fixes the issue.
I'm kinda just documenting my steps here in case anyone wants to follow and chime in if i'm doing something wrong.
Thanks for the help guys!
************3AM EDIT*****************
Ok so I managed to get TWRP 2.7 on the device as I needed the ability to adb sideload the update.zip to the phone since I can't boot into the phone's OS whatsoever.
This is the error I'm receiving now:
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
then it restarts and I'm stuck at the Samsung GALAXY Note II screen... what's my next step..? Find a different ROM?
**********Another Edit**************
It has just come to me, I shouldn't have to adb sideload the update.zip or the custom rom... even though I can't get into the phones OS and can't copy and paste to the root of the device. Can't I just copy and paste it to a micro SD card and mount that, and then apply the update from there? And as far as those errors I had earlier, I'm still not sure why I received them...
Again, thanks for all the help
Adb won't work if USB debugging wasn't enabled.
In TWRP you can disable md5 checking.
And you don't unzip the zip file.
Thanks for the reply. ADB didn't work because, in fact, since I haven't been able to turn the phone on, I know USB debugging isn't turned on.
And as far as having the MD5 check, it is unchecked.
I received a success message. However, when I try to boot the phone it still gets stuck at the Samsung Galaxy Note II screen.
******Edit******
Ok ended up using a different ROM, I think PacMan rom? It seemed to work until it got to extracting system files and then the phone sits for a couple minutes, screen turns black. And when I try to wake the screen, only the back and menu buttons come up...
Another thing, even though I've already rooted my device using CF-Auto-Root, When I reboot my device with TWRP I go to reboot and then recovery. Then it warns me saying no OS bla bla bla, and then it says it notices that my phone isn't rooted? And that SuperSU isn't on the device. It asks to install it by swiping. I swipe it starts to install, phone reboots. When I reboot it again, it still tells me that the phone isn't rooted. And with the phone not being rooted, I'm coming to the conclusion why I'm having trouble trying to flash Roms.. Is this a possibility?
Why are you using ADB? just drop the .zip for the ROM you wish to flash onto a micro SD card, and flash from within the TWRP. Don't try to extract the .zip whatsoever.
Hello! Im using HTC M8, yesterday i decided to root it so I used this guide to do bootloader activation, flashing recovery and rooting it (h t t p :/ / theunlockr.com/2014/04/19/root-htc-one-m8-all-in-one-toolkit-method-video/).
Everything was fine till i done everything and started my phone. I tried to run Supersu, and i got message that Supersu binary is not installed, i tryed to update it from googleplay, but nothing. Than i decided to flash updated version found on internet, now i get strange things like, x application failed to run , report this to HTC, my phone storage is not recognized or shown in any file menager or when i connect it to pc, i cant download anything from chrome, to my phone... Help please. What to do?
I tryed factory reset, reflashing recovery, but nothing happend. I have plan to instal newest version of super su but i cant put it in phone root to instal it from recovery boot...
Somebody?! Anything?
Hello friends,
My HTC M9 is acting weird.It reboots endlessly whenever I connect to any Wi-Fi.There is no problem when
Wi-Fi is off.
Recently this problem has stretched to the mobile data connection also.Therefore now I can't use Wi-Fi and data so that the phone won't start rebooting.
Please help.
Is the phone rooted etc, we need more info. Do you remember when it started doing it?.
If the phone is running a stock rom and firmware you can try factory test mode by calling *#*#3424#*#*.
Beamed in by telepathy.
shivadow said:
Is the phone rooted etc, we need more info. Do you remember when it started doing it?.
If the phone is running a stock rom and firmware you can try factory test mode by calling *#*#3424#*#*.
Beamed in by telepathy.
Click to expand...
Click to collapse
The phone is not rooted.Running stock Android 6.0
The problem started when I rebooted the device because the playstore updates where failing.
On that reboot,the phone was stuck on HTC One splash screen.So I pressed power,vol up & down to restart.Then it booted up.
When my Wi-Fi connection came up the phone started rebooting which is where the problem started.I tried a factory reset and it doubled the problem affecting data connection also.
Most times when I factory reset or reboot it will be stuck at HTC One splash screen and I will have to restart again.
The device model is OPJA100
[email protected] said:
The phone is not rooted.Running stock Android 6.0
The problem started when I rebooted the device because the playstore updates where failing.
On that reboot,the phone was stuck on HTC One splash screen.So I pressed power,vol up & down to restart.Then it booted up.
When my Wi-Fi connection came up the phone started rebooting which is where the problem started.I tried a factory reset and it doubled the problem affecting data connection also.
Most times when I factory reset or reboot it will be stuck at HTC One splash screen and I will have to restart again.
The device model is OPJA100
Click to expand...
Click to collapse
Try use ruu.
leos0000 said:
Try use ruu.
Click to expand...
Click to collapse
I have downloaded ruu file for unlocked/developer version from htc website.
Will try to install today and will give an update.
[email protected] said:
I have downloaded ruu file for unlocked/developer version from htc website.
Will try to install today and will give an update.
Click to expand...
Click to collapse
Tried to install ruu.The Update utility proceeded until final step where it tells "It may take 10 mins to update your device".
The small window came up and phone rebooted to bootloader...deleted user data...and then a window came up saying update failed.The phone rebooted and now freezes at HTC One splash screen(Tried another reset but nothing).
What maybe the problem..is it because i'm having wrong ruu?
I am from India and here we don't use carrier devices.(The phones are not locked to any carrier.)
Note : I did not install HTC Sync Manager.Just enabled usb debugging in device settings.
what does it say in the update fail pop up? any error #?
side_flip15 said:
what does it say in the update fail pop up? any error #?
Click to expand...
Click to collapse
The error code is 132 signarure error.
Update : I left the phone which was freezed showing HTC One splash screen and it turned off after the battery run out.
Now I plugged it in and powered on and the phone completed the boot and came to homescreen.
The problem is still there though.
So tried unlocking the bootloader and installing a custom rom and voila...the problem is now solved.
So I guess it was a software issue after all.
Didn't get as many replies as I expected but thanks everyone.