Database Users

[Q] SW Rev Check Fail fused 2 Binanary 1

hey
Could someone please please help me get my phone (sm-n9005) Back on. My phone has been off for the last 12 hours try to figure out how to restore back to stock. i am literrally pulling my hair out.
I keep getting this error message when restoring through odin SW REV CHECK FAIL: [ABOOT]FUSED 2 > BINARY 1
Please could someone tell me a fix for this i would really really really appreciate it.
Thank you

BUMP anyone pls

Are you trying to downgrade?
Little more info would probably help
SM-N9005 via Tapatalk 2

sewe said:
Are you trying to downgrade?
Little more info would probably help
SM-N9005 via Tapatalk 2
Click to expand...
Click to collapse
thanks for the reply
i just simply want to get the phone working
i orignally tried to flash from TGY hong kong firmware to BTU uk firmware, but that didnt work so i have tried to retry flashing the hong kong firmware
but odin gives me the [aboot] fused 2 > Binary 1 error
i tried doing emergency repair from kies too still gives me the same error

DjeMBeY said:
SW REV. CHECK FAIL : fused:2, Binary: 1 is when you try to downgrade aboot.mbn (bootloader) or try to flash incorrect system/csc etc..
If you get this message , just reboot in Download mode and flash correct package..
Click to expand...
Click to collapse
SM-N9005 via Tapatalk 2

sewe said:
SM-N9005 via Tapatalk 2
Click to expand...
Click to collapse
I am getting the same error when I try to flash back to the stock ROM and unroot my Verizon Note 3. I made the mistake of accepting the OTA update on my rooted device, did not have custom ROM or anything. The installation seemed to go okay but apparently wiped out the root. Everything was working fine but my root apps so I thought the device was essentially stock. I tried the Dela Vega Root method and it failed several attempts. So I tried flashing a stock ROM in Odin and I get the message you got. I tried downloading the stock ROM on two different occasions in case it was corrupted but still not working. Is my device bricked or is there something I can do? Any help would be appreciated.

Got my phone unbricked by following the directions in this thread. Installed pit file and my phone rebooted! Thank G-d! Was able to root with Kingo. De la vega root does not work with the firmware upgrade.

Back to life
I had same issue and restored it . Follow this : http://forum.xda-developers.com/showthread.php?t=2511880

Need Help
I need help too
Im having the same problem i have been trying for like 2 days now.
I tried to upgrade my phone to 4.4.2 but it didnt work and when i tried to flash back my old Rom im getting the same thing
"SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
need help want to fix my phone.
i tried three different roms and Odin came back with different errors. but errors the less.:crying:
Help:crying::crying::crying:

StarBoy007 said:
I need help too
Im having the same problem i have been trying for like 2 days now.
I tried to upgrade my phone to 4.4.2 but it didnt work and when i tried to flash back my old Rom im getting the same thing
"SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
need help want to fix my phone.
i tried three different roms and Odin came back with different errors. but errors the less.:crying:
Help:crying::crying::crying:
Click to expand...
Click to collapse
You cannot go back or restore an old ROM, you have upgraded to 4.4.2 with NA6 Bootloader, so you can ONLY Run NA6 Bootloader which means you are stuck on KitKat now..
Reflash Kitkat 4.4.2 Stock and you're good to go :good:

help
radicalisto said:
You cannot go back or restore an old ROM, you have upgraded to 4.4.2 with NA6 Bootloader, so you can ONLY Run NA6 Bootloader which means you are stuck on KitKat now..
Reflash Kitkat 4.4.2 Stock and you're good to go :good:
Click to expand...
Click to collapse
THanksfor the replay but the tjing is when i was installing kitkat Odin came up with an error and it failed so the upgrade didn't go through. So does it mean I'm stuck with kitkat. The thing is I tried 2 other kitkat and none of them worked. So when I tried to go back to my old ROM Odin always coming up. with errors. "FAIL (Auth)"
What does that mean..... :crying:

