Related
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
TWERP failed flash message
blairan said:
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
Click to expand...
Click to collapse
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
blairan said:
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
Click to expand...
Click to collapse
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
i'm part way there...
tdhite said:
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
Click to expand...
Click to collapse
OK, I have downloaded the 2 files. placed them in a directory near my root directory on my pc. placed the phone in fastboot usb, opened a command prompt window from that directory. typed in fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014
and I get error: cannot load 'fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014'
per a video showing how to flash recovery, I also tried the command adb reboot bootloader I get error : device not found
back to my pc, I open device manager, and I show a device labeled android device that is working properly.
stumped at this point.
is updating recovery the same as the initial install of a custom recovery?
do I need updated drivers for win 7? where are the latest? all videos say they are the latest, but that was when they were recorted.
thanks for help!
Yes u need updated drivers....any easy solution however is go and get the app flashify u will need root of course...it allows u to flash recovery that is on ur sd card. Just choose the img and flash recovery in the app then reboot into recovery and u will be good to go.
Sent from my HTCONE using Tapatalk
Thank you!
Thanks to both of you, updated TWERP did the trick and Flashify allowed me to install it without the fastboot, and PC hookup which was not working. Latest nightly installed, I am a happy camper!
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Slagathor01 said:
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Click to expand...
Click to collapse
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
luigi311 said:
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I got it with fastboot, I forgot I re installed windows since I did it initially, so I was pulling my hair out wondering why fastboot wouldnt see it, and I couldnt even get files to or from it till I installed HTC sync.....heh
thanks for the info.....
I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
Code:
E:footer is wrong
E:signature verification failed
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Deleted
Anyone have any suggestions?
Bump
Someone has to have some sort of suggestions I could try... would flashing a custom rom on do anything or is this related to the KNOX security stuff?
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Nergal di Cuthah said:
Are you using twrp? if so, did you turn off zip verification and md5 verification?
Click to expand...
Click to collapse
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
lordofbeond said:
i am using twrp manager 9.0 (from the play store) but i didn't see a place/option to disable the verification. is there a different app i should be using or am i overlooking something obvious?
edit: I've also tried CWM and i get the same errors
Click to expand...
Click to collapse
Not in manager in actual twrp
Nergal di Cuthah said:
Not in manager in actual twrp
Click to expand...
Click to collapse
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
This thread is probably your answer
lordofbeond said:
I wasn't aware of the install twrp step which answers most of the questions I have about this.
I tried it and softbricked my device. Did a little more research and it looks like the kernel I have won't allow me to install TWRP. I'm trying to use verizion's recovery tool to downgrade/repair the device and I'll see if I can get this device rolled back and TWRP installed.
Thank you for the info, this gives me a launching point at least. I'll check back here if/when I get TWRP installed and I try to disable the validation.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-framework-install-galaxy-s4-sch-t3425615
lordofbeond said:
I have a Samsung Galaxy S4 (verizon SCH-I545) running android 5.0.1
I have already rooted my device using KingRoot
I have been trying to flash the xposed zip file for several days now and I'm not having any luck. I've tried a few different tools to flash but they all kick me to bootloader but fail to flash the zip. I get the following error when bootloader is verifying the update package:
I've tried putting the zip file on my device and on SD to see if that might help, but still no dice. Does anyone have suggestions or know what I'm doing wrong? I'm using the most recent zip from XDA (xposed-v86-sdk21-arm.zip updated 08-Jul-2016 15:25... I've also tried arter97's package and dkcldark's package as well as Magisk v1)
Click to expand...
Click to collapse
Hola. i just did this on vz GS4 i545:
use FlashFire for everything. make sure you have a titanium backup of your apps and data for after you flash new ROM. here are the steps:
1. Flash Fire Zip or OTA stock of1 deodexed ROM from here: http://forum.xda-developers.com/gal...1-keeproot-t3182544/post62413212#post62413212
it will spend 10 to 15 minutes on the red Verizon splash screen.
2. reload from titanium at this point.
3. install xposed 3.0alpha4.apk from the xposed forum page.
4. flashfire zip or ota Arter97's xposed v65 sdk21 arm arter97 V5 krait.zip
this last step took about 35 minutes to upgrade all 260 plus apps i have.
make sure you have the proper uninstaller loaded too just in case. i put mine on the ext sd card in case i needed to load it from recovery. though that might not work because of the unsigned issue.
Hi, I'm new to this forum.
I have a problem with my phone.
After rooting it was good, but later I wanted to upload another ROM and confused the versions to the Snapdragon processor than HiSilicon and now I don't have a baseband and IMEI.
I have tried the original 6.0, 5.1 trough adb-fastboot, because I can't restore trough dload, I had message 'Install software failed' and nothing helps.
Do you have any ideas?
moczu17 said:
Hi, I'm new to this forum.
I have a problem with my phone.
After rooting it was good, but later I wanted to upload another ROM and confused the versions to the Snapdragon processor than HiSilicon and now I don't have a baseband and IMEI.
I have tried the original 6.0, 5.1 trough adb-fastboot, because I can't restore trough dload, I had message 'Install software failed' and nothing helps.
Do you have any ideas?
Click to expand...
Click to collapse
I don't know, but maybe @MarcoPLs or @panchovix has an idea? Sorry to quote you guys, but this is a quite important question: What if someone flashes the wrong rom? Honor 4x can be confusing with snapdragon/kirin versions.
Bob1900 said:
I don't know, but maybe @MarcoPLs or @panchovix has an idea? Sorry to quote you guys, but this is a quite important question: What if someone flashes the wrong rom? Honor 4x can be confusing with snapdragon/kirin versions.
Click to expand...
Click to collapse
Flashing sd rom is 100% brick.
Try to use rollback package and then reflash lollipop. (you can also try to flash marshmallow with updateappflasher but i think it flash only stuff you need to boot)
http://www.hihonor.com/uk/support/details/index.html?DOC_ID=82283
moczu17 said:
Hi, I'm new to this forum.
I have a problem with my phone.
After rooting it was good, but later I wanted to upload another ROM and confused the versions to the Snapdragon processor than HiSilicon and now I don't have a baseband and IMEI.
I have tried the original 6.0, 5.1 trough adb-fastboot, because I can't restore trough dload, I had message 'Install software failed' and nothing helps.
Do you have any ideas?
Click to expand...
Click to collapse
If you can boot to TWRP use this method to install stock rom.
https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702
keikari said:
If you can boot to TWRP use this method to install stock rom.
https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702
Click to expand...
Click to collapse
I think using stock recovery is better for fixing bugs because it flash all partitions
MarcoPLs said:
I think using stock recovery is better for fixing bugs because it flash all partitions
Click to expand...
Click to collapse
If you install with that you can have easier access to use dload method.
MarcoPLs said:
I think using stock recovery is better for fixing bugs because it flash all partitions
Click to expand...
Click to collapse
I tried to use rollback, but always durning instalation from dload 'Instal software failed'...
I tried too method with TWRP, but durning instalation:
' unmounf of /system failed; no such volume
unmounf of /cust failed; no such volume
write radio image...
E:unknow command [errno]
Updater process ended with ERROR: 7 '.
I'm worried...
moczu17 said:
I tried to use rollback, but always durning instalation from dload 'Instal software failed'...
I tried too method with TWRP, but durning instalation:
' unmounf of /system failed; no such volume
unmounf of /cust failed; no such volume
write radio image...
E:unknow command [errno]
Updater process ended with ERROR: 7 '.
I'm worried...
Click to expand...
Click to collapse
Flash system and cust with fastboot and use twrp flasher again.
(rollback is not full update, you have formated system thats why it also failed)
MarcoPLs said:
Flash system and cust with fastboot and use twrp flasher again.
(rollback is not full update, you have formated system thats why it also failed)
Click to expand...
Click to collapse
OK, done, but I still can't install rollback and stock ROM.
Now I only have:
'write radio image...
E:unknow command [errno]
Updater process ended with ERROR: 7 '.
moczu17 said:
OK, done, but I still can't install rollback and stock ROM.
Now I only have:
'write radio image...
E:unknow command [errno]
Updater process ended with ERROR: 7 '.
Click to expand...
Click to collapse
unknow command is nornal.
im not sure what status 7 could be. you are not trying to flash rollback with twrp? with twrp you can only flash full roms
I tried flash rollback from dload, but failed.
I tried flash full stock rom MM b535 trough TWPR, but failed, so I don't know...
I must trying with other rom or meta-inf is wrong?
It works!
I extract META-INF in Huawei Multi-Tool and install rollback in TWRP, but I still didn't have baseband and IMEIs.
I flashed 6.0 B535 trough adb.
Extract from update.app and flash, flash, flash *.img.
Only full packages work, so thanks for Your help!
moczu17 said:
It works!
I extract META-INF in Huawei Multi-Tool and install rollback in TWRP, but I still didn't have baseband and IMEIs.
I flashed 6.0 B535 trough adb.
Extract from update.app and flash, flash, flash *.img.
Only full packages work, so thanks for Your help!
Click to expand...
Click to collapse
Have you restored your IMEI numbers or not?
If not flash stock ROM which you got with your device.
Yes, I have restored my IMEI.
moczu17 said:
Yes, I have restored my IMEI.
Click to expand...
Click to collapse
how did you get succeeded by flashing stock rom or any other?
moczu17 said:
Yes, I have restored my IMEI.
Click to expand...
Click to collapse
Can you let us know how you were able to solve this ?
I wrote, that I flashed rom 6.0 B535 trough adb.
I extracted file update.app in huawei extractor and manually flashed images.
Only full packages work...
moczu17 said:
I wrote, that I flashed rom 6.0 B535 trough adb.
I extracted file update.app in huawei extractor and manually flashed images.
Only full packages work...
Click to expand...
Click to collapse
Ya,sure it is one of the best way to regain lost phone information.
moczu17 said:
I wrote, that I flashed rom 6.0 B535 trough adb.
I extracted file update.app in huawei extractor and manually flashed images.
Only full packages work...
Click to expand...
Click to collapse
Glad u sorted things on your own .hope to see u helping someone in future. Goodluck
moczu17 said:
I wrote, that I flashed rom 6.0 B535 trough adb.
I extracted file update.app in huawei extractor and manually flashed images.
Only full packages work...
Click to expand...
Click to collapse
please edit the title and write as [solved ] in front of the question
Hi everyone,
Just taking my chances if anyone in here encountered the same issue. I'm currently on EVA-L19C636B381 and the System Updater is asking me to update to B390. However, I've tried downloading the update several times but keep on getting the "Software Install Failed" error message. Any ideas on how I can update the firmware and ensure that updates will be installed seamlessly moving forward?
Note that the bootloader was unlocked before and it used to have TWRP. Now I've relocked the bootloader and installed the stock recovery.
Thanks!
Clarification:
Version: EVA-L19C636B381 (everything's stock: BOOT, RECOVERY, RECOVERY2, SYSTEM)
Would like to update to: B390
Issue: Getting "Software install failed" error message after downloading through System Update
** Used to have TWRP and root. Flashed stock IMGs
Update:
Issue solved! Please see last post for the update/solution.
thedarkinvader said:
Hi everyone,
Just taking my chances if anyone in here encountered the same issue. I'm currently on EVA-L19C636B381 and the System Updater is asking me to update to B390. However, I've tried downloading the update several times but keep on getting the "Software Install Failed" error message. Any ideas on how I can update the firmware and ensure that updates will be installed seamlessly moving forward?
Note that the bootloader was unlocked before and it used to have TWRP. Now I've relocked the bootloader and installed the stock recovery.
Thanks!
Click to expand...
Click to collapse
If you had TWRP, maybe you also rooted - root will also block OTA (you had to unroot in that case).
Btw, unlocked bootloader does not prevent/affect OTA
zgfg said:
If you had TWRP, maybe you also rooted - root will also block OTA (you had to unroot in that case).
Btw, unlocked bootloader does not prevent/affect OTA
Click to expand...
Click to collapse
Hi zgfg!
Thanks for the response. Yeah, if I'm not mistaken, it used to be rooted. However, I've installed stock B381 and stock recovery already, and still getting the error message. Checked with Root Checker and it says that there's no root access.
thedarkinvader said:
Hi zgfg!
Thanks for the response. Yeah, if I'm not mistaken, it used to be rooted. However, I've installed stock B381 and stock recovery already, and still getting the error message. Checked with Root Checker and it says that there's no root access.
Click to expand...
Click to collapse
Rooting affects Boot partition, it must be flashed back to stock. And it's recommended to Hard reset then, before OTA. For OTA, go to Settings, and choose Full upgrade
zgfg said:
Rooting affects Boot partition, it must be flashed back to stock. And it's recommended to Hard reset then, before OTA. For OTA, go to Settings, and choose Full upgrade
Click to expand...
Click to collapse
Yeah, that's what I did. Basically, everything's stock already. That's why I don't understand why I'm still getting the error message.
You can try downloading the full stock rom package and manually update with the dload method.
noalt said:
You can try downloading the full stock rom package and manually update with the dload method.
Click to expand...
Click to collapse
Hi noalt! Thanks for the response.
Yeah, kinda wondering if that'll work. For the dload method, does it really require an SD card? Also, for the dload method, it is okay to get the latest full package instead? (Upon checking using Firmware Finder, the latest one is B395 or B396)
Any steps that I can follow to do a sort of "clean install"? As in free of any modifications? In short, some kind of steps as alternative for using System Update (which I can't use due to the error message I'm getting)?
You can use any stock rom you like. If it is the same or higher build, you may not need to do a rollback. The dload method only works from sd-card. It will be a clean install.
I think the dload method is the safest. Alternatives are flashing images indiviually through fastboot but I have no experience with that, except for the recovery.img
noalt said:
You can use any stock rom you like. If it is the same or higher build, you may not need to do a rollback. The dload method only works from sd-card. It will be a clean install.
I think the dload method is the safest. Alternatives are flashing images indiviually through fastboot but I have no experience with that, except for the recovery.img
Click to expand...
Click to collapse
I see. Regarding the dload method, if by sd-card you're referring to the internal memory, I'm afraid I've tried that (creating a dload folder and putting nothing else but the UPDATE.APP file inside) and I'm getting a Software Install Failed error message as well. :crying:
No, I mean a micro sd card. You can put one in the tray next to your sim card. And then you have to shut down you phone and boot it holding vol+ vol- and power until you get into the updater.
noalt said:
No, I mean a micro sd card. You can put one in the tray next to your sim card. And then you have to shut down you phone and boot it holding vol+ vol- and power until you get into the updater.
Click to expand...
Click to collapse
Ah yes, that's the one that I have yet to try (as I don't have an SD card, the other spare phone that I have is a 5s).
UPDATE:
I eventually was able to install EVA-L19C363B395!
Initially, I was having issues with the partitions (as I tinkered around a bit with TWRP) and was stuck with the Huawei logo and not proceeding with the booting. So what I did was I flashed BOOT.img, SYSTEM.img, RECOVERY.img, and RECOVERY2.img from the stock B381 (use the Huawei Update Extractor to get it from the UPDATE.APP file from the update.zip (the large file), do some Googling to find it here in XDA . Then I was still experiencing the said issue so I used the stock recovery's features: "Wipe data/factory reset" and "Wipe cache partition" to sort of repair the issues with the partitions (didn't know how to properly do it in TWRP.
Then B381 booted and was able to access USB debugging (initially had issues with this as well, after flashing images, Settings app kept on crashing when trying to access Security and Developer options).
And then finally followed the HWOTA procedure made by @Atarii. Make sure that you're going to use the proper recovery file for your version (L09, L19, etc). According to the steps, being rooted is also required so I used @zgfg's SuperSU 2.82 permissive (https://mega.nz/#F!w41RmZKB!IG53JadhjUKgFK8anbctIw). Make sure to flash it before flashing the nocheck recovery file.
And voila! That should do it. Based on what I'm seeing, root has been removed after doing the HWOTA procedure, same goes for TWRP, and bootloader's locked again.
Thanks to all of those who responded and credit goes to @Atarii and @zgfg for the procedure and file/link.
After installing TWRP and rooting my device on the latest firmware N950FXXU5CRHA,
I get an error message when I power on the device and it won't boot up
(Only official released binaries are allowed to be flashed)
I got root working but when I try to restart it, I always ended up getting that message and I need to flash again the official firmware and losing my root again
any solutions for this? :crying:
upbeatwrench said:
After installing TWRP and rooting my device on the latest firmware N950FXXU5CRHA,
I get an error message when I power on the device and it won't boot up
(Only official released binaries are allowed to be flashed)
I got root working but when I try to restart it, I always ended up getting that message and I need to flash again the official firmware and losing my root again
any solutions for this? :crying:
Click to expand...
Click to collapse
After flashing TWRP and rebooting you have to delete "securitylogagent" in system/app before rebooting again.
stonedpsycho said:
After flashing TWRP and rebooting you have to delete "securitylogagent" in system/app before rebooting again.
Click to expand...
Click to collapse
I deleted "securitylogagent in system/app but when I restarted my phone, I still got that errror. But anyways, I did install a custom rom on my phone to obtain root without any problems
Sent from my SM-N950F using Tapatalk