Hello,
My beloved Sprint Note 3 died on me today. After rebooting, it kept repeating an error message (should of written it down).
I used Odin3 v1.85 to install TWRP v2.8.7.0. That all seemed to work fine.
Using TWRP, I did an advanced wipe and cleared "Dalvik Cache", system, Data, and Internal Storage"
Then I attempted to install Freeza's "Galaxy-Note-frez-3-2.26.zip"
I get the error message:
"E:Error execting updater binary in zip '/external_sd/Galaxy-Note-fre3-2.26 zip'
and
Error flashing zip '/external_sd/Galaxy-Note-fre3-2.26 zip'
Any ideas what I should try?
Thanks!
Brandon
brranndon said:
Hello,
My beloved Sprint Note 3 died on me today. After rebooting, it kept repeating an error message (should of written it down).
I used Odin3 v1.85 to install TWRP v2.8.7.0. That all seemed to work fine.
Using TWRP, I did an advanced wipe and cleared "Dalvik Cache", system, Data, and Internal Storage"
Then I attempted to install Freeza's "Galaxy-Note-frez-3-2.26.zip"
I get the error message:
"E:Error execting updater binary in zip '/external_sd/Galaxy-Note-fre3-2.26 zip'
and
Error flashing zip '/external_sd/Galaxy-Note-fre3-2.26 zip'
Any ideas what I should try?
Thanks!
Brandon
Click to expand...
Click to collapse
I used to have this issue with Freeza's ROM as well, not sure why.... but just try a different ROM before you declare a time of death.
Thanks poncholo36. I installed a stock OS using Odin and that worked fine. What ROM are you using?
brranndon said:
Thanks poncholo36. I installed a stock OS using Odin and that worked fine. What ROM are you using?
Click to expand...
Click to collapse
You could try mine, just click the 4.4.4 N K4 in my signature. Or try chaz187 Classic 4.4.4 NH7. . . However this would depend on what stock OS you installed. If It was Lollipop 5.1.1 you will have to flash back to stock 4.4.4 NK4 first, or you my end up with a bootloop. There is not a lot of custom roms based on Lollipop 5.1 as yet.
brranndon said:
Thanks poncholo36. I installed a stock OS using Odin and that worked fine. What ROM are you using?
Click to expand...
Click to collapse
Cool glad that worked out for you man. I'm running the latest CyanogenROM nightly right now...
http://forum.xda-developers.com/showthread.php?t=2599669
Related
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
Here is a link on what error im getting (after installing some ROMs) only on this Baseband I605VRUEMJ9 I get this error I use to be able to install any kind of ROM but after I605VRUEMJ9 update I can't install some ROMs. I can some ROMs but not all the error I get it says i'm losing Root after successfully installing a ROM (I get no errors installing a ROM) but after I swipe dalvik & cache it says I have lost root and TWRP says if it will fix my root but it doesn't I've stayed on Samsung NOTE II sign for more than 10 minutes and nothing i've also installed the latest SUPERSU zip file after installing a ROM and still nothing can anyone tell me what i'm doing wrong or what I need to do please,,, thanks in advance!!!!
https://www.dropbox.com/s/hskv5j7gjlhq99r/2014-02-07 03.00.53.mp4
Do you have the latest TWRP?
MunkinDrunky said:
Do you have the latest TWRP?
Click to expand...
Click to collapse
Yes sir I do have latest TWRP.
Recently i was trying to install custom rom "du_n7000_v.7.0_20140411.zip" on to my note GT N7000, initially i got an error saying status 7.
after that i searched for the same error and got a solution, asking to delete couple of lines from the script file after unzipping the zip file.
I deleted the extra lines which were causing the status 7 error, after that i got Verification Error, and none of the 4.4 roms can be installed or ported on to my GT N7000 device.
IF there is any other way than please do let me know.
Thanking in Advance.
djp007s29 said:
Recently i was trying to install custom rom "du_n7000_v.7.0_20140411.zip" on to my note GT N7000, initially i got an error saying status 7.
after that i searched for the same error and got a solution, asking to delete couple of lines from the script file after unzipping the zip file.
I deleted the extra lines which were causing the status 7 error, after that i got Verification Error, and none of the 4.4 roms can be installed or ported on to my GT N7000 device.
IF there is any other way than please do let me know.
Thanking in Advance.
Click to expand...
Click to collapse
Which recovery and version are you using? You need one that has SELinux support for KK roms. Also, it's recommended to also factory reset your phone after installing the rom and gapps for KK roms, according to the Omni thread for N7000.
Samsung GT N7000
es0tericcha0s said:
Which recovery and version are you using? You need one that has SELinux support for KK roms. Also, it's recommended to also factory reset your phone after installing the rom and gapps for KK roms, according to the Omni thread for N7000.
Click to expand...
Click to collapse
I am using CWM v6.0.3.3. i also used the advance Touch CWM recovery but still i am not able to install 4.4 roms, 4.3 is not a problem at all, it gets installed without any problems, but when i try to install 4.4 roms it gives error of " Status 7"
Thanking you for your prompt reply. If there is any solution for it than do let me know.
It's definitely your recovery. That version came out in middle of last year and Kit Kat & SELinux being necessary wasn't a thing. You need one of the newest recoveries from CWM, Philz Touch (modded CWM - if you like CWM, you'll probably like Philz better), or TWRP.
Samsung GT N7000
es0tericcha0s said:
It's definitely your recovery. That version came out in middle of last year and Kit Kat & SELinux being necessary wasn't a thing. You need one of the newest recoveries from CWM, Philz Touch (modded CWM - if you like CWM, you'll probably like Philz better), or TWRP.
Click to expand...
Click to collapse
I used Philz touch (Advanced Touch CWM) but even after using Philz Touch, i get Status 7 Error and after removing the mentioned files from script i get authentication error. And this error comes for all 4.4 Roms, if i install 4.3 through Philz Touch it gets installed like a charm, so now i really can not understand what exactly is the problem for installing 4.4 roms.
djp007s29 said:
I used Philz touch (Advanced Touch CWM) but even after using Philz Touch, i get Status 7 Error and after removing the mentioned files from script i get authentication error. And this error comes for all 4.4 Roms, if i install 4.3 through Philz Touch it gets installed like a charm, so now i really can not understand what exactly is the problem for installing 4.4 roms.
Click to expand...
Click to collapse
I'm not sure how to be more clear. The version of the recovery you are using is out of date. It's very simple. Update your recovery to something that has support for flashing 4.4 roms. It does not matter that 4.3 roms install fine with that recovery as 4.3 does not equal 4.4 and the install methods have changed somewhat. The only other time you are gonna get the Status 7 errors is when you are trying to install the rom that's built for another phone or version of the phone you are using and the updater-script has an assert to check the build.prop to make sure you install it to the right device. But update your recovery first and go from there.
es0tericcha0s said:
I'm not sure how to be more clear. The version of the recovery you are using is out of date. It's very simple. Update your recovery to something that has support for flashing 4.4 roms. It does not matter that 4.3 roms install fine with that recovery as 4.3 does not equal 4.4 and the install methods have changed somewhat. The only other time you are gonna get the Status 7 errors is when you are trying to install the rom that's built for another phone or version of the phone you are using and the updater-script has an assert to check the build.prop to make sure you install it to the right device. But update your recovery first and go from there.
Click to expand...
Click to collapse
I am downloading 4.4 roms from XDA Samsung Galaxy GT - N7000 , still i can not install the roms, if you have any 4.4 rom for Galaxy Note GT-N7000 than do let me know i would try to install that rom on to my Galaxy Note.
Appreciate your help on time.
Thanking you
Regards
Galaxy Note GT-N7000
djp007s29 said:
I am downloading 4.4 roms from XDA Samsung Galaxy GT - N7000 , still i can not install the roms, if you have any 4.4 rom for Galaxy Note GT-N7000 than do let me know i would try to install that rom on to my Galaxy Note.
Appreciate your help on time.
Thanking you
Regards
Click to expand...
Click to collapse
I have Successfully Installed du_n7000_v.7.0_20140411.zip.
Steps taken.
1. Wipe Cache Partition
2. Wipe Data/Factory reset
3.Advance/Wipe Dalvik Cache
Any body who gets Status 7 error, please follow these steps. Now i dont get Status 7 error or Authentication error and the rom got installed.
Regards
djp007s29 said:
I have Successfully Installed du_n7000_v.7.0_20140411.zip.
Steps taken.
1. Wipe Cache Partition
2. Wipe Data/Factory reset
3.Advance/Wipe Dalvik Cache
Any body who gets Status 7 error, please follow these steps. Now i dont get Status 7 error or Authentication error and the rom got installed.
Regards
Click to expand...
Click to collapse
This is basically the steps to take when installing any new custom rom. How WERE you trying to install the rom??
S1
es0tericcha0s said:
This is basically the steps to take when installing any new custom rom. How WERE you trying to install the rom??
Click to expand...
Click to collapse
The only thing i never did was step 1. Ie Wipe Cache Partition.
but without doing step 1, i was able to install all other versions of rom but could not instal 4.4 rom. when i did Wipe Cache Partition, i could install 4.4 Rom without Status 7 Error and also now not getting authentication error.
Regards
djp007s29 said:
The only thing i never did was step 1. Ie Wipe Cache Partition.
but without doing step 1, i was able to install all other versions of rom but could not instal 4.4 rom. when i did Wipe Cache Partition, i could install 4.4 Rom without Status 7 Error and also now not getting authentication error.
Regards
Click to expand...
Click to collapse
Ah ok. Well, the factory reset should also wipe the cache too, but it is not uncommon for Samsung's of this vintage to need extra wiping. Dunno why, but have seen it before.
I was just on the MJ9 firmware had no problem flashing other roms using TWRP. I read that TWRP was having issues flashing ND7 and seen that using Philz was the best thing to use, so I downloaded Philz and saved it, uploaded it to my external SD card along with the other required files for ND7. Rebooted to the recovery formatted the internal storage,dalvik and cache. First thing I did was try to install Philz. I instantly got failed and this message "assert failed: getprop (ro.product.device") I thought it had something to do with the Kitkat update. But, then I read on the forum that one user was having trouble installing Philz also and the user installed the ND7 first then Philz and it installed. So, I decided to try that. The update installed just fine but Philz still gave me the same error. I decided to try to install the radio that gave me the same error. I already had Liquid smooth 4.4 downloaded on my SD card and that wouldn't flash either but the gapps installed. I have installed the newest version of TWRP still no luck. I can't even use Airdroid to transfer to either SD card or internal storage (Later found out its an app problem). What else can I do to get the ball rolling?
DCVR 614 said:
I was just on the MJ9 firmware had no problem flashing other roms using TWRP. I read that TWRP was having issues flashing ND7 and seen that using Philz was the best thing to use, so I downloaded Philz and saved it, uploaded it to my external SD card along with the other required files for ND7. Rebooted to the recovery formatted the internal storage,dalvik and cache. First thing I did was try to install Philz. I instantly got failed and this message "assert failed: getprop (ro.product.device") I thought it had something to do with the Kitkat update. But, then I read on the forum that one user was having trouble installing Philz also and the user installed the ND7 first then Philz and it installed. So, I decided to try that. The update installed just fine but Philz still gave me the same error. I decided to try to install the radio that gave me the same error. I already had Liquid smooth 4.4 downloaded on my SD card and that wouldn't flash either but the gapps installed. I have installed the newest version of TWRP still no luck. I can't even use Airdroid to transfer to either SD card or internal storage (Later found out its an app problem). What else can I do to get the ball rolling?
Click to expand...
Click to collapse
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
gr8nole said:
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
Click to expand...
Click to collapse
That installed and worked. The ND7 Radio also installed. How do I fix the getprop asserts?
gr8nole said:
Seems like you still have the wrong TWRP for your device.
Here is a Philz Zip with the getprop asserts removed, so it should flash just fine in your current TWRP.
Click to expand...
Click to collapse
Okay, I got liquid smooth installed along with the gapps. Thank you for all your help. What can I do to get this get props corrected?
DCVR 614 said:
Okay, I got liquid smooth installed along with the gapps. Thank you for all your help. What can I do to get this get props corrected?
Click to expand...
Click to collapse
It is already fixed now that you have a proper i605 recovery installed.
Sent from my SCH-I605
gr8nole said:
It is already fixed now that you have a proper i605 recovery installed.
Sent from my SCH-I605
Click to expand...
Click to collapse
OH! Thank you so much. I appreciate your help!
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.