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.
Related
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
Hi there,
I have CWM 6.0.3.1 and I tried to flash Tripndroid's Kitkat ROM, however it didn't flash properly and now nothing will flash.
Unfortunately, in trying to solve the issue, I have managed to delete all back-ups by formatting my sdcard. So I have to get something to flash and boot.
Flashing happens way too quickly, and the log reports:
Code:
Install from sdcard complete
minzip: Error writing 16384 bytes from zip file from 0xbef74c6c: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
unmount of /system failed; no such volume script result was []
Flashing boot image...
Install from sdcard complete.
I:using /data/media for /sdcard/0/clockworkmod/.recovery_version
I:using /data/media for /sdcard/clockworkmod/.recovery_version
I:Can't partition non-vfat: datamedia
I:Can't format unknown volume: /emmc
Can someone shed some light on what I need to do?
I have HBoot 1.44 and S-On
swatsbiz said:
Hi there,
I have CWM 6.0.3.1
Click to expand...
Click to collapse
update CWM, 6.0.3.1 is WAY outdated: http://forum.xda-developers.com/showthread.php?t=2173863
nkk71 said:
update CWM, 6.0.3.1 is WAY outdated: http://forum.xda-developers.com/showthread.php?t=2173863
Click to expand...
Click to collapse
That's what I get for going to the CWm website! Flashing now, will update if that fixes my challenge.
swatsbiz said:
That's what I get for going to the CWm website! Flashing now, will update if that fixes my challenge.
Click to expand...
Click to collapse
the websites are outdated, latest CWM (and even TWRP I think) are on the xda threads.
If you're going for 4.4 might wanna check this too: http://forum.xda-developers.com/showthread.php?t=2539474
Unfortunately now when I flash the zip (it's Slimrom: Android 4.3) recovery reboots the phone after supposedly flashing. So I can't provide a log from the install.
The only log available is from booting up and it reports:
Code:
I:checking for extendedcommand ...
I:Skipping execution of extendedcommand, file not found...
I'll check out the 4.4 advice for the next time I try to flash one
swatsbiz said:
Unfortunately now when I flash the zip (it's Slimrom: Android 4.3) recovery reboots the phone after supposedly flashing. So I can't provide a log from the install.
The only log available is from booting up and it reports:
Code:
I:checking for extendedcommand ...
I:Skipping execution of extendedcommand, file not found...
I'll check out the 4.4 advice for the next time I try to flash one
Click to expand...
Click to collapse
everything looks strange ; what's your device & carrier?
nkk71 said:
everything looks strange ; what's your device & carrier?
Click to expand...
Click to collapse
YEAH I KNOW!
I'm on the International version of the M7 with THREE
swatsbiz said:
YEAH I KNOW!
I'm on the International version of the M7 with THREE
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n)
et voila!
{
"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"
}
swatsbiz said:
et voila!
Click to expand...
Click to collapse
"et voila!" -> eh bien non!!
firmware!! version-main: <empty>
not nice!!
you're still on hboot 1.44 and S-On, so I would assume firmware 1.xx, highly recommend you try using revone to get s-off. you'll need a 4.1.2 ROM for highest chance of success.
let me know if you need one, i can send the link via PM....
nkk71 said:
"et voila!" -> eh bien non!!
firmware!! version-main: <empty>
not nice!!
you're still on hboot 1.44 and S-On, so I would assume firmware 1.xx, highly recommend you try using revone to get s-off. you'll need a 4.1.2 ROM for highest chance of success.
let me know if you need one, i can send the link via PM....
Click to expand...
Click to collapse
Yeah, could you send me that link please? I've tried revone but unsuccessfully so far.
Thanks for your time!
swatsbiz said:
Yeah, could you send me that link please? I've tried revone but unsuccessfully so far.
Thanks for your time!
Click to expand...
Click to collapse
Incoming PM, hit the thanks button if i've helped
I'll post my results once flashed
Many thanks that has finally worked, I think ... any suggestions for the next step?
swatsbiz said:
Many thanks that has finally worked, I think ... any suggestions for the next step?
Click to expand...
Click to collapse
maybe best to run a full RUU.exe to (re)install everything back to stock (S-Off will stay, and since you're s-off no need to relock bootloader), then flash back custom recovery, and your favorite rom. and u can now upgrade firmware since you're s-off
remember: RUU will wipe everything off your phone so backup anything you may need to PC
Thanks again, albeit, have already started the RUU update before seeing your reply ...
swatsbiz said:
Thanks again, albeit, have already started the RUU update before seeing your reply ...
Click to expand...
Click to collapse
no problem, good choice going for an RUU, as a first step imho
ERM...
Flashed RUU successfully
Sideloaded ARHD again, after booting screen wouldn't respond, rebooted a couple of times but still no response.
Flashed Slimrom instead, reboot ... screen blank, led blank, holding buttons down seems to do nothing ...!!!
ERM...
Flashed RUU successfully
Sideloaded ARHD again, after booting screen wouldn't respond, rebooted a couple of times but still no response.
Flashed Slimrom instead, reboot ... screen blank, led blank, holding buttons down seems to do nothing ...!!!
swatsbiz said:
ERM...
Flashed RUU successfully
Sideloaded ARHD again, after booting screen wouldn't respond, rebooted a couple of times but still no response.
Flashed Slimrom instead, reboot ... screen blank, led blank, holding buttons down seems to do nothing ...!!!
Click to expand...
Click to collapse
reflash RUU, boot up, make sure phone is working before going custom ROM; could just be a firmware issue, but first make sure your phone boots normally after RUU.exe
Hi,
I bought today a 701T ww, with bootloader version 10.26.1.7.
I've been able to unlock the bootloader, root the rom, and install a custom CWM (now 6.0.4.6).
I installed the custom rom CROMi-X 6.0b2
But I'm now unable to upgrade the bootloader to 10.26.1.18.
I reverted to stock 10.27.1.7 rom thanks to the nandroid backup I made prior CROM install, I've tried downloading the official update package from Asus, which is supposed to be the only way to upgrade the bootloader. I've put the UL-K00C-WW-10.26.1.18-user.zip file on the root of a MicroSD, the tablet recognized the update file, and rebooted to install it. Problem is that, after reboot, the tablet enters in the CWM with the following error :
{
"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"
}
Off course if I try "Yes - install untrusted.zip" it doesn't rework, and the tablet reboots ....
many thanks if you can help !
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
berndblb said:
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
Click to expand...
Click to collapse
Hi Berndblb, thanks for your reply.
Toggling the signature verification didn't help, I've already tried that.
I didn't miss this, but as I've never been able to upgrade the bootloader thanks to the official update, I thought that with CROMI the bootloader would be upgraded too. I noticed that was'nt the case, that's why I restored my nandroid backup to revert to the stock 10.26.1.7.
Now I'm in 10.26.1.7, and precisely want to upgrade the bootloader to be able to install CROMI with the correct bootloader. Therefore my question.
Would a "fastboot flash boot boot.img" using the boot.img file included in the official asus 10.28.1.18 package be a good idea ?
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
usoska said:
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
Click to expand...
Click to collapse
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Calp said:
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Click to expand...
Click to collapse
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
berndblb said:
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
Click to expand...
Click to collapse
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Calp said:
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Click to expand...
Click to collapse
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
berndblb said:
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
Click to expand...
Click to collapse
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Calp said:
THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
You're very welcome !
That looks correct.
Calp said:
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
WooHoo! excelent. Glad you got everything all sorted out.
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
2 days, how dare you. You should be concentrating on b4 and only b4.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
Wow, you're crazy! I really appreciate your help, mate.
For anyone else needing to do these stips, here's the download link for the stock recovery which you have to flash first: http://droidbasement.com/db-blog/?p=3210 ( i also tried a different one but only this one did work in the end)
Also, thanks a lot for the ROM, sdbags. I've been using it for a couple of hours now and it seems to work like a charm. Great work, mate!
Sent from my K00C using xda app-developers app
How can I tell which bootloader (BL) and firmware (FW) I run currently? When I hold power/volume down, the top of the screen says user BL released by "US_epad-10.26.1.7". When I boot into Android and go into settings -> about -> software, I see Build number "JSS15J.US_epad-10.26.1.18". Is the 1.18 the firmware (FW) version?
Finally, is there a way to upgrade BL/FW to ...1.18 version without using an external SD card?
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Thanks. Just to verify, you don't think doing "fastboot flash boot boot.img" will work? (using boot.img from UL-K00C-US-10.26.1.18-user.zip).
Also, by SD-card method, are you talking about the rename “WW_10_26_1_18_SDupdate” to “T4_SDUPDATE.zip" process etc.? It seems that I have the US SKU, and not sure if this would work, being that it mentions WW in the file name.
Sleeepy2 said:
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Click to expand...
Click to collapse
I am no expert but I am pretty sure that the fastboot method doesn't work as there have been several people with the wrong bootloader issue and and the only way to do it was with the official update.
I am not sure about using the WW file or not. I am in canada and I used the other file to update and that did the bootloader also. With the status your in now I am not sure if the US one will work or not. I would try the US one first and then if not go with the steps from pershoot
http://forum.xda-developers.com/showpost.php?p=52187532&postcount=87
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
MilesWilford said:
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
Click to expand...
Click to collapse
It's still there, try this link
http://droidbasement.com/asus/tf701t/stock/
Hi,
I have a rooted NEM-L51 (with TWRP 3.1.1-0 as recovery) running Android 7.0/EMUI 5.0 (build number NEM-L51C432B350).
A new OTA update is available (build number NEM-L51C432B355) but after downloading and rebooting to recovery (TWRP) to apply it, it fails with the following error:
Code:
script aborted: assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
Updater process ended with ERROR: 7
I googled it but couldn't find anything that seems useful. You'll find attached the complete log (I was using TWRP 3.1.0-2 at the time and has since upgraded, thinking it could be related to it).
Does anyone have any idea about what's going wrong here?
Could it be because the system partition has been modified in the process of rooting the phone (I'm thinking about that because of the 'block_image_verifiy(.../system...)') — note that I was able to apply OTA updates on my rooted device in the past?
Thanks!
You have magisk or SuperSU?!
why you trying to install updates on twrp....
Try useing stock recovery from the update.
PalakMi said:
You have magisk or SuperSU?!
Click to expand...
Click to collapse
SuperSU, v2.82.
thelous said:
why you trying to install updates on twrp....
Click to expand...
Click to collapse
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
AlexMihai26 said:
Try useing stock recovery from the update.
Click to expand...
Click to collapse
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?
Try magisk!
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?
fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?
Click to expand...
Click to collapse
Update.app with stock recovery, zip with twrp
sclarckone said:
SuperSU, v2.82.
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?
Click to expand...
Click to collapse
Yep
PalakMi said:
Try magisk!
Click to expand...
Click to collapse
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash.
Click to expand...
Click to collapse
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_data_public.zip (around 13 MB) which seems to contain updates for Honor system apps.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
fishnchips2 said:
Are you using the openkirin twrp?
Click to expand...
Click to collapse
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^
I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Twrp and root were lost during the update because the rom replaces them with its own files in the first boot. I don't know why the ota updates worked before.
Because you can hide root with magisk.
fishnchips2 said:
I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
Click to expand...
Click to collapse
Just to be clear, these files I mentioned in my previous post are the one downloaded by the OTA updater of EMUI (and TWRP fails on flashing the first one, update.zip) so I shouldn't flash them with TWRP, right?
I'm a bit confused about this because if ZIP files are supposed to be used with TWRP and the APP files with the stock recovery, why did the EMUI OTA updater download ZIP files (I would expect it to download files as if I had a stock recovery)?
fishnchips2 said:
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Click to expand...
Click to collapse
So these are the files flashable with TWRP (in that case I don't need the stock recovery)? The ones corresponding to the upgrade I'm looking for seem to be the following:
The OTA one seems to be exactly the same update.zip that was downloaded by the EMUI OTA updater. Should I try the FullOTA variant?
{
"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"
}
Sorry if I sound a bit meticulous but I'd rather not brick my phone and understand what I'm doing. ^^
The error you're getting is error 7 which means the rom is supposedly incompatible with your device. As this is the official update, I have no idea why this error is coming up. I think that once you get past that error, twrp should be fine flashing the zip file.
The difference between ota files and fullota files is that a fullota contains most of the files needed by the rom while the ota only replaces files that have changed. As you are on b350 nougat already, an update to b355 should only need a normal ota update.
Don't worry about asking questions, it's good that you're cautious with your phone.?
---------- Post added at 09:52 PM ---------- Previous post was at 09:45 PM ----------
EDIT!!!
Sorry I was wrong in the previous reply. Twrp can't flash an ota update because it only replaces some files, whereas twrp will flash the entire system. However, a fullota file should work (haven't tried??).
This also explains why it had error 7: the manufacturer doesn't want someone accidentally flashing an incremental update as a full rom.
More info is here : https://twrp.me/faq/officialota.html
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
Further edit : I believe that you have to wipe certain partitions (system and cache?) before flashing an update because 'dirty flashing' doesn't always fully replace everything and causes issues later. However this may be different for stock roms. Nevertheless, always make a backup!
Hopefully final edit: a dirty flash means that you don't wipe data first. This should be fine for an official update. Opinions vary on wiping system, cache and dalvik but I think the recovery should do that for you.
Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.
PalakMi said:
Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.
Click to expand...
Click to collapse
Yup I believe so
Honor devices are one of the most complicated when it comes to flashing ROMs.
I know ? at least it isn't the s8 exynos version. I hear you can't even unlock the bootloader on that.
Yeah, however, I wish honor makes it simple with upcoming devices (like OnePlus)
sclarckone said:
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^
Click to expand...
Click to collapse
Use Huawei update extractor,and you should find a recovery.img
Guys, there is a VERY good (and very bad, but about it in the end) news, at my request, one good forumchanin under the nickname yurxxl from 4PDA, collected on TWRP for Poco M4 Pro 5G
Decryption / data works, connection to the computer, I installed magisk through it.
**********************
Installation:
in fastboot mode with the command:
fastboot flash boot twrp.img
<><><><><><><><><><><
And now the bad news:I put the Taiwanese firmware on myself in the morning,and first tested the recovery on it,yes,the recovery is put on it,and everything also works,there are no questions to the recovery,BUT I flashed the magisk,rebooted the system,updated the magisk from the application,the program wrote about the need to reboot,the reboot went,but then the system did not boot,and even deleting the adb folder (where the magisk is placed),nor the twrp firmware (which is the boot, if anyone did not know) did not help again,I was able to boot into the system only by making format data. Then I put back the global firmware, and everything is fine on it, magisk works fine.
——————————————————
Well, I will add more, yesterday, after all these installations of gsi firmware, and flashing the drain, this inscription dm-verity corruption appeared on my logo your device is corrupt. it can't be trusted and my not work properly. press enter button to continue. Or, device will power off in 5s. Since the firmware via fastboot is buggy for me, I flash through F.T. Sewed in download mode.Then I decided to still try to flash in firmware upgrade mode, since in this mode the firmware formats the memory, and after the firmware the inscription disappeared. Yes, also, in this mode, the bootloader is blocked, I first flashed the Taiwanese firmware, and through MiUnlock, without waiting, unlocked the bootloader.And when a jamb with a magisk appeared on it, I flashed it to the global one, again through firmware upgrade, respectively, I blocked the bootloader again, but I unblocked it right after. Maybe someone will need it.I updated the recovery, now the smartphone is visible in them by the computer when connected in fastbootd mode, which facilitates the installation of gsi firmware.
Yes, the recovery is already patched in magisk
Spoiler: screenshots
{
"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"
}
Guys, I forgot to add, I have Poco, so the recovery was tested on this modification, on two firmware versions, Global and Taiwan. I do not know if it will work for Redmi.I've disassembled the boot from the firmware for India, there is another core used. And yet, I see they have already downloaded 5 times, they could have written how everything went, it became normal
Hello,
I've tried your twrp, but some partitions are unavailable. By the way, why to flash in boot and not in recovery?
stratonz said:
Hello,
I've tried your twrp, but some partitions are unavailable. By the way, why to flash in boot and not in recovery?
Click to expand...
Click to collapse
Because we do not have a separate recovery, it is located in the boot, so it is practically a stock boot, with a recovery added to it. Which sections are unavailable?
arraki said:
Because we do not have a separate recovery, it is located in the boot, so it is practically a stock boot, with a recovery added to it. Which sections are unavailable?
Click to expand...
Click to collapse
I can't remember now, cos' I have uninstalled twrp and restore original firmware, but it seems to me that was impossible to install GSI in system. A question: have I to install twrp in both the boot partition?
ah, maybe I've tried to do a nandroid backup and in the partition list there wasn't system
stratonz said:
to install GSI in system.
Click to expand...
Click to collapse
For the gsi firmware, it is necessary that the recovery supports this function, few recoveries are able to do this. Backup should be done of the super partition, for normal recovery it is enough to make a backup of two partitions:data and super, I checked. And gsi are normally put through fastbootD. Here I put it on trial
Spoiler: GSI
Thanks, I reinstall twrp, it works, but during backup process createTarFork ended with error code 255, seems dued to (from log):
failed to lookup fscrypt tar policy for '/data/extm' - 'a0e08c6d2252b15091f8e5807863eaa1'
....
I:Error adding file '/data/extm/I581aDAAAAQh4qwuBNkwvrSSE3fUn6RD' to '/data/media/0/TWRP/BACKUPS/CQX899S4BQ8TQWAU/2022-03-04--07-06-12_CUST_evergreen/data.f2fs.win011'
any suggestions? googling, this extm folder seems to be a common problem...
stratonz said:
Thanks, I reinstall twrp, it works, but during backup process createTarFork ended with error code 255, seems dued to (from log):
failed to lookup fscrypt tar policy for '/data/extm' - 'a0e08c6d2252b15091f8e5807863eaa1'
....
I:Error adding file '/data/extm/I581aDAAAAQh4qwuBNkwvrSSE3fUn6RD' to '/data/media/0/TWRP/BACKUPS/CQX899S4BQ8TQWAU/2022-03-04--07-06-12_CUST_evergreen/data.f2fs.win011'
any suggestions? googling, this extm folder seems to be a common problem...
Click to expand...
Click to collapse
Strange, I did a backup data, everything went fine.Although, I didn't do a backup in twrp, I still have a recovery Orange Fox, I did a backup to them, I'll check in twrp later And I've seen this error before on another smartphone, you just need to delete this folder, and everything will be fine.
arraki said:
Strange, I did a backup data, everything went fine.Although, I didn't do a backup in twrp, I still have a recovery Orange Fox, I did a backup to them, I'll check in twrp later And I've seen this error before on another smartphone, you just need to delete this folder, and everything will be fine.
Click to expand...
Click to collapse
Excuse me, have you also a orange fox recovery working on poco m4 pro 5g/redmi etc etc?
stratonz said:
Excuse me, have you also a orange fox recovery working on poco m4 pro 5g/redmi etc etc?
Click to expand...
Click to collapse
Yes, but I also don't know if it will work on Redmi, it works well on Poco, but I really didn't check everything.
I have Poco (evergreen) could I test it?
Just another question: flashing twrp I lost root (magisk). To restore root I have to install magisk from inside twrp, with "install zip"?
stratonz said:
Just another question: flashing twrp I lost root (magisk). To restore root I have to install magisk from inside twrp, with "install zip"?
Click to expand...
Click to collapse
Ok! Done as described and it works
Regarding the TWRP I posted (and orange Fox, which will be below), the MTP works in them, but there is no connection to the computer in fastbootd, the computer does not even react.I wrote about this to the author, I hope he will fix it. Also, when creating a backup /data in twrp, the process ends with an error, the extm folder is to blame for everything.I've seen this error before, on other smartphones, you just need to delete this folder, it won't be a big deal.But there is no such mistake in Orange Fox.
arraki said:
Regarding the TWRP I posted (and orange Fox, which will be below), the MTP works in them, but there is no connection to the computer in fastbootd, the computer does not even react.I wrote about this to the author, I hope he will fix it. Also, when creating a backup /data in twrp, the process ends with an error, the extm folder is to blame for everything.I've seen this error before, on other smartphones, you just need to delete this folder, it won't be a big deal.But there is no such mistake in Orange Fox.
Click to expand...
Click to collapse
Thanks for OF and for working on recoveries!
Twrp available for Note 11T (Evergo) is useless. It can't flash magisk or Gapps. Tested by some users in Telegram, and they failed.
So can anybody help how to flash GApps into Note 11T (evergo) with TWRP?
I mean flashing China MIUI ROM and Flash GApps into that with TWRP.
When i tried to install using "fastboot flash boot OF_boot.img" it gives error
FAILED (remote: This partition doesn't exist)
I also tried "fastboot boot OF_boot.img" then it gives this error
downloading 'boot.img'...
OKAY [ 3.720s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.552s
Please guide me @arraki
Update : It worked , i tried using latest platform tools then it does not give any errors!
Thank you very much for creating this recovery file @arraki
Anmol98 said:
When i tried to install using "fastboot flash boot OF_boot.img" it gives error
FAILED (remote: This partition doesn't exist)
I also tried "fastboot boot OF_boot.img" then it gives this error
downloading 'boot.img'...
OKAY [ 3.720s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.552s
Please guide me @arraki
Click to expand...
Click to collapse
Is your bootloader unlocked?
arraki said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
it is working now , after i used latest platform tools !
Thanks...