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.
Related
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 there
I tried to get a recovery on my phone with this http://forum.xda-developers.com/showthread.php?t=2030777 app.
I pressed the first option ( so Install recovery), then it said something like "flashing succesfull" , so I tried to boot into recovery.
That didn´t work, though, I only got into the preinstalled android recovery, not TWRP.
So I tried to reboot my phone, but ended up in a boot loop...
Any ideas how to solve that?
Thanks in advance,
Metlca
metlca said:
Hi there
I tried to get a recovery on my phone with this http://forum.xda-developers.com/showthread.php?t=2030777 app.
I pressed the first option ( so Install recovery), then it said something like "flashing succesfull" , so I tried to boot into recovery.
That didn´t work, though, I only got into the preinstalled android recovery, not TWRP.
So I tried to reboot my phone, but ended up in a boot loop...
Any ideas how to solve that?
Thanks in advance,
Metlca
Click to expand...
Click to collapse
Hi
Try to follow this tutorial to see if it works http://forum.xda-developers.com/showthread.php?t=2069723
You can then try to flash this recovery http://forum.xda-developers.com/showthread.php?t=2180138
metlca said:
Hi there
I tried to get a recovery on my phone with this http://forum.xda-developers.com/showthread.php?t=2030777 app.
Click to expand...
Click to collapse
Don't use TWRP. CWM is 100x better and actually works - plus you will find it far easier to get support on here.
tyraek said:
Hi
Try to follow this tutorial to see if it works http://forum.xda-developers.com/showthread.php?t=2069723
You can then try to flash this recovery http://forum.xda-developers.com/showthread.php?t=2180138
Click to expand...
Click to collapse
Thanks a lot, everything´s working again
But there´s another problem now..
I tried to flash cm10.1 with my new cwm recovery, but I get the error
"assert failed: getprop ("ro.product.device") =="p880"
getprop "ro.build.product") == "p880"
E:error in /sdcard/cm-10.1.2-p880.zip (Status 7)
Installation aborted"
Now what does that mean?.....
Thanks a lot
Edit:
Tried with other cm 10.1 based rom, didn´t work either
metlca said:
Thanks a lot, everything´s working again
But there´s another problem now..
I tried to flash cm10.1 with my new cwm recovery, but I get the error
"assert failed: getprop ("ro.product.device") =="p880"
getprop "ro.build.product") == "p880"
E:error in /sdcard/cm-10.1.2-p880.zip (Status 7)
Installation aborted"
Now what does that mean?.....
Thanks a lot
Edit:
Tried with other cm 10.1 based rom, didn´t work either
Click to expand...
Click to collapse
FFS - Learn to SEARCH before asking questions that have been covered 50+ times already.
Flash the newest cwm recovery and search next time it's a known problem and is well discussed.
Sent from my LG-P880
Tried FTL, TripNDroid and Omni - I still get the same errors like: set_metadata_recursive: some changes failed, E:Error in /sdcard/bla bla....
I tried CWM 6.0.3.1 and TWRP 2.6 3.3 and same thing happens...im a nab so ill just tell you what is says on my bootloader: TAMPERED, UNLOCKED and I dont know if its S-OFF or not
Please help!!!
Vorphs said:
Tried FTL, TripNDroid and Omni - I still get the same errors like: set_metadata_recursive: some changes failed, E:Error in /sdcard/bla bla....
I tried CWM 6.0.3.1 and TWRP 2.6 3.3 and same thing happens...im a nab so ill just tell you what is says on my bootloader: TAMPERED, UNLOCKED and I dont know if its S-OFF or not
Please help!!!
Click to expand...
Click to collapse
http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
Thank you, worked like a charm!
Hi,
My phone is refusing to flash cyanogenmod, I'm getting the following error:
assert failed: getprop("ro.product.devices") == "m7ul" |
E:Error executing updater binary in zip '/sdcard
Anyone have any ideas of why this is happening? I can flash other roms.. tried flashing HD revolution both in GPE and sense edition and both works. The phone is s-off, supercid
Have worked before, but it has been in for service, and got it back today.. and now this dosn't work.. HEEEELP
What recovery are you using?
SaHiLzZ said:
What recovery are you using?
Click to expand...
Click to collapse
Hey,
I'm using TWRP 2.6.3.3 Do i need to change to clockwork?
Its possible. Also try 2.6.3.0 TWRP
Hello
I received a notice to install the new KitKat on my rooted HTC one with TWRP 2.7.0.0
"OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-3.62.401.1_release_356395e7z2lsr0msqontmw.zip" 3XX,XX MB
When I tried to install the update from the recovery it tells me that no MD5 file was found
then
E:Signature Verification failed :1
and update is aborted ...
How can I solve this problem ?
Should I save a backup before starting solving ?
Will I lose my files ?
And thanks by the way
xsodia said:
Hello
I received a notice to install the new KitKat on my rooted HTC one with TWRP 2.7.0.0
"OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-3.62.401.1_release_356395e7z2lsr0msqontmw.zip" 3XX,XX MB
When I tried to install the update from the recovery it tells me that no MD5 file was found
then
E:Signature Verification failed :1
and update is aborted ...
How can I solve this problem ?
Should I save a backup before starting solving ?
Will I lose my files ?
And thanks by the way
Click to expand...
Click to collapse
There are many threads to do with this subject already.
You need stock recovery to install OTA. Find the one that is for your existing OS and flash it. Redownload the ota and it should install. If you have made any mods to your existing rom, that can also prevent the ota from installing properly.
Any yes I would make a nandroid first!
Ah that's all I needed !
this word key : Stock Recovery !
Thanks a lot my problem is solved and I'm eating the Kitkat now thanks
I had to "FIX Fastboot for win 8.1 x64"
Then "S-OFF my phone with hboot 1.55"
Then Flash the recovery with "Stock Recovery signed"
Last but not least,My kitkat is awesome !
Solved