"Device halted due to Large Image update failure. Press <POWER> to reboot"
*Help*
I tried to flash via sdcard a firmware (lollipop) for a51_tuhl that i found online. I recieve this error msg after both the blue bar and the red bars in hboot finish loading I recieve this
Parsing
Device halted due to Large Image update failure. Press <POWER> to reboot
Hboot also displays msg *System update failure* however i manageds after several reboot to boot system by removing external sd and then selecting check smart sd and that option booted system.
Does anyone know why this error has occured ?
Related
Good afternoon,
I am having serious trouble trying to install my FOTA from Orange (1.84.xx.x) and with little knowledge available on it, I'm trying to break it down piece by piece.
The phone works fine at the moment with the 1.40.xx.x Firmware on it but I do want to install the update.
I can load in to the bootloader no problem but when I do it hangs for a few seconds before a screen appears saying that it has tried to check PD98IMG.zip but it can't be found. It then says it can't find various connotations of that such as PD98xxx.nbh. Is this an issue?
Would not finding these files result in the phone hanging when I try to put it in Recovery mode? I have the FOTA file on the SD card (in the Download folder where it was downloaded to) and wa hoping that clicking Recovery would boot the FOTA file. It doesn't. The system hangs until I either take the battery out or....
.... I press Vol UP (3 seconds) and tap the Power button. This takes me to a new screen with blue writing (Android system Recovery 3e) that gives me the option to either Boot, Apply sdcard:update.zip, Wipe data/factory reset, Wipe cache partition.
I also have yellow writing on the screen with the message, "E:Can't open /cache/recovery/command". I can only assume that this is quite important - what is wrong?
As for the update.zip, what is it? Should I rename the FOTA file as update.zip? where should it be put on the SD card to make it available to the Recovery menu?
Many thanks in advance,
AC
Hey did you ever get this fixed? I'm having the same issues. hit me up @ [email protected] please.
Hello everyone, i'm new to this forum and i hope anyone can help me. I recently received a Nubia z7 mini. It's an awesome phone! However just tonight i tried to upgrade using the OTA option. When my phone rebooted into the Nubia v1.0 recovery it kept displaying this message:
E: footer error
E: signature verification failure
operation aborted
The phone then rebooted.
I then searched for other ways of updating and this is where i went wrong. I downloaded the latest official update, placed it on my phones external SD and tried to install using flashify. Since the search for zip file option didn't load properly i clicked on 'boot image' (really didn't know what i was doing there). It then loaded the zip file, and asked for my okay. I then rebooted and the phone didn't start anymore, it's just stuck at the Nubia logo. I can get it into recovery mode (Nubia recovery 1.0) but if i try to flash a new rom i keep getting the above errors (footer error and signature verification error).
My phone is not being recognized by windows right now so i cant flash with odin.
Is there a way to fix this phone ?
Many thanks in advance!
Afross said:
Hello everyone, i'm new to this forum and i hope anyone can help me. I recently received a Nubia z7 mini. It's an awesome phone! However just tonight i tried to upgrade using the OTA option. When my phone rebooted into the Nubia v1.0 recovery it kept displaying this message:
E: footer error
E: signature verification failure
operation aborted
The phone then rebooted.
I then searched for other ways of updating and this is where i went wrong. I downloaded the latest official update, placed it on my phones external SD and tried to install using flashify. Since the search for zip file option didn't load properly i clicked on 'boot image' (really didn't know what i was doing there). It then loaded the zip file, and asked for my okay. I then rebooted and the phone didn't start anymore, it's just stuck at the Nubia logo. I can get it into recovery mode (Nubia recovery 1.0) but if i try to flash a new rom i keep getting the above errors (footer error and signature verification error).
My phone is not being recognized by windows right now so i cant flash with odin.
Is there a way to fix this phone ?
Many thanks in advance!
Click to expand...
Click to collapse
Well, I can inform that you do need a custom recovery on that phone in order to flash a custom ROM... Or it wont work. But i dont have that phone, you can try this.
1.copy ****.zip to root folder of the phone SD card (no need to unzip).
2.Turn off the phone, then keep pressing power button and volume+ button until the robot icon appear, then press power button again and it will show as below
3.Press the volume- to move up and down to choose“wipe data/factory reset”, then press volume+ button to confirm.
4.Choose “yes—delete all user data”, then press volume+ button to enter the page as below.
5.It will enter below page after finishing delete all user data.
6.Then choose“apply update from sdcard”
7.Find and select the ROM, press volume+ to enter the page as below.
8.Please make sure the power is sufficient during the upgrading. It will showed as below when the upgrading finished.
9.Choose “reboot system now”,then press volume+ button to reboot your phone.
Also, Are you rooted?
Regards,
Exxo
Exxoriscism said:
Well, I can inform that you do need a custom recovery on that phone in order to flash a custom ROM... Or it wont work. But i dont have that phone, you can try this.
1.copy ****.zip to root folder of the phone SD card (no need to unzip).
2.Turn off the phone, then keep pressing power button and volume+ button until the robot icon appear, then press power button again and it will show as below
3.Press the volume- to move up and down to choose“wipe data/factory reset”, then press volume+ button to confirm.
4.Choose “yes—delete all user data”, then press volume+ button to enter the page as below.
5.It will enter below page after finishing delete all user data.
6.Then choose“apply update from sdcard”
7.Find and select the ROM, press volume+ to enter the page as below.
8.Please make sure the power is sufficient during the upgrading. It will showed as below when the upgrading finished.
9.Choose “reboot system now”,then press volume+ button to reboot your phone.
Also, Are you rooted?
Regards,
Exxo
Click to expand...
Click to collapse
Hi Exxo,
Thanks for your reply. Yes, i am rooted
Now in step 1 what do you mean with ***.zip. Is that supposed to a zipfile to change the recovery?
i tried downloading and flashing Clockworkmod Touch Recovery 6.0.4.3 CWM (downloaded from here: http://forum.xda-developers.com/showthread.php?t=2531628).
However it is giving me the following error:
Finding update pakacge
Opening update package
Verifying update package
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
anyone?
Up until yesterday I had a great little HTC Desire HD, A9191 with rooted gingerbread 2.3.5, an unlocked bootloader (from htcdev), S-ON - and everything in my garden was rosy... Then I tried to get too clever and pushed a new hosts file to /system/etc while I had su privileges.
This was a big file (540K) which I had been using quite happily on Windows to keep adware at bay. However, I now think it caused the phone to fail because the first time I tried to boot up after the push, it started looping round the boot sequence indefinitely. I am wondering if the IP for localhost, being 127.0.0.1, is incompatible with linux...? Anyway, that's a job for tomorrow because before I can think about draining the swamp there are some "alligators" to deal with...
While this continuous re-booting was going on I found I could still do "adb shell" and run "su" but all my attempts to restore hosts to the original file were futile because at this point the file system was "read-only" even for root. Then I made my biggest error which was to attempt "RECOVERY" from the boot menu...... ( I think my previous attempt to create a recovery file failed and I must have just forgotten to attend to it.)
The boot loader still responds and I am now looking at the boot screen which says:
=============================================
*** UNLOCKED ***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M (this is the original factory-shipped version for my phone)
eMMC-boot
Dec 22 2011, 14:28:19
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
==============================================
Here's what happens with these various options:
1. Normal boot ends with "Sorry! Process system is not responding" and two buttons "Force close" and "Wait" - but in reality the phone is simply hung...
2. FASTBOOT ends with a phone gif and a red triangle / exclamation mark.
3. RECOVERY also ends with a phone gif and a red triangle / exclamation mark.
4. FACTORY RESET runs a black/white barber pole and sd card symbol for 2 minutes, then reboots as far as "quietly brilliant" but this then ends up the same as 1. above.
5. SIMLOCK produces this output:
FAT32 init OK
Open MCCMNC file fail
Open CID file fail
Process done, reboot device?
<VOL UP> Yes
6. IMAGE CRC produces this output:
osbl: 0x3AA5FD29
amss: 0xD791CCA8
hboot: 0xFB10D632
boot: 0x8446CCFD
recovery: 0x0x88F60913
system: 0x898C2200
When I put an sd card in the slot and press and hold the power button with HBOOT highlighted it produces this:
SD checking...
Loading...[PD98DIAG.zip]
No image!
Loading...[PD98DIAG.nbh]
No image or wrong image!
Loading...[PD98IMG.zip]
No image!
Loading...[PD98IMG.nbh
No image or wrong image!
So am I right in thinking that it's not quite dead yet and still recoverable? I have made a few attempts to position ROM files in the root of the sd card, but so far without success.
Could someone please tell me (assuming it's not bricked yet) what file(s) I need to put on the sd card to stand any chance of recovering. Previously I had downloaded the nearest "stock rom" to the phone's original but this came as a .exe which just compounded my confusion as to what needs to be done.
Here's hoping...
Happy New Year to all.
Having some problem giogke play store.
I download the latest jellytime 4.3 and cw Google app 4.3 as well. Everything works just finebut keep trying to download ssomething's from Google play store by using WiFi but it just don't work, am I missing something? I can search anything in play store, but hen I try to download it, it just won't run. Please give me some advice, thanks a lot.
One time, when I tried an update an error occured, the phone reboot and said: "the device has been reported to the initial configuration". Now there is no notification to update. I have to do it manually.
What is the problem ?
i did a factory reset but it doesn't prompt me again if i want to update.
I did this tuto: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=14962 to receive OTA
but nothing changes and i'm now onto 2.20.40.97 but each time i have to update manually.
And now when i go into recovery it show me: "installing system update..." and few seconds later it show me error (with the android logo)..
Can you help me ?
up please help me.
I succeed to (re) update to .97 with recovery: i put the firmware onto sd and internal root storage named mofd_sdupdate.zip and it update BUT I don't know if i can receive updtaes notifications...
That error logo is not a problem as long as the device wasn't updating. Also, I never received any notifications for OTA except once.
Hi,
I had previously rooted my device: Android 1 - Micromax Canvas A1. I also had installed CWM on my device. For some reason, I have removed recovery mode and unrooted my device. My device had Marshmallow with February patch.
But whenever I try to get OTA it doesn't get succesfull. Whenever I try to go into recovery mode it shows my dead android with warning sign saying "No command!". When I try to press "Power Key + Volume UP" I get error message saying "Error in @/cache/recovery/block.map (status 7)".
Reading few posts, I understood that some system files got corrupted and I won't get OTA updates. So downloaded one Zip files and I flashed all the *.img files (recovery, system, boot, etc). Now my system had Android 5.1. But I'm getting same error while going into recovery mode.
I also tried to use "Smart Phone Flash Tool " but whenever I click "Download button" it stucks in the same state showing no progress.
I have read many posts and tried many things but I'm stuck at this stage. Can anybody help me out of this problem?
Update: Though I wasn't able to get into recovery mode directly. I (major) updated my device from KitKat to Marshmallow. Then, minor updates also went fine. Now, I'm on latest April 2016 update. Still, when I try to get into recovery mode, I still see "No Command". But after pressing Volume Up + Power button I get the recovery option. Is this default behavior.
ghsatpute said:
Hi,
I had previously rooted my device: Android 1 - Micromax Canvas A1. I also had installed CWM on my device. For some reason, I have removed recovery mode and unrooted my device. My device had Marshmallow with February patch.
But whenever I try to get OTA it doesn't get succesfull. Whenever I try to go into recovery mode it shows my dead android with warning sign saying "No command!". When I try to press "Power Key + Volume UP" I get error message saying "Error in @/cache/recovery/block.map (status 7)".
Reading few posts, I understood that some system files got corrupted and I won't get OTA updates. So downloaded one Zip files and I flashed all the *.img files (recovery, system, boot, etc). Now my system had Android 5.1. But I'm getting same error while going into recovery mode.
I also tried to use "Smart Phone Flash Tool " but whenever I click "Download button" it stucks in the same state showing no progress.
I have read many posts and tried many things but I'm stuck at this stage. Can anybody help me out of this problem?
Update: Though I wasn't able to get into recovery mode directly. I (major) updated my device from KitKat to Marshmallow. Then, minor updates also went fine. Now, I'm on latest April 2016 update. Still, when I try to get into recovery mode, I still see "No Command". But after pressing Volume Up + Power button I get the recovery option. Is this default behavior.
Click to expand...
Click to collapse
What is your current build Number??
Sent from my Micromax AQ4501 using XDA-Developers mobile app
Too long to read full story