So I decided I'm tired of all the bugs in Android 4.4 and wanted to flash the PACMan ROM onto my 2012 Wifi only Nexus 7. So I have my nexus unlocked and rooted but when I go to install the ROM via TWRP V2.6.3.1 I get this error message:
Installing '/sdcard/pac_grouper-nightly-20140121.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" II getprop("ro.build.pr
E:Error executing updater binary in zip '/sdcard/pac_grouper-nightly-20140121.zip
Updating partition files..
Can anyone tell me whats going wrong? I'm terrible at the whole computer thing, unlocking and rooting was tough enough even with the Nexus Root Toolkit.
Thanks
ST2014 said:
So I decided I'm tired of all the bugs in Android 4.4 and wanted to flash the PACMan ROM onto my 2012 Wifi only Nexus 7. So I have my nexus unlocked and rooted but when I go to install the ROM via TWRP V2.6.3.1 I get this error message:
Installing '/sdcard/pac_grouper-nightly-20140121.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "grouper" II getprop("ro.build.pr
E:Error executing updater binary in zip '/sdcard/pac_grouper-nightly-20140121.zip
Updating partition files..
Can anyone tell me whats going wrong? I'm terrible at the whole computer thing, unlocking and rooting was tough enough even with the Nexus Root Toolkit.
Thanks
Click to expand...
Click to collapse
Transfer zip to a pc Open up the zip file with winrar or 7zip there is a meta inf folder find the updater script file open with notepad erase the first line it will say something like asset get prop ect...... save the file transfer back to tablet it will now flash. Or use cwm to flash. I can do it for you if u send me the updater script file.
Even I have the same problem and if you flash a modded zip, TWRP and CWM give an error with no specified status number. I even tried signing the zip
EDIT: Install CWM and toggle signature verification. Simple right?
Press thanks if I helped.?
b3ltazar said:
Transfer zip to a pc Open up the zip file with winrar or 7zip there is a meta inf folder find the updater script file open with notepad erase the first line it will say something like asset get prop ect...... save the file transfer back to tablet it will now flash. Or use cwm to flash. I can do it for you if u send me the updater script file.
Click to expand...
Click to collapse
Thanks for the help. Unfortunately I got a tad frustrated and accidentally deleted EVERYTHING!!! So I have blank tablet now. I'm trying to download the Google Factory Images from their site but it only downloads this .tgz file instead of a zip with 4 files. I even tried extracting the .tgz and it give me a single file. Anyone have any ideas as to why this is?
I'm trying to restore this tablet based on following this page (can't post outside links on this site until after 10 posts?.......really?)
But as you can imagine I'm stuck because I can't download the aforementioned zip file.
My tablet is soon becoming destined to be a rifle target.
BAM!!! Never mind got it all squared away. Now if we can get that ROM set up so that it will work properly.
Androlover98 said:
Even I have the same problem and if you flash a modded zip, TWRP and CWM give an error with no specified status number. I even tried signing the zip
EDIT: Install CWM and toggle signature verification. Simple right?
Press thanks if I helped.?
Click to expand...
Click to collapse
I used CWM to load the ROM no problem. Thanks for the heads up.
So far I''m loving this PACMan ROM, smooth and tons of options. For me KitKat ruined my tablet, completely breaking the auto-rotate (making is stick in portrait mode), chrome crashed all the time and it was just generally laggy and slow.
Thanks to all that replied.
ST2014 said:
I used CWM to load the ROM no problem. Thanks for the heads up.
So far I''m loving this PACMan ROM, smooth and tons of options. For me KitKat ruined my tablet, completely breaking the auto-rotate (making is stick in portrait mode), chrome crashed all the time and it was just generally laggy and slow.
Thanks to all that replied.
Click to expand...
Click to collapse
Kitkat should work with no issues. i use slimkat 4.4.2 and i love it. Just make sure you wipe before the kitkat install and your tablet will fly.
b3ltazar said:
Kitkat should work with no issues. i use slimkat 4.4.2 and i love it. Just make sure you wipe before the kitkat install and your tablet will fly.
Click to expand...
Click to collapse
Exactly. Nothing beats KitKat. PERIOD
Sent from my Nexus 7 using Tapatalk
Hi XDA,
Before I decided to open this topic I've read through several topics, but I can't seem to find out what I am doing wrong. I hope that opening this thread will help me solving my problem.
I have a Dutch Samsung Galaxy S4 (i9505) running Android 5.0.1 Lollipop using the Nova launcher, but I'd like to install a ROM for new features and better battery life. After looking around in the development forum I found two interesting ROMs which I wanted to try out. These are the following:
http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-imperium-ll-v1-0-t3046889
Or
http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-albe95-s6-port-1-0-t3092479
I downloaded the zip file from the first ROM listed and copied it to my SD-card
Both seemed like decent ROMs. I looked up how to root my phone and found out that by using Odin this was pretty easy. After rooting my phone I used QuickBoot to enter Recovery mode. After wiping the DATA I chose update through SD Card > selected the zip file and thought it would install from that moment.
After waiting several minutes the ROM seemed to be installed, the phone rebooted itself and after seeing the swingy SAMSUNG logo it said SYSTEM-UI has stopped. I was able to use all functions, aside from the taskbar, homebutton and backbutton. Also, it seemed like nothing changed? My phone was exactly the same, aside from the fact that my background was black.
I am confused where I am making a mistake by installing either ROM. Can anyone point me out where I make the mistake and tell me how to solve my problem.
Thank you.
If there's any other info neccesary please don't hesitate to ask, i'm happy to provide!
Did you actually install any custom recovery?
You need a custom recovery to install any custom roms. It won't work with the stock recovery.
I'd recommend TWRP recovery. It can also be installed via Odin.
I did, but maybe something went wrong. I am back on the normal ROM now, just rooted the device using http://forum.xda-developers.com/showthread.php?t=2219803 this thread.
I Will try installing twrp again. Can I use one of the following despite not being in the USA? How do I know for sure?
Samsung Galaxy S4 AT&T (jflteatt)
Samsung Galaxy S4 Canada (jfltecan)
Samsung Galaxy S4 Cricket (jfltecri)
Samsung Galaxy S4 C-Spire (jfltespi)
Samsung Galaxy S4 Google Edition (jgedlte)
Samsung Galaxy S4 International Exynos (i9500)
Ok, installed TWRP and copied the zip files to both my SD card as well as the internal hd, going to install, finding the zip files, swipe to install. Following happens:
Installing '/external_sd/imperium_ll_blabla.zip
Checking for MD5 file
Skipping MD5 chekc: no MD5 file found
Verifying zip signature
E: Zip signature verification failed: 1
FAILEd.
I'm confused.
mess89 said:
Ok, installed TWRP and copied the zip files to both my SD card as well as the internal hd, going to install, finding the zip files, swipe to install. Following happens:
Installing '/external_sd/imperium_ll_blabla.zip
Checking for MD5 file
Skipping MD5 chekc: no MD5 file found
Verifying zip signature
E: Zip signature verification failed: 1
FAILEd.
I'm confused.
Click to expand...
Click to collapse
Disable zip signature verification and try again.
Make sure you use the latest TWRP recovery. CWM and Philz are highly outdated.
Thanks for the tips guys. I will try on sunday, don't want to mess with my phone during birthday parties
I will let you know about the results.
Please do a clean flash when you're installing a new ROM.
Clean as in delete cache, dalvik, system, and if needed, internal storage.
krasCGQ said:
Disable zip signature verification and try again.
Click to expand...
Click to collapse
That's where I went wrong, thanks guys!
Hi,
I have rooted my Nexus 7 and installed TWRP, but when tried to flash slimkat 4.4.4 it failed with error message "set_metadata:recursive: some changes failed". An important details was that I did this after a couple of glasses of wine (genious, i know) and of course I messed up and did a backup after the my first attempt at flashin the slimkat rom, so restoring the back up is no good. I did all of this from the device itself, except the OEM unlocking.
How do I access the the Nexus 7 and add other rom files in the state it is now. I can see that Android filemanager in OSX detects it when I try to start normally, but is not able to gain access, then the device goes to TWRP
How do I move forward from here? I guess I need to get a nother rom zip file to flash, but I'm not sure.
I want to have lightweight custom rom, before trying to flach slimkat my Nexus 7 was on android 5.1.1 and it was not really usable. My goal is to use the device for not heavier than kitkat, please help me.
------------------------------------------------------------
format and mount systems, mount system data...
symlinks and permissions...
set_metadata:recursive: some changes failed
E: error in sdcard/download/slim.grouper-4.4.4.build.9.0.-OFFICIAL-8258.zip
(status 7)
Error flashing zip 'sdcard/download/slim.grouper-4.4.4.build.9.0.-OFFICIAL-8258.zip
updating oartition details
------------------------------------------------------------
Details:
device: Nexus 7 grouper
rom that failed: slim.grouper-4.4.4.build.9.0.-OFFICIAL-8258.zip
TWRP ver. 2.4.4.0
Computer OS: Ubuntu 16.04
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 there. I had recently updated my p9 lite to android nougat from VNS-L31C440B132 single sim to VNS-L31C440B380 with the official uk ee firmware and was absolutely in love with it so far. I had installed magisk and viper4audio with but i wanted to see what other mods like dolby atmos and xtrememusic could do so i added the audio modification library mod so i use multiple mods at once. Dolby Atmos was pretty unresponsive and time i did manage to open it it immediately crashed so i unistalled it and tried out xtrememusic and this is where the problems really began. when i tried to play videos on apps like facebook and youtube they wouldn't load, the video would buffer but it didn't play and on facebook some videos did load and strangely music apps like would play music but i couldn’t hear anything but sound came out of my phone’s music player, i thought the sound mod was messing up so i looked for an uninstaller and found one androidfile host. I booted into TWRP (Openkirin edition), flashed it, and rebooted. I was met with a black screen and the phone was trapped in a bootloop and booted to a screen that told me to do a factory reset which then led into my tarp;I realised the phone got soft-bricked I panicked at this point and the reset didn’t and went back into twrp to try and flash any other versions of the mods to see if it would clear up the problem but it didn’t. I tried to format data but was met with: ‘mkfs.f2fs -t 0 /dev/block/mmcblk0p49 process ended with error: 255’ so I had to go back then i tried to see if i could dirty flash the rom as i still the original firmware i used to update my phone and the stock rom before the update, should’ve realised that wasn’t the best idea; I failed trying to install the main package but the ota update installed with no problems. I booted up the it still wasn’t loading (at this point I had already done a factory reset via twrp and data cache and dalvik) so i decided to see if i could clear the system and then re-install the b380 rom. every attempt i made was unsuccessful as twrp kept saying ‘failed to mount data (device or resource busy)’ or other problems like ‘could not mount /data and unable to find crypto footer’. Eventually I got to where I am now by completely erasing cache, data, system and storage. As there’s absolutely nothing on the phone now as i am on B380 can i just push the nougat firmware to /sdcard/ via adb on my mac and install it as is it or failing that is there any way I can downgrade to L31C440B132? I know to downgrade you need to download an intermediary package specific to your phone build but i looked and I can’t find one for the L31C440 range; I’ve checked Huawei’s official uk support site but the firmware is listed as C900B3000 and my build number isn’t listed. I’m worried that if i do manage to rollback to that specific firmware I won’t be able to restore my VNS-L31C440B132 rom to the phone as it may be rendered incompatible. At the very least I want to know if I can restore the from the nougat rom + update or a sim toolkit i can use to change my oeminfo to C440 and then install my stock firmware. Another thing this is the ota package i flashed: update_data_full_VNS-L11_ee_gb.zip, it says VNS-L11; please let me know if that is going to complicate restoring the rom. Thank you.
Update: I have managed to repair my data partition by doing another factory reset and changing the file system from f2fs to ext4 and the phone is seemingly in a normal state but every time I try to reinstall the main update.app package i get:
Updating partition details...
..done
Installing zip file '/sdcard/update.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Removing unneeded files...
Removing empty directorys...
Patching system files...
Unpacking new files...
add link type file...
write radio image...
32K crc checked failure
E:unknown command [errno]
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
However the other file, update_data_full_VNS-L11_ee_gb.zip installs just fine:
Updating partition details...
..done
Installing zip file ‘/sdcard/update_data_full_VNS-L11_ee_gb.zip’
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Verifying current userdata…
mountencrypt: failed to mount /data: Success
Removing unneeded files...
Removing empty directorys...
Patching system files...
Unpacking new files...
add link type file...
write radio image...
script succeeded: result was []
Updating partition details...
...done
I'm completely stuck now and really don't know where to go from here as only the other smaller package seems to install but when i try the reboot option it gives me ’no os installed! are you sure you want to reboot?’; should i change the data partition filesystem back to f2fs or is something else wrong with the install? This has been incredibly fruatrating for me. back when i was on marshmallow if i had problems rom-wise, all i had to do was advanced wipe and then just reflash my L31C440B132 stock rom with no problems but now i'm stuck in a real mess as the original rom which i updated to 7.0 is also gone so I've basically got a phone that's upgraded to C440B380 with no firmware at all; I can still boot into twrp but it can't really do anything significant atm. I would like to try debranding it through the rollback package on the official huawei support site but i'm not sure how I can convert my phone's oem info back to VNS-L31 single-sim C440 afterwards. any advice you guys have would be extremely helpful now, especially finding a rollback package to match my build number.
I have been in a similar situation before, but my region is c440 (I changed from c432). I used the C900B300 rollback package in the dload folder on my sd card and updated by the three-button method. I then put the VNS-L31C432B161 update in the dload folder and updated by the three-button method again. Maybe this will work with C900B300 and C440B132?
Jaiket78 said:
I have been in a similar situation before, but my region is c440 (I changed from c432). I used the C900B300 rollback package in the dload folder on my sd card and updated by the three-button method. I then put the VNS-L31C432B161 update in the dload folder and updated by the three-button method again. Maybe this will work with C900B300 and C440B132?
Click to expand...
Click to collapse
Like I said i'm being very cautious about about what to do next but how did you manage to change regions btw?
I used the toolkit and oeminfo files from the following link to change the region.
toolkit
Official systems are not for twrp instal! Unpack update.zip and you will get UPDATE.APP, put that in dload folder then on sd card, switch off device, disconnect any cables, hold vol- , vol+ and power button untill installation starts...
Hey man. I am in the exact same situation as you. Have you solved the problem yet?