I am trying to flash the RCMIX 2.2 kernel on my IncS, but I always get the following errors:
Code:
assert failed: write_raw_image("/tmp/newboot.img", "boot")
E:Error in /sdcard/RCMIX_VIVO_2.2_OC_1.6_TUN_CIFS_2WCR_EXT4.zip
(Status 7)
Installation aborted.
can anyone help? Do I need to convert my partitions to EXT4?
EDIT: I figured out the original boot.img had to be rooted prior to flashing the kernel... But now my phone becomes unresponsive... Would I need to deodex the operating system so it can successfully rewrite the apks?
Sorry if this sounds sstupid but do u have s-off?
danial.aw said:
Sorry if this sounds sstupid but do u have s-off?
Click to expand...
Click to collapse
Yes, I am S-OFF'ed using the AlphaRevX tool...
charch said:
I am trying to flash the RCMIX 2.2 kernel on my IncS, but I always get the following errors:
Code:
assert failed: write_raw_image("/tmp/newboot.img", "boot")
E:Error in /sdcard/RCMIX_VIVO_2.2_OC_1.6_TUN_CIFS_2WCR_EXT4.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Hi! You need to flash 4EXT Recovery before flashing this kernel! I ran into this situation and this method worked for me, I hope it works for you too. )
Flash the latest EXT4 Recovery from here http://forum.xda-developers.com/showthread.php?t=1104765
After it should work!
Maxesz said:
Hi! You need to flash 4EXT Recovery before flashing this kernel! I ran into this situation and this method worked for me, I hope it works for you too. )
Click to expand...
Click to collapse
Really? OMG I'll try that tomorrow! (Went back to Cyanogenmod since you can't overclock the stock kernel very well, so I have to re-root the Bell Mobile RUU) I will give you thanks if it works.
Hi,
I flashed CF-Root-XX_OXA_JW4-v4.4-CWM3RFS using ODIN and attempted to install CWM using ROM MANAGER but whenever I boot into recovery all I get is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
About phone reveals:
Model number: GT-I9000
Firmware: 2.3.6
Baseband: I9000XXJW4
Kernel version: 2.6.35.7-I9000XXJW4-CL1043937 [email protected] #2
Build number: GINGERBREAD.XXJW4
I have read loads of different posts about fixing this but I do not want to screw up the phone. Can someone please help me before I go mad? I believe that I need a '2e' recovery but where exactly do I get it and install it?
I am not a rookie and had absolutely no problems with my HTC Desire or ZTE Blade but this Samsung is something else.
Cheers guys.
-valerebel
Check my posts in this thread
http://forum.xda-developers.com/showthread.php?t=1995831
Donovan662 said:
Check my posts in this thread
http://forum.xda-developers.com/showthread.php?t=1995831
Click to expand...
Click to collapse
Cheers, but I got there in the end.
My problem was that although I'd flashed the right Kernel with CWM 3, I kept trying to install CWM again from ROM Manager (v2.*.*.*) and this is what was causing the issue. I refashed the Kernel and got into Recovery Mode straight away. I have now installed a Cyanogen JB ROM.
Thanks,
-valerebel
valerebel said:
Hi,
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
-valerebel
Click to expand...
Click to collapse
I just got the above on everything I tried, after flashing "CWM".
Turns out I clicked the wrong link and downloaded a file labelled similarly, but was in fact not CWM recovery but a modified stock recovery.
That said, the CF-AUTOROOT package for my I9500 did work on it... I just had to go into recovery again, right away, and then install SuperSU from the market. I had to flash the proper CWM recovery to get all the other fancy ZIPs to work, such as the pretty Philz touch recovery.
Eureka!! Got answer!
Hi Dude,
I got the solution as I just faced it and came over from it.
The thing is simple. You have been trying to install the update.zip or superSU.zip from your default android recovery. thats y its showing error. That means the custom recovery has not been successfully installed on your mobile. so pls try again then it will surely install.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
The link which i got solution and u should consider it.
http://teamw.in/devices/androidone.html
Hope this helps you dude. let me know if u have any ques.
Thanks all.
Hi guys,
I have a Nexus 7 3G tablet which was running android 4.2.1. I had flashed a custom apk to enable tethering .
Now, to enable flashing, I copied the original framework-res.apk file and replaced the modified one. Then edited the prop file to eliminate the getprop error . This enabled me to start flashing. Flashing happens all the way to the booloader then fails while flashing radio. it gives the following error
Code:
writing radio...
assert failed: batch.update_modem("/radio/SAM_6260_ALL.fls")
Error in JOP40D.zip
(Status 7)
Aborted
any suggestions would be great.
sayantandas said:
Hi guys,
I have a Nexus 7 3G tablet which was running android 4.2.1. I had flashed a custom apk to enable tethering .
Now, to enable flashing, I copied the original framework-res.apk file and replaced the modified one. Then edited the prop file to eliminate the getprop error . This enabled me to start flashing. Flashing happens all the way to the booloader then fails while flashing radio. it gives the following error
Code:
writing radio...
assert failed: batch.update_modem("/radio/SAM_6260_ALL.fls")
Error in JOP40D.zip
(Status 7)
Aborted
any suggestions would be great.
Click to expand...
Click to collapse
Flash stock recovery. Update via sideloading. Profit!
Just in case you are interested in the cause: Current custom recoveries for tilapia are missing the "bach.modem_update" function (not really sure if all of them).
frikisama said:
Flash stock recovery. Update via sideloading. Profit!
Just in case you are interested in the cause: Current custom recoveries for tilapia are missing the "bach.modem_update" function (not really sure if all of them).
Click to expand...
Click to collapse
if i flash stock recovery, i will lose all my data. any other possible solution, which would enable me to keep my data?
sayantandas said:
if i flash stock recovery, i will lose all my data. any other possible solution, which would enable me to keep my data?
Click to expand...
Click to collapse
No, you won't. I said stock RECOVERY, not stock IMAGE.
Code:
fastboot flash recovery stockrecoverysname.img
OK. So could you give me a link to download the recovery image ?
Sent from my Nexus 4 using xda app-developers app
Do you have the original factory image from google? The recovery.img is inside,
if not i will upload it somewhere, though it doesn't fixed the radio update error for me.
I now have a mixed version > the ota update installed without errors, the bootloader is 4.18 but
in settings it complains to still be at 4.2.1 JOP40D
Flashing the stock recovery only leads to an unusable recovery screen with no options for flash/sideload
with an red exclamation mark over the chest of the sweet robot..
any ideas?
maybe i have to reflash my nandroid and try again, the custom recovery was openrecovery-twrp-2.4.1.0-tilapia
here are the images for those who need them
nakasig-jop40d-factory-efcec044.tgz
http://www.share-online.biz/dl/0OWHBFIMLC
recovery.img
http://www.share-online.biz/dl/LM9JBFIMKSG8
EDIT:
Ok finally i was able to use the stock recovery. though it seemed to be dead.
By pressing power+volup showed the recovery menu for me.
Then flashing the update via sideload worked.
cheers phk
hi whenever i try to install cm 10.1 nightly any version i get following errors.
-- Installing: /external_sd/cm-10.1-20130423-NIGHTLY-p880.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880"
E:Error in /external_sd/cm-10.1-20130423-NIGHTLY-p880.zip
(Status 7)
Installation aborted
i have tried to wipe data, catche and dalvik cache, and also tried after formating system, but same error every time.
can anyone tell me why i get this error and it's solution please?
i'm on official v20a, rooted, unlocked bootloader with clockworkmod recovery 6.0.3.1 installed through rom manager,
The problem is your recovery, if you install official clockworkmod via ROM manager or from the website it will work. The problem is in cm10.1 our device is labeled as "x3" instead of "p880", this is another ID for our device but some recoveries don't like it. Its also this ID in the build.prop that makes some games show up in Google play that shouldn't, saw my old Gameloft games like backstab, tried installing but I got "your device is not compatible, please request a refund"
Sent from my rooted P880
Mr.LOVER said:
hi whenever i try to install cm 10.1 nightly any version i get following errors.
-- Installing: /external_sd/cm-10.1-20130423-NIGHTLY-p880.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880"
E:Error in /external_sd/cm-10.1-20130423-NIGHTLY-p880.zip
(Status 7)
Installation aborted
i have tried to wipe data, catche and dalvik cache, and also tried after formating system, but same error every time.
can anyone tell me why i get this error and it's solution please?
i'm on official v20a, rooted, unlocked bootloader with clockworkmod recovery 6.0.3.1 installed through rom manager,
Click to expand...
Click to collapse
Friend, I had the same problem.
Solution: Update your CMW. After upgrade, try installing the latest version.
Here it worked.
allanlinux said:
Friend, I had the same problem.
Solution: Update your CMW. After upgrade, try installing the latest version.
Here it worked.
Click to expand...
Click to collapse
i already have the latest version of CWM, i flashed it through rom manager.
before i did this, i also tried to install the CWM recovery by dexter and that also didn't work for me.
Mr.LOVER said:
i already have the latest version of CWM, i flashed it through rom manager.
before i did this, i also tried to install the CWM recovery by dexter and that also didn't work for me.
Click to expand...
Click to collapse
Strange, this shouldn't be happening and isn't for anyone else as far as I know. I think there was a fix so this could be flashed on any recovery somewhere, search the general section and try that
Sent from my rooted P880
were nsaidec
Mr.LOVER said:
i already have the latest version of CWM, i flashed it through rom manager.
before i did this, i also tried to install the CWM recovery by dexter and that also didn't work for me.
Click to expand...
Click to collapse
Ok, this is not normal as our friend said.
Try installing a new CWM for this program: https://play.google.com/store/apps/...xLDEsImNvbS5rb3VzaGlrZHV0dGEucm9tbWFuYWdlciJd
I say this because I installed my version of this app and funcinou the CM10.
Take the test and tell me if it worked
Step 1.Open the ROM.zip with winrar
Step 2.Found \META-INF\com\google\android\updater-script ,use Notepad open
Step 3.delete assert(getprop("ro.product.device") == "p880" ||
getprop("ro.build.product") == "p880");
Step 4.OK,safe
--------------------------------------------------------------------------------------------------------------------------
Another method
installing a new CWM ，thx
I just installed the latest CWM and it worked fornme. I was also stuck on that error after installing CWM using the root/bootloader/cwm and so on tool, i forgot the name. Then i figured out that the CWM was the problem so i downloaded the latest .img from CWM website (not touch version) and replaced the .img in the tool's folder with the new one i downloaded. Replace meaning deleting the old one and placing the new one in their with the same name. Hope this helps, sorry for my bad english.
Edit: The tool is the one in here: http://forum.xda-developers.com/showthread.php?t=2230934 and replaced the CWM .img with version 3.0.3.1 instead of 3.0.2.8
Sent from my LG-P880 using xda app-developers app
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-p880.img
You can download touch version 6.0.3.1. You can install like Dexter way or change the name O4X_CWM.img and put it in ALL IN ONE TOOL inside /files folder.
I had the same problem before using mickey.outcast method. Everything is fine now, except wifi doesn't connect
Hansey said:
Step 1.Open the ROM.zip with winrar
Step 2.Found \META-INF\com\google\android\updater-script ,use Notepad open
Step 3.delete assert(getprop("ro.product.device") == "p880" ||
getprop("ro.build.product") == "p880");
Step 4.OK,safe
--------------------------------------------------------------------------------------------------------------------------
Another method
installing a new CWM ，thx
Click to expand...
Click to collapse
Thanks a lot, now i can flash cyanogenMod, but after flashing, there's an error that said "[LGE_SECURITY] ERROR: boot image signature Critical failure: Unable to start kernel. Unrecoverable boot loader error (0x00000002).".
I try with several roms and builds but nothing works!
milerx said:
Thanks a lot, now i can flash cyanogenMod, but after flashing, there's an error that said "[LGE_SECURITY] ERROR: boot image signature Critical failure: Unable to start kernel. Unrecoverable boot loader error (0x00000002).".
I try with several roms and builds but nothing works!
Click to expand...
Click to collapse
installing a new CWM 6.0.3.1 ，
Hansey said:
installing a new CWM 6.0.3.1 ，
Click to expand...
Click to collapse
Hi,
I try to install a new recovery but I fail to succeed, I try with the toolkit and with the rom manager and also fails, I don't know what to do
milerx said:
Hi,
I try to install a new recovery but I fail to succeed, I try with the toolkit and with the rom manager and also fails, I don't know what to do
Click to expand...
Click to collapse
You need
→ wipe data/factory reset → YES*
→wipe cache→ YES-*
try
milerx said:
Hi,
I try to install a new recovery but I fail to succeed, I try with the toolkit and with the rom manager and also fails, I don't know what to do
Click to expand...
Click to collapse
is your bootloader even unlocked?
Did you get it to work?
milerx said:
Thanks a lot, now i can flash cyanogenMod, but after flashing, there's an error that said "[LGE_SECURITY] ERROR: boot image signature Critical failure: Unable to start kernel. Unrecoverable boot loader error (0x00000002).".
I try with several roms and builds but nothing works!
Click to expand...
Click to collapse
I got the same problem, this is what i did to fix it, (sorry if this is already solved)
I got the same error code you did.
I used Lg´s mobile support tool to just restore my O4X (bootloader will still be unlocked) and if it isn't there will be a message displaying that i the upper left corner.
Then i re-rooted using All in one tool kit.
NOT FLASHING CWM via All in one.
In the Superuser app i updated my binery file.
Downloaded the rom manager from store
Install rom manager and install the latest CWM (Not the touch version)
Boot recovery
Wipe/data factory reset
Wipe cache partition
Wipe dalvik cache
format system
I actually put the rom on my internal sd card, same whit the Gapps.
Install rom
Install gapps
Works for me problemfree :good:
Im kind of new to this but this solved the problem.
Hope this might help you.
Hey guys, I've been getting the 'assert failed getprop' error.
I replaced the files of the rom and tried flashing again - no luck
Updated CWM, and tried flashing again, still no
Tried flashing an appropriate kernel and then flashing the rom, same error
I tried wiping everything in between and also not wiping, but it didn't help
I've got the Wilfire S Marvelc, the rom i'm trying to flash is cm10 (tried several versions for that might work, the marvelc version doesn't even make it through the install)
It's unlocked, rooted, and with CWM installed.
Can anybody help? I'd immensely appreciate it!
lightstryk said:
Hey guys, I've been getting the 'assert failed getprop' error.
I replaced the files of the rom and tried flashing again - no luck
Updated CWM, and tried flashing again, still no
Tried flashing an appropriate kernel and then flashing the rom, same error
I tried wiping everything in between and also not wiping, but it didn't help
I've got the Wilfire S Marvelc, the rom i'm trying to flash is cm10 (tried several versions for that might work, the marvelc version doesn't even make it through the install)
It's unlocked, rooted, and with CWM installed.
Can anybody help? I'd immensely appreciate it!
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You've got a HTC Wildfire S? This is the LG Optimus 4X HD forum
Lol, well I was hoping you might have a suggestion anyways because it's a common error, but alright o.o
lightstryk said:
Lol, well I was hoping you might have a suggestion anyways because it's a common error, but alright o.o
Click to expand...
Click to collapse
Yeah, it's hugely common on our device - only because people don't read the instructions and keep using the wrong version of CWM.
I have a 4x hd, rooted, and unlocked. I used all_in_one tool to flash TWRP(*wrong#2). I wiped everything on the phone(*wrong#2) and when i tried to flash the rom, in twrp i cant even see the sdcard. In cwm inside TWRP says:
assert failed :getprop("ro.`product.devide") == p880 getprop("ro.build.product.device"= ==p880
E : error in /external_Sd/rom.zip
(status 7 )
it sems i flashed the wrong recovery, i cant get into android recovery center, only in TWRP. How can i fix it, please??? TWRP has a terminal and a adb sideload??
Please, help me restore my phone.
Thank you so much
(maybe LG-KDZ-UPDATE-TOOLS, ????)
http://bit.ly/11yDGM4
TRY THIS
hi I got my phone stuck in bootloop after flashing a bad recovery file.. so I had to flash original fireware through kdz tool and it worked have a look at this link
http://forum.xda-developers.com/showthread.php?t=2069723
phone saved!!
Hursty uk said:
hi I got my phone stuck in bootloop after flashing a bad recovery file.. so I had to flash original fireware through kdz tool and it worked have a look at this link
http://forum.xda-developers.com/showthread.php?t=2069723
Click to expand...
Click to collapse
thanks, it worked, thanks a lot. You guys are awesome!!!!! have my stock room again, !!!
reyner0 said:
thanks, it worked, thanks a lot. You guys are awesome!!!!! have my stock room again, !!!
Click to expand...
Click to collapse
glad it worked mate
you need to delete the first line in the updater script using any text editor to install the zip without errors.
meta-inf ->google->android->updater-script
I think it would be easier to just flash CWM 6.0.3.1.