Related
So I got this Tablet a few days ago and wanted to get root. It came with the 3.2 update already installed so I read around and saw I needed to downgrade the os, root, flash recovery, then flash a rom via recovery.
I plan to install this rom:
http://forum.xda-developers.com/showthread.php?t=1290318
It is basically stock acer 3.2 with root. Which is all I really want.
I followed method 2 here:
http://forum.xda-developers.com/showthread.php?t=1276227
After booting and installing the unstable version to be able to get root, then I did the adb push for cwm and itsmagic. Wasn't sure what to do after this so I rebooted. (I tried downloading the acer recovery installer but my market would not let me type anything in with all the force closes)
So after reboot I am unable to get adb to show it as a listed device and everytime I try to copy the rom over I need I get an error "Cannot copy *filename* The device has either stopped responding or has been disconnected"
In frustration I figured I didn't get cwm installed properly so I downloaded the apk from the web and installed it via dropbox. It let me apply it and actually boot into recovery.
I powered off and tried getting back in but my pc still fails to see the device listed in adb or save files to it via the basic windows file explorer.
I'm currently letting the update install itself (I flashed back the original recovery via acer recovery installer) don't know if this will fix it.
If anyone can help, it would be much appreciated.
Update:
It upgraded me to 3.1 but I still can't save anything to my tab (atleast the fc's are gone). It doesn't list anything on my tab just shows 0 files. Not sure how to get this fixed.
Update:
I did a factory reset. Now it detects it and I'm able to save the rom to it. I did the root, and flashed cwm thru acer recovery installer. (avoiding adb entirely). However when I'm in there now it says "E:Can’t mount /sdcard". Read some folks are throwing it on a usb drive and flashing it that way.(BTW I put the rom zip on the root file directory, not on the external SD). Will update if it works or not.
*RESOLVED*
Got it working. It installed off the USB thumb drive just fine. Was able to install the 3.2 root Rom mentioned earlier. Everything is working as it should. Able to read and write to and from the device now. Showing superuser in my apps. Now to start removing the crap Acer put on there
This is just in case anyone runs into the same problem. Took a few hrs but its working nice
Basically I suggest this if you wish to just install the the 3.2 stock rom via cwm
1.) Since the unstable flash doesn't clear your data, download and install everything you will need first. ex: Acer Recovery Installer, Iconia Root. Put the rom on the root drive and/or a thumb drive.
2) Flash the downgrade.
3) Run the Iconia Root tool.
4) Run the Acer recovery installer (since you'll have root now) and reboot to recovery
5) Flash the rom. If it doesn't detect it try it on a usb thumb drive. Done
I always put my ROMS on an external microSD. That is the only thing I use my SD card for, and as far as I can tell is always the recommended place to store your ROMS for updating. In the root of the microSD card.
Glad to hear you got it working though.
I just got OTA notification, should I install it? I'm rooted and have custom recovery.
If you're running stock 4.2.2 (you didn't flash a custom ROM or applied other system changes), then yes go ahead and install the OTA.
Check this thread for more info.
4.2.2 OTA Failed
Hey
I have a rooted Nexus 4 also. Running mako kernel. I got the 4.3 OTA update. Proceeded to install the update. But the update failed, then directed me to the stock recovery screen with the red warning sign. I rebooted the phone, went to Settings -> System Update, the 4.3 OTA is no longer there, and the phone is still running 4.2.2. What should I do to get 4.3?
I'm a noob.
Thank you for your help.
By "mako kernel" do you mean the stock kernel?
Why did the update fail - did you see the error message?
Since you're rooted, you have the option of re-flashing the OTA update:
1. The update zip should be in system/cache. First copy the zip file into your sdcard (ie the root folder).
2. If you don't have a custom recovery already, I suggest you use one to flash the OTA update. Install GooManager from the Play Store and install recovery. The default recovery is TWRP. Google Youtube for the process if you're not clear.
3. Once you're ready, reboot into TWRP recovery and select the OTA update file which you copied over in step 1. This should update you to 4.3.
4. If flashing this is successful, select the option to wipe dalvik cache, then select reboot device.
5. The phone will boot up and you should now see that you're on 4.3. You can now delete the OTA zip from your root folder.
6. If you want to re-root your phone, here's where TWRP comes in handy again. Download SuperSU from here, and paste it in the same root folder you placed the OTA zip before.
7. Now boot into recovery again, then choose to flash the SuperSU zip file.
8. Reboot phone and check that you have root access.
Good luck.
Settings -> About Phone -> Kernel Version
3.4.0-faux123-mako-custom
[email protected] #141
Sun Jun 23 00:57:50 CDT 2013
Can you please expand on Step 1?
Im not so sure as to what you mean and how to complete that step
Sorry for the trouble
Thanks
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
I managed to get the 4.3 OTA again
It downloaded and I'm now in the process of installing.
The phone reboots, (bootloader is unlocked), I see Droid, with the stomach open, blue bar right underneath it.(The screen that shows up with all updates)
Now the progress stopped. The blue bar stopped moving. This is the message on screen
Install Untrusted Package?
THIS CAN NOT BE UNDONE.
-No
-No
-No
-No
-No
- Yes - install untrusted zip
-No
-No
*******Go Back *********
When I choose "Yes- install untrusted zip", the installation fails, with the red warning sign and the droid laying on the ground.
Now I'm at the ClockworkMod Recovery v6.0.3.1 screen, given the following options.
- reboot system now
- install zip from sdcard
-install zip from sideload
- wipe data/ factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
The error message below the droid reads:
ClockworkMod Recovery v6.0.3.1
E: Invalid command argument
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installing update...
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/bin/thermald", "94e92fc68071c4f5b131d6b6a634a8e3ecca", "1f2323bbfa00ccb97c4f345e83f908ba61b830df")
E: Error in /cache/ebc8bad23772b5fd6e2907e48b4c74ba0ed58f21.signed-occam-JWR66V-fromJDQ39.ebc8bad2.zip
(Status 7)
Installation aborted.
Any help would be great.
Thanks again. I appreciate it
That message is very similar to mine when I tried to apply the update using my cwm I have my baseband flashed to .33 so I can enable LTE idk if that's the problem causing it
Sent from my Nexus 4 using xda app-developers app
@cliew:
Signature verification check failures tend to happen on CWM, which is another reason why I recommend using TWRP instead.
You can try following step 2 of my initial post and see if that works.
If the update still fails when you use TWRP, that means you've altered some system files that conflict with the OTA. You'll get another error message when that happens, and it should point to whichever file is in conflict.
---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------
@droidman89:
Yes, I believe if you've flashed different radios, that would most certainly stop the OTA taking. If you haven't already done so, you'll need to re-flash the stock ones in order to update.
I have the OTA file. Assuming that I'm on stock everything but rooted with a custom recovery, will the install still work, or should I reflash stock recovery as well?
@viewfindr
If only your recovery is custom - and no other system files have been modified - then yes, you should be able to take the OTA successfully.
Rooter? Lol just root or rooted. Sure it's a typo.
Sent from my Nexus 4 using xda app-developers app
mlj11 said:
I believe that's the faux kernel (not sure if that's the correct name; I don't keep up on kernels). You will need to flash the stock one from Google if you want to apply the 4.3 update.
Search this forum for more info on doing that; I think the thread I linked to earlier should have instructions.
Expanding on step 1:
- When your phone automatically downloads the OTA zip file, it will store it in system/cache. Open a file explorer app (like Solid Explorer), press back a few times, and you should see the "System root" folder. Look for the "cache" folder, and the OTA zip file should be inside.
- Copy this OTA zip file into your "Internal memory" folder. Actually you don't really need to do this step, however it's the easiest folder to select when you go into recovery mode.
Click to expand...
Click to collapse
Can't seem to locate this file anywhere in those folders. Any suggestions?
inc188 said:
Can't seem to locate this file anywhere in those folders. Any suggestions?
Click to expand...
Click to collapse
It should be in System root / cache. The other stuff in that folder (at least for me) are three folders named backup, lost+found and recovery.
If you can't find it there, it's probably because it's been some time since your OTA arrived. Which means it's now been cleared from cache.
If that's the case don't worry, because it'll come back again. Alternatively you can flash the update manually using the 4.3 image elsewhere in these forums.
------------------
Hit thanks if I helped
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Recovery stock and SD card seem to be the most reliable method.
Did you check the md5 of the zip? Also update.zip to put on root of the SD card should be the final zip, not the zip that contains another zip.
Also when booting in Android, I assume your SD is recognized, isn't it?
If so, instead of going to recovery then update from SD card, you can try to update from inside Android, from Phone settings, then Update item.
The phone should indicate the current version and the version to be updated to. Then follow the phone indication to update.
Nope, i dont checked MD5. But shouldn't be the problen. I tried many different update files, always same error.
Yes, after booting the SD card is connected and i could use it. Just the recovery mode cant mount the card.
Also the updater recognize my update. But he just boot in the recovery mode and try to update -> Same error: "couldn't mount /sdcard"
Edit 1:
But i can check the MD5 files if necessary. I just need the "correct" MD5 value to compare.
Just a guess:
Is your micro SD card size greater than or equal to 128 GB? Some version has this bug, size less than or equal to 64 GB should work better. To try if this is the case.
t4ggno said:
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Click to expand...
Click to collapse
Why are you using an SD card though? Put it in the root of the internal storage and it will surely pop up, then try again from Updates, not the recovery (and get the SD off the phone to avoid the phone from detecting the zip there)
Otherwise root and get TWRP and flash Tron1's stuff
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
t4ggno said:
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Click to expand...
Click to collapse
Also, bricked means totally unusable, so no it isn't bricked lol
dnlilas said:
Just a guess:
Is your micro SD card size greater than or equal to 128 GB? Some version has this bug, size less than or equal to 64 GB should work better. To try if this is the case.
Click to expand...
Click to collapse
Its a 64 GB card Should i try a <= 32 GB card? Could be I have some lying around. Just to be sure its not a special case.
I will test it tomorrow if i found one
Choose an username... said:
Why are you using an SD card though? Put it in the root of the internal storage and it will surely pop up, then try again from Updates, not the recovery (and get the SD off the phone to avoid the phone from detecting the zip there)
Otherwise root and get TWRP and flash Tron1's stuff
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Also, bricked means totally unusable, so no it isn't bricked lol
Click to expand...
Click to collapse
Hm, last time it only recognize the update file on my SD card. I will try it tomorrow again and will post the result.
TWRP isnt a option, because i dont want to lose my warranty. Also i read that TWRP can be incompatible with Stock-ROM?!
t4ggno said:
Hm, last time it only recognize the update file on my SD card. I will try it tomorrow again and will post the result.
TWRP isnt a option, because i dont want to lose my warranty. Also i read that TWRP can be incompatible with Stock-ROM?!
Click to expand...
Click to collapse
I don't know where you read that, but the closest answer that I can give you is: if you don't install SuperSU, Magisk, or the dm-verity patch, TWRP will get replaced with the stock recovery and you'll have to flash it again (~2 minutes anyways). But it is in no way incompatible. Also you can relock and stuff, but yeah better keep the warranty at least until you're sure that your phone is good.
You unpacked the zip that you downloaded right? to get the update.zip inside? Or did you download it from raysteff's thread? It should work anyways
Another thing: What is your phone's model (G, U, chinese) and what is the update that you're trying to install? I guess it will fail if it is from another model, and if you're trying to jump fron a very old MM build to a very new N build it will probably fail too. Keep that in mind.
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Choose an username... said:
I don't know where you read that, but the closest answer that I can give you is: if you don't install SuperSU, Magisk, or the dm-verity patch, TWRP will get replaced with the stock recovery and you'll have to flash it again (~2 minutes anyways). But it is in no way incompatible. Also you can relock and stuff, but yeah better keep the warranty at least until you're sure that your phone is good.
You unpacked the zip that you downloaded right? to get the update.zip inside? Or did you download it from raysteff's thread? It should work anyways
Another thing: What is your phone's model (G, U, chinese) and what is the update that you're trying to install? I guess it will fail if it is from another model, and if you're trying to jump fron a very old MM build to a very new N build it will probably fail too. Keep that in mind.
Click to expand...
Click to collapse
I didnt unpacked the folder. A recovery normally installs zip files?! The zip file isn't packed twice. The zip contains the files directly.
I tried the package A2017G-MM-B11 and A2017G-N-B01 from the link I posted, also i tried the oficiell patch files from the axon website (B10 and Nougat)
otaconremo said:
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Click to expand...
Click to collapse
I have a A2017G (that information i found on the back of my phone).
My phone overview tells me:
Modelnumber: ZTE A201G
Build-Number: ZTE A2017GV1.0.0B08
Android-Version: 6.0.1
Security-Patch: 1. December 2016
I can try to install the B09. Probably this patch is required to go to version 10 (and than to nougat)?
Don't know if it applies to your situation, but when the OTA for 7.x came out, there was a bug that would not allow the update to be applied if there was an SD card installed. I know I had to pull my card to get the update to take. Might try running the OTA without the card installed and see if it works.
karlkarloff said:
Don't know if it applies to your situation, but when the OTA for 7.x came out, there was a bug that would not allow the update to be applied if there was an SD card installed. I know I had to pull my card to get the update to take. Might try running the OTA without the card installed and see if it works.
Click to expand...
Click to collapse
I tried it, but doesn't work :/
The update stops at 33% with the error message "Package Mismatch".
t4ggno said:
I didnt unpacked the folder. A recovery normally installs zip files?! The zip file isn't packed twice. The zip contains the files directly.
I can try to install the B09. Probably this patch is required to go to version 10 (and than to nougat)?
Click to expand...
Click to collapse
No, B09 was a patch only for Spain.
The zip you download from the ZTE website has a bunch of numbers as name and has an update.zip inside and a PDF or sth like that. The one you have to flash is the update.zip inside, just sayin'...
If you download the zips from raysteff's thread they are already unpacked.
Try installing an older zip, like B03, then B10
Choose an username... said:
No, B09 was a patch only for Spain.
The zip you download from the ZTE website has a bunch of numbers as name and has an update.zip inside and a PDF or sth like that. The one you have to flash is the update.zip inside, just sayin'...
If you download the zips from raysteff's thread they are already unpacked.
Try installing an older zip, like B03, then B10
Click to expand...
Click to collapse
The big problem still exists -> I cant mount my SD card in recovery mode, so I cant install any patch.
I really want to try B03 as you suggested, but i am unable to install it.
I will search another SD card an try to use it. Probably my SD card has some problems.
Edit: I download my files from these side: http://www.ztemobile.de/support/downloads/?product_id=2100
They dont contain a update.zip. Only many .dat, .bin, .img and .mbn files.
t4ggno said:
The big problem still exists -> I cant mount my SD card in recovery mode, so I cant install any patch.
I really want to try B03 as you suggested, but i am unable to install it.
I will search another SD card an try to use it. Probably my SD card has some problems.
Edit: I download my files from these side: http://www.ztemobile.de/support/downloads/?product_id=2100
They dont contain a update.zip. Only many .dat, .bin, .img and .mbn files.
Click to expand...
Click to collapse
But install it from the internal storage and with thr Updates option on Android itself... You need to put it in the root of the internal storage or it most likely won't find the zip
Choose an username... said:
But install it from the internal storage and with thr Updates option on Android itself... You need to put it in the root of the internal storage or it most likely won't find the zip
Click to expand...
Click to collapse
Thanks! That worked very well. I did a factory reset and moved the update file directly to the root of my internal storage. After that the updater detected my update and I could install the Patch B011. After that i was able to update to Nougat trough OTA. No errors, every worked fine.
otaconremo said:
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Click to expand...
Click to collapse
it seems that I got this one with modified rom. is there anyway to get it back to the official chinese rom?
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Did you fix your problem cause I fix mine my device can boot to fast boot mode if you
Did you fix your problem cause I fix mine my device can boot to fast boot mode if yours can I will send you the original recovery boot manger then download the latest firmware from the official webpage the go to bootloader and update the file it will work for sure but now have a software touch problems I tried to change theme and enable gloves mode it worked fine for a little time
Same issue..
Hey Lobstercat,
I am having the same problem as you..
I have tried TWRP (format /cache, /dalvik, /system and /data) with an unlock bootloader from an Asus Selfie. I have made a backup of it before trying the above. TWRP was able to restore the UL-Z00T-WW-1.12.40.382 OS fine.
But when install through TWRP, on UL-Z00T-WW-1.13.40.661-user.zip, it gives up on authentication, of which I also turned off with the same result.
In sideload mode it failed with the following message;
sudo adb sideload UL-Z00T-WW-1.13.40.661-user.zip serving: 'UL-Z00T-WW-1.13.40.661-user.zip' (~79%) E: fota_return_code 408
I have also tried "sudo fastboot flash system system.img" it failed, with the message "system.img was too large" this rendered my device unbootable and TWRP cannot restore the backup grrr..
I have the latest fastboot and adb from google went through the same above procedure with the same result, TWRP terminal shows files which I cannot be deleted with rm -rf command
I need to update with the OTA updates to UL-Z00T-WW-1.15 from Asus first before moving over to LOS.
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse
Resolved..
I was able to sort it out through this link.
https://forum.xda-developers.com/zenfone-2-laser/orig-development/rom-cyanogenmod-13-0-t3317515
"In order to update your firmware to MM one you can either flash ASUS MM rom in stock recovery or flash a package that will update your fw which you can download right here"
Download that link, sideload it with no issues and lineage OS 14 with no issues.
Now running Lineage OS 14. Damn its quick!
Getting failed to mount'/persist'(invalid argument) while flashing custom rom lineage
Lobstercat said:
Posted this as well over on the official Asus site, but I've always found XDA to be full of great answers (& awesome devs) so posting here as well. Okay, so my fault for being impatient to wait for the gradual OTAs but now here's the problem. I rooted the phone and unlocked the bootloader, then installed TWRP for recovery. I backed up my phone. Then I tried to install (flash) new ROMs, starting with some official ones from the ASUS website, then branching out to Lineage, CM, Ressurection, Dirty Unicorns, and uh, something else, don't remember. Anyway, nothing works. I cannot install from SD card, from phone, or from ADB sideload. Nor can I now restore my backup.
ALL ROMs give me errors, I took screenshots of some recent attempts all saying zip signature verification error, lots of other ones indicating the wrong ROM. I researched that error, don't remember exactly what it said, but the workarounds posted were to unzip the ROMs and edit a file, deleting the part that checks for the right version. I can understand if a third party ROM has this problem, but ALL the ROMs - even the ones downloaded directly from Asus?!? No, I think there is another problem here though I could be wrong. Trying to restore my backup gives me either MD5 failed to match or Extracktarfork() Error 255.
So now the system partition is wiped and so nothing will boot at all. The one silver lining is that I CAN still boot into TWRP recovery. Another issue which may or may not be related is that (Just before the system partition got wiped during another attempted ROM flash) I lost the ability to write anything to the external SD card. The contents were readable but I could not write anything to it at all. I would chalk all my ROM problems up to a screwy SD card except that ADB sideloading didn't work either so ... I don't know what to do here. Any help or suggestions would be appreciated.
If you need any additional info, just ask - I probably just forgot to put it in the post. Just in case, I am working with a Asus Zenfone Selfie, ZD551KL, Z00UD, Android WW, 32G internal, 3G RAM. Oh, one last thing, probably just a bum cord but sometimes especially now ADB in windows doesn't see anything & I have to use linux.
Was originally hoping to get the latest Android N installed - Lineage/CM, but at this point I would gladly just go back to the stock ROM if I could finally get it to work. Thank you all again for reading my question & for any help or suggestions you can offer.
EDIT: The more info the better the help, right? I removed the SD card- trying to retrieve my info from it. I can view, just not copy (or write) so using a data recovery program to copy my files off, then I will try to reformat it. Anyway, I tried sideloading and installing from both CM and official Asus zips so I could post the errors - & they have changed a bit. Sideloading remains the same: CM gets to around 50% then stops with the line "Total xfer: 1.00x". The Asus ROM never starts. It gives the error "cannot read ..." but checked it with 7zip and it says there are no errors. On the phone side, obviously nothing on the Asus ROM since it never even starts, but the CM says "assert failed: ....", then gives an ERROR: 7. Copying the files to internal storage & trying to flash them from there, Asus ROM says Zip signature verification failed. Then "Unable to mount storage". CM says assert failed, ERROR: 7, & Unable to mount storage. Hope that helps!
EDIT2: Also tried the suggestion of deleting the asserts part of the ROM, but it says "Invalid zip file format". Any ideas on what the proper zip file format would be? If you open up 7zip as a program there are some options there, what would I need to do differently?
Click to expand...
Click to collapse
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance
Jayants susner said:
I am on latest version of TWRP have done all the process
unlocked bootloader
Rooted my phone
On latest version of TWRP
Official lineage os 14.1
But all time getting failed to mount'/persist'(invalid argument)
Even not able to go back to stock recovery through back2stock.zip process
currently operating my phone through restoring backup
What I need to do please anybody have any solution of this please reply thanks in advance
Click to expand...
Click to collapse
Excuses excuses, but bottom line just don't get around to things very fast very often. Did you ever figure it out? It was a long time ago now so I assume you did....
Hello,
This question has been posted before but I didn't find a solution on the previous threads.
My VNS-L31C432 doesn't boot past 'Your device is booting now'' after trying to install the C900B300 rollback package. The dload method, as well as the default recovery don't work either. I can access fastboot and flash another rom (using this method: https://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404), but so far nothing worked.
I can also install TWRP, access adb and shut down. I wiped everything from my phone in order to do a clean install, didn't work.
I was previously on Marshmallow (VNS-L31C432B161)
Any help would be greatly appreciated!
If your twrp works , try to install the rom with this method : https://forum.xda-developers.com/hu...ota-p9-lite-upgrade-rebrand-tools-pc-t3778839, it worked for me from soft brick. Download and try with FullOTA-MF-PV rom first.
lost3 said:
If your twrp works , try to install the rom with this method : https://forum.xda-developers.com/hu...ota-p9-lite-upgrade-rebrand-tools-pc-t3778839, it worked for me from soft brick. Download and try with FullOTA-MF-PV rom first.
Click to expand...
Click to collapse
Well holy sh** thank you so much!
I saw that you have single sim phone , so you must download rom with odd number ,try to download 391 version.
Download the HWOTA-VNS.zip file and unzip it. Copy the directory HWOTA-VNS to the root of your sd card.
When all of 3 files downloads find the one update_full_hw_xxxx zip (xxx is like e.g vns-l21c391 ) and rename it to update_all_hw.zip, copy the 3 files inside the HWOTA-VNS/upgrade directory.
Reboot to twrp and go to WIPE->Advanced wipe mark data and push Repair or Change File System, if writes: File System : ext4, live it , if its F2FS , hit Change File System and change it to ext4. Go back to main menu , go to install guide to HWOTA-VNS directory and install hwota_update.zip after that the phone will reboot and starts to update.