StarBoy007 said:
THanksfor the replay but the tjing is when i was installing kitkat Odin came up with an error and it failed so the upgrade didn't go through. So does it mean I'm stuck with kitkat. The thing is I tried 2 other kitkat and none of them worked. So when I tried to go back to my old ROM Odin always coming up. with errors. "FAIL (Auth)"
What does that mean..... :crying:
Click to expand...
Click to collapse
Yeah you'll have upgraded cause it'll have installed the Bootloader then tried the ROM before the failure. -
What model/region are you using ? Is it a HK note?

help
radicalisto said:
Yeah you'll have upgraded cause it'll have installed the Bootloader then tried the ROM before the failure. -
What model/region are you using ? Is it a HK note?
Click to expand...
Click to collapse
Ok no problem I understand
But I tried installing 4.4.2
But no luck it's not updating. Odin giving me errors every time
Do you have any idear when i can get a rom that can work for me
Plz
well i am using Hong Kong

1 Minute I will edit and give you link to fix your device :good:
Follow exactly these steps (I've fixed the second link.). Update progress.
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
Thanks to @rinuvimal posting here

I've updated working links here:
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://d-h.st/gb3
Download Sweet Rom and place it in ExtSDcard http://forum.xda-developers.com/showthread.php?t=2487425
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)

rinuvimal said:
I've updated working links here:
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://d-h.st/gb3
Download Sweet Rom and place it in ExtSDcard http://forum.xda-developers.com/showthread.php?t=2487425
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
Click to expand...
Click to collapse
@StarBoy007, after you try this out, please update your handset details and whether it worked for you. Cheers. Will help someone else!

thanks
rinuvimal said:
@StarBoy007, after you try this out, please update your handset details and whether it worked for you. Cheers. Will help someone else!
Click to expand...
Click to collapse
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:

StarBoy007 said:
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Try using PIT file, then re-flashing SweetROM, JackyawayROM or FlexKAT ROM

StarBoy007 said:
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Don't worry, as long as you can get into recovery and download modes, there will be a solution, its only a matter of time before we zone in on a solution.
What CSC region phone do you have? Dial *#1234# and check what the CSC code is. Also how much storage do you have on your phone 16Gb or 32GB?
R

thanks
rinuvimal said:
Don't worry, as long as you can get into recovery and download modes, there will be a solution, its only a matter of time before we zone in on a solution.
What CSC region phone do you have? Dial *#1234# and check what the CSC code is. Also how much storage do you have on your phone 16Gb or 32GB?
R
Click to expand...
Click to collapse
well thanks..
i know that the problem is not that big anymore its just getting the right rom. well i cant dial anything so i cant check for the CSC but im wondering is there any other way to get the CSC region well the phone was bought officially in hong kong.
do you have links to the other roms you suggested earlyer that would be helpful.
thanks again.

Nexus 4 kitkat update error

So I just got my OTA for 4.4 and downloaded the update. So I hit the restart and install button. The installing process ran like it supposed to be until the end part of it. The screen showed the word "error" with the android logo laying down. Then the phone just stayed like that and the screen not changing. So I decided to turn off the phone. Then I booted up the phone again, the google screen shows normally, but after that it shows the screen showing "no command" and I am stuck with that screen now and cannot go in. So I researched about it and find out I need to go to recovery mode. Then I hit the vol up and power button, then hit the recovery mode. But still, it shows the no command screen again.
Please help me... Thanks

Same issue here. Nexus 4 (rooted) OTA update from 4.3 to 4.4 failed. "No command" error. Please help

It's not pressing then together, have you tried this: http://forum.xda-developers.com/showpost.php?p=44388152&postcount=13

eksasol said:
It's not pressing then together, have you tried this: http://forum.xda-developers.com/showpost.php?p=44388152&postcount=13
Click to expand...
Click to collapse
It worked, now what do I do? I don't want to wipe all my data ._.
Is there a way to get the update and install it ?

GIANTLIZARDMAN said:
It worked, now what do I do? I don't want to wipe all my data ._.
Is there a way to get the update and install it ?
Click to expand...
Click to collapse
Check in the general section, there are a ton of info on this. i'll give you the links this time.
Follow the Scenario #1 instruction from here:http://forum.xda-developers.com/showthread.php?t=2145848
Or qbking77 video: http://forum.xda-developers.com/showthread.php?t=2537410

eksasol said:
Check in the general section, there are a ton of info on this. i'll give you the links this time.
Follow the Scenario #1 instruction from here:http://forum.xda-developers.com/showthread.php?t=2145848
Or qbking77 video: http://forum.xda-developers.com/showthread.php?t=2537410
Click to expand...
Click to collapse
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((

GIANTLIZARDMAN said:
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
Click to expand...
Click to collapse
Just watch the video and follow its instruction, you enabled the adb sideload command in the stock recovery. It has nothing to do with USB Debugging whatsoever.

eksasol said:
Just watch the video and follow its instruction, you enabled the adb sideload command in the stock recovery. It has nothing to do with USB Debugging whatsoever.
Click to expand...
Click to collapse
Followed the instructions shown in the video, but when I try to install the 4.4 update it gives me an error:
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Once again.... please help me.

GIANTLIZARDMAN said:
Followed the instructions shown in the video, but when I try to install the 4.4 update it gives me an error:
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Once again.... please help me.
Click to expand...
Click to collapse
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)

eksasol said:
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
Click to expand...
Click to collapse
Hi, I have tried both packages twice and re-downloaded them, and also wipe cache. I'm still getting the error status 7 installation aborted. I dont know what to do now. Please help im stuck.

I got it with the method in your sig. Flash factory image without wiping data (a different method) (short, if bootloader already unlocked). Thanks!

eksasol said:
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
Click to expand...
Click to collapse
tippingvan said:
Hi, I have tried both packages twice and re-downloaded them, and also wipe cache. I'm still getting the error status 7 installation aborted. I dont know what to do now. Please help im stuck.
Click to expand...
Click to collapse
GIANTLIZARDMAN said:
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
Click to expand...
Click to collapse
I'm having the same problem.
I had 4.2 stock (JOP40C).
I used NRT to unlock and root.
I then got an OTA update for 4.3 (JWR66Y, I believe) and lost root.
I was going to re-root, but received another OTA for 4.4, so I figured I'd install it before re-rooting.
Unfortuntately, I didn't re-enable USB debugging, which may be my current issue.
The install encountered an error (Android on his back and little red triangle).
Now I can't get past Recovery.
I tried installing 4.4 from JWR66Ymanually via adb using methods described here and get the status 7 message shown above.
If I try installing 4.4 from KRT160 I get an error indicating my device has the wrong keys (seems to imply not the right starting version for the upgrade).
I've also tried flashing the factory JWR66Y ROM from the Google site using adb. When I do that, I get a "signature verification failed" message.
It looks like there may be a way around this if a flash a different recovery. Can I do that with adb?
I can't connect with NRT anymore. I ahve some backups I made with NRT, but am not sure how to load them without using NRT.
I can sideload with adb, but can't do much else. "fastboot devices" doesn't return anything.
Help!
Thanks!

[Q] (for me) unrecoverable softbrick

Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Hardware involved:
Galaxy Note 3 N9005 that was running 4.4.2 (bought unlocked)
iMac with Yosemite and Parallels with Ubuntu and Windows 10 with Heimdall and Odin 3.09 installed
What I set out to do: root & install clockworkmod recovery with the ultimate goal to install Linux on Android. I had my previous Note 2 and LG P990 rooted too, so I was not entirely new to the procedure.
What I "achieved": Heimdall would not work at all due to a problem that apparently affects all Samsung 4.4.2 devices. So I got Parallels on my Mac and installed Windows 10 Technical Preview to run Odin. After several attempts I finally managed to got Odin to say "PASS" on the CF Auto-Root procedure. However, the phone would not boot anymore and always return to it's ODIN state. But I also succeeded to get Clockworkmod installed.
With that I installed Cyanogen, thinking to be able to get around the booting problem. I wasn't. Now when booting Cyanogen, I get a message that encryption was unsuccesful and the device needs to be restored.
I would like to comply and downloaded the stock files for restoring through Odin, but now even with the device in the proper ODIN download state, the phone is no longer recognized by the Software. Tried about a hundred times now with reboot etc. and nothing seems to work. Even KIES does note recognize the phone anymore.
I can enter CWM and Odin modes just fine. I just can't boot and I can't get it recognized by my Mac anymore. My best guess is I unintentionally screwed up the partition table / PIT file and now I can't restore it anymore.
I am at the end of the rope here and getting desperate, any suggestions (preferably step by step) would be most welcome!

psearcher said:
Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Click to expand...
Click to collapse
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.

Joku1981 said:
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.
Click to expand...
Click to collapse
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?

psearcher said:
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?
Click to expand...
Click to collapse
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.

Joku1981 said:
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.
Click to expand...
Click to collapse
Hi there Joku!
Just tried the Polish Lollipop Firmware and it still keeps displaying the "Encryption failed" error. It looks like it does not matter which file I flash, it will keep showing the same error.
Like I said, I believe I somehow broke the PIT file of the phone. Any ideas how to fix this?
Regards,
Rene

Try this pit file.
https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT VFG-UK-MSM8974.zip/
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005

Question solved!
DeuXGod said:
Try this pit file.
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005
Click to expand...
Click to collapse
Thanks DeuXGod, but by now I more or less stumbled on the solution by trial and error. I'll post it here, hoping that somebody may benefit from my endeavours in the future. As a n00b I can't post links though. Sorry for that.
I do not know if all the steps are necessary or correct, but in the end they did lead me back to a working device. :fingers-crossed:
After trying a few PIT files here in the forums, the problems did not go away. Some of them would lead to a phone that just got stuck at the "Samsung" screen and would not fully boot up.
So I got the idea to flash back the "old" Dutch 4.4.2 ROM, which I downloaded from Sammobile and flashed in ODIN. After booting it showed a bit of a different error message, saying the file system was corrupted
I googled for this and stumbled on a small ZIP file that is supposed to fix "cannot mount DATA / EFS errors". I loaded this on my SDXC.
Flashed aforementioned ZIP file through the recovery from the SDXC.
After rebooting it still showed the same error, so I got back to recovery, did a factory reset and a cache wipe.
Another reboot and much to my surprise (and great relief) the phone booted up normally again!
From there I thought that if this worked, the Polish 5.0 should work too. I flashed it. Flashed CF Auto Root after that and everything seems to be working fine!
I set everything up and the phone is now restoring the apps etc. So far looking very good!

I Need Help Please! PLEASE HELP!

Hello Everyone, i got a note 3 phone
SM-N9005 FCC ID: A3LSMN9005
SSN:- N9005GSMH
MADE IN VIETNAM BY SAMSUNG..
i bought this note 3 phone from UAE and it was with Kitkat 4.4.2 and when i was using it, some apps used to stop and not responding and get a pop-up message "System has stopped" or something like .com.system has stopped responding, also when i open some other apps the phone shuts down, so i turn it on, sometimes it works fine and sometimes it stops responding and shut down many times, so i had to make a full restore factory reset and still have the same problem, some guys told me you have problems with the rom, so i had to look for stock roms to it and found a lollipop rom under this name (AP_N9005XXUGBNL8_CL3643614_QB3415922_REV00_user_low_ship_MULTI_CERT.tar) and i installed samsung usb drivers just to make sure that everything is okay.
so when i started flashing it by odin it said Fail, so i tried once again but failed again, and i found my phone went to that black screen with (firmware upgrade encountered an issue, please select recovery mode in kies & try again), i couldn't get to my previous kitkat rom after that, but i'm able to go to download mode and recovery mode, so after this( brick) i had to search of how to unbrick it so after that i flashed philz as a recovery mode, and then flashed (All samsung recovery.tar) so then after flashing it, that message of (firmware upgrade encountered an issue, please select recovery mode in kies & try again) is gone, but i got another loop of restart each time i open the phone, it is not booting it is only taking me to the black start screen of android, and after a while it restarts itself.. and then when i tried to flash the same rom once again and connected my phone to my computer, drivers started configuring and so i waited to finish, but it failed it said (MTP USB Device Failed), though i still can see the phone connected over Odin in download mode.
so i had to look for another rom which is a kitkat stock version (N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar) which i found after downloading it and flashing it to my phone that it is for n900, which is normally failed flashing!.
so I don't know if i messed things up or not, and i really don't know what else or more to do ?
please give me your advice so i can restore this phone to its original stats.
Thank You!​

Are you sure the first firwmware you flashed is a full stock firmware?. What is the size?.
The second firmware you flashed isn't for n9005. Try different firmware specifially for UAE.
Sent from my SM-G925F using XDA Free mobile app

Rosli59564 said:
Are you sure the first firwmware you flashed is a full stock firmware?. What is the size?.
The second firmware you flashed isn't for n9005. Try different firmware specifially for UAE.
Sent from my SM-G925F using XDA Free mobile app
Click to expand...
Click to collapse
well i found it on a web site also this rom size is (2.304 GB), and it had an additional files with it about more 4 other files to flash with
what do you think?

hlabbad said:
well i found it on a web site also this rom size is (2.304 GB), and it had an additional files with it about more 4 other files to flash with
what do you think?
Click to expand...
Click to collapse
I see. It's a leaked lollipop firmware. Flash again with 4 files except pit. First boot will take some time.

Rosli59564 said:
I see. It's a leaked lollipop firmware. Flash again with 4 files except pit. First boot will take some time.
Click to expand...
Click to collapse
but when i flashed it with big sized file, the flashing process failed, it didn't work!

hlabbad said:
but when i flashed it with big sized file, the flashing process failed, it didn't work!
Click to expand...
Click to collapse
It's exactly here.
http://forum.xda-developers.com/galaxy-note-3/development/n9005xxugbnl8-5-0-lollipop-rom-t2982110
What kind of error shown in odin?.

Rosli59564 said:
It's exactly here.
http://forum.xda-developers.com/galaxy-note-3/development/n9005xxugbnl8-5-0-lollipop-rom-t2982110
What kind of error shown in odin?.
Click to expand...
Click to collapse
like this shown in the photo

Rosli59564 said:
It's exactly here.
http://forum.xda-developers.com/galaxy-note-3/development/n9005xxugbnl8-5-0-lollipop-rom-t2982110
What kind of error shown in odin?.
Click to expand...
Click to collapse
1. Go to Download Mode.
2. Tell me if you can flash this ONE using ODIN. It's the latest for KSA (Country Saudi Arabia).

hlabbad said:
like this shown in the photo
Click to expand...
Click to collapse
Choose corresponding file for BL, AP, CP & CSC. Do not tick repartition. You could also try with the firmware as suggested by joku

hlabbad said:
like this shown in the photo
Click to expand...
Click to collapse
You have repartion ticked but without a pit file, so obviously it will fail.
Sent from my SM-N9005 using Tapatalk

Thanks All for help

Did you solve the problem?

Getting error 7 upon flashing custom rom

Good morning everyone,
I was finally able to get out of my previous situation (bricked phone) thanks to your help, i can now fully load my phone (Samsung Galaxy A5 SM-A500FU).
I wanted to go back to modding right again cause i really dislike the samsung software (i actually have stock 6.0.1 firmware).
I flashed TWRP 3.0.2 with odin, and then tried to flash Cyanogenmod 13 taken from the proper thread. Tried to flash it, got error 7. I try to get information on that error and discovered it should be about rom version not right for my model. I was already sure i was trying to flash the correct rom, but i downloaded it again to be 100% sure. same error. Followed a guide who told me to edit some script file and remove some text lines, did it. Still error 7. Tried to flash with that "signature option" unselected. Still error 7.
Also tried to flash Cyanogenmod 12. something for my device, still error 7.
Do you have any clue on how to get out from this situation? maybe trying a different recovery?
I never had this kind of error, and i flashed dozens of time on multiple devices
Thank you in advance as always for your patience

Dharmost said:
Good morning everyone,
I was finally able to get out of my previous situation (bricked phone) thanks to your help, i can now fully load my phone (Samsung Galaxy A5 SM-A500FU).
I wanted to go back to modding right again cause i really dislike the samsung software (i actually have stock 6.0.1 firmware).
I flashed TWRP 3.0.2 with odin, and then tried to flash Cyanogenmod 13 taken from the proper thread. Tried to flash it, got error 7. I try to get information on that error and discovered it should be about rom version not right for my model. I was already sure i was trying to flash the correct rom, but i downloaded it again to be 100% sure. same error. Followed a guide who told me to edit some script file and remove some text lines, did it. Still error 7. Tried to flash with that "signature option" unselected. Still error 7.
Also tried to flash Cyanogenmod 12. something for my device, still error 7.
Do you have any clue on how to get out from this situation? maybe trying a different recovery?
I never had this kind of error, and i flashed dozens of time on multiple devices
Thank you in advance as always for your patience
Click to expand...
Click to collapse
When u get the error, go to ADVANCED and "Copy log" to sdcard, upload here and maybe we can help :good:

TheAbraham696 said:
When u get the error, go to ADVANCED and "Copy log" to sdcard, upload here and maybe we can help :good:
Click to expand...
Click to collapse
Here you go, sir

Dharmost said:
Here you go, sir
Click to expand...
Click to collapse
If i'm right error it's caused by broked signature in zip cuz u edited for skip devicename assert. So u need to sign again the zip or delete all files in "rom.zip/META-INF", only files! No the "com" folder.
And r u doing a factory reset before install?
Enviado desde mi SM-J710F mediante Tapatalk

TheAbraham696 said:
If i'm right error it's caused by broked signature in zip cuz u edited for skip devicename assert. So u need to sign again the zip or delete all files in "rom.zip/META-INF", only files! No the "com" folder.
And r u doing a factory reset before install?
Enviado desde mi SM-J710F mediante Tapatalk
Click to expand...
Click to collapse
I'm sorry sir, i'm not sure i fully understood your message :
The attached lo was a result of flashing the regular custom rom (not the edited one), don't remember if i had the signature option ticked or not. What are You suggesting me To do? On this try i didn't resect factory (no dalvik or cache ) But i di reset those 3 in previous tries And always got error 7

Dharmost said:
I'm sorry sir, i'm not sure i fully understood your message :
The attached lo was a result of flashing the regular custom rom (not the edited one), don't remember if i had the signature option ticked or not. What are You suggesting me To do? On this try i didn't resect factory (no dalvik or cache ) But i di reset those 3 in previous tries And always got error 7
Click to expand...
Click to collapse
You need to put in phone/sdcard the rom without any edition, do a factory reset, then flash

TheAbraham696 said:
You need to put in phone/sdcard the rom without any edition, do a factory reset, then flash
Click to expand...
Click to collapse
This is what i did the first time i tried to flash, didn't worked. I tried again, and incredibly the thing worked itself out. I have no idea what happened honestly, but now i'm back on track!
Thank you so much for assistence