Database Info

[Q] Update from 3.1 & Tiamat 1.4.4 failed

Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you

rogerodd said:
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
Click to expand...
Click to collapse
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!

okantomi said:
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
Click to expand...
Click to collapse
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.

rogerodd said:
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
Click to expand...
Click to collapse
The problem is that you can't flash anything from the external sdcard with v4.0.0.4. In rom manager, see if you can find"all clockwork recoveries" and find 3.2.0.0. If not, find 3.0.2.8 or 3.0.2.5 and flash one of them, preferably the latest of those I have listed. I think those will at least recognize your sdcard. If you can't do that, you will need to reflash the correct recovery the same way you did when you rooted. Remember, never flash a zip file through adb.
Good luck!

I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you

possible bad download... download again... also, don't think this would be an update... leave it as originally named, just choose the option to choose which zip file to install from the sd card

rogerodd said:
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
Click to expand...
Click to collapse
It sounds like you are flashing recovery ok, but you keep overwriting it with the stock recovery.
Here is some important information that should help a lot with making your new recovery "stick"and this was taken from the Idiot's guide to flashing...in the Development section, and originally written by publicanimal:
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
Boot into flash mode with 'adb reboot bootloader'
Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this section
Enter CWM with the following procedure
Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. If that happens, or if you see "starting fastboot protocol " your timing wasn't right and you need to reflash the recovery image and try it again.
See original post,below for more information.
http://forum.xda-developers.com/showthread.php?t=1130996

[Q] OTA modifier

Thank's to this forum I have phone with 16gb memory, fastboot , TWRP and rooted - this is really great, thank you!
There is new update for 6039H - - 010 07p ~55Mb the of size, waiting for installation.
1st - where is this the file? Where "System updates" app is hiding it?
2nd - should we check update.zip somehow before flashing or just modify, flash and see results.?
Thank you.
Sent from my 6039H using Tapatalk

Just found where is ota hidden : /data/data/com.tcl.fota/.fotadownload
You need to have "Show hidden files" enabled in file manager to see/find it.
I tried use ota_modifier.sh get error:
ota_modifier.sh update.zip
The provided file is not a zip file!
then:
file update.zip
update.zip: Java Jar file data (zip)
In my system LXLE 14 witch is actually Ubuntu there is "zip" not a "Zip" witch is expected from script. I had to change this - editing script. One letter - big difference for linux.
Flashing update_modified.zip filed...
"/system/bin/app_process32" has unexpected contents.
E: Error executing updater binary in zip .... [path to my modified zip]
Error flasing zip [path]
[edit]
If you see this error reason is - root. Need to be fully unrooted!
Now everything went fine. Flashed thru TWRP, rerooted. Whole process takes quiet of time be patient.

"This package is for A0001, this device is bacon." Wiped internal storage, cant flash

"This package is for A0001, this device is bacon." Wiped internal storage, cant flash
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time

If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot

KuranKaname said:
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
Click to expand...
Click to collapse
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?

niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
Instead of using adb push metod try to flash stock rom (https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/) and then flash the rom you want.
Good luck!
Note: You will loose twrp, so you have to flash it via fasboot [fastboot flash recovery (recovery name).img]

I'd suggest you to start over with a clean flash of COS13 fastboot factory image. Sounds like you are on a very old base.

Try to reboot TWRP and flash again. Or remove that check string from the updater-script.

download CM11 factory recover tool from my google drive @ https://drive.google.com/open?id=0ByfGPjP5zNYSTDZZcXZpLU44Q00 and install drivers and go to fastboot and plug in the phone and run recovery tool to push default factory image then install whatever CM version you want directly

No updater-script file that I can see
Can't find that file!
Anghirrim said:
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
Click to expand...
Click to collapse

use usb otg, success each time!

setup on ubuntu
Instructions for install on linux (test on ubuntu)
1- install adb :
Code:
$ sudo apt-get install android-tools-adb
2- install fastboot :
Code:
$ sudo apt-get install android-tools-fastboot
3- Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
4- test if the phone is detected with the cmd :
Code:
$ fastboot devices
5- unlock bootloader (/!\ it wipe the phone) :
Code:
$ sudo fastboot oem unlock
6- install TWRP :
- go to the path where is the img
Code:
$ cd path/to/twrp/folder/
- rename the image to twrp.img
Code:
$ mv old_name.img twrp.img
- flash the recovery
Code:
$ sudo fastboot flash recovery twrp.img
/!\ Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually turn it off by pressing and holding power button until it switches off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step. /!\
7- install custom/official ROM with TWRP :
- Wipe > Swipe to Factory Reset
- Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
- Install GApps using same process as ROM, then reboot. (optionnal: the official OnePlus ROM come with GApps pre-installed)
Possible errors with official ROM :
"This package is for device: A0001; this device is bacon" or "This package is for device: OnePlus; this device is A0001" or other similar
==> go into the ROM zip file, in "/META-INF/com/google/android/" there is an "updater-script" file. Open it, locate the expression ' getprop("ro.build.product") == "A0001" ' and replace the "A0001" by the device name you have. Replace the file in the archive. Note : after that, you can't verify the official MD5 !
- example : "This package is for device: A0001; this device is bacon", the ' getprop("ro.build.product") == "A0001" ' become getprop("ro.build.product") == "bacon" '
Sources :
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
https://forum.xda-developers.com/oneplus-one/help/package-a0001-device-bacon-wiped-t3457766

Oneplus one Oxygen Installation error using TWRP
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
check this post
wirelessindeed.blogspot.com/2017/07/oxygen-installation-error-on-oneplus.html

Update TWRP Recovery
I know this is an old post, so this is here in case anyone finds it in the future and requires help...
My mate asked me to upgrade his OnePlus (original, codename Bacon) and I received this error when upgrading from LineageOS 14.1 to 15.1.
To resolve, its extremely easy - simply upgrade the TWRP recovery. My mate originally had TWRP 3.1.1.0 installed, but the latest weekly LineageOS 15.1 required v3.2.3.0 installed which resolved the error message "This package is for device: bacon, a1001. this device is ."
Either Vol+ and Power to enter bootloader, or from command line:
adb reboot bootloader (with Android USB debugging turned on. You can test for connection using command "adb devices" and if successful it should show your phone's serial number). You will need to trust the computer's connection on your phone. To get to Android USB Debugging, you need to go Settings -> Developer menu options, and if you can't see that: Settings -> About Phone and tap "Build" 7 times for developer mode to appear.
Once phone goes into bootloader mode, type:
fastboot flash recovery "path:\twrp-x.x.x.x-bacon.img" (obviously path is the directory that the recovery is stored in, and x.x.x.x will be replaced with the version you've just downloaded. At time of writing, v3.2.3.0 is the latest. You can always use "fastboot devices" if you used Vol+ and Power to enter bootloader to ensure you have a valid connection, in USB debugging mode on your phone and correct Android adb drivers installed in Windows.
Wait until it's succeeded, and turn off phone. Now go into recovery and try again - and this time you should be good to go!!!
All the above implies your bootloader is unlocked. If you need to unlock your bootloader, there are plenty of instructions telling you how to do this - but HAVE A BACKUP as unlocking your bootloader will do a factory reset on your phone.
Hope this helps someone
......mmmmmm BACON!!!

Error during shield update

Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?

bird12358 said:
Hello,
I can update my shield tablet. I get that error:
Code:
Updating partition details …
… done
Full SELinux support is present
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file …
Sskipping MD5 check*: no MD5 file found
Source*: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys
Target: nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys
Verifying current system...
Package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/40827_726,62502:user/release-keys or nvidia/sb_na_wf/shieldtablet:6,0,1/MRA58K/49349_766,5399:user/release-keys*; this device has nvidia/sb_na_wf/shieldtablet:6,0:MRA58K/41524_664,1902:user/release-keys.
Update process ended with ERROR*: 7
Error installing installing zip file '@/cache/recovery/block.map'
Done processing script file
MTP Enabled
Can someone help me?
Click to expand...
Click to collapse
some more information might help people help you mate, are you rooted, do you have a custom recovery installed or are you running a custom rom? things like that help us alot

I user to be as root. But I restore factory setting ans I still have thé error.
Should i made an other thing to suppress thé root settings.?

Yes Mate I thought no so do you have a custom recovery installed
Sent from my HTC One using Tapatalk

I don t think I have that recovery installed. Where could I find this?

bird12358 said:
I don t think I have that recovery installed. Where could I find this?
Click to expand...
Click to collapse
Turn off your tablet then hold volume down and the power button untill you get to the boot loader then use the volume down button to select recovery and press power if you have a custom recovery it will bot to it and it will say team win recovery
Sent from my HTC One using Tapatalk

It seems I don t have a custom recovery. How should I do nos?

Note 3 neo boot loop. Nand erazed. No backup.

hi
I think i killed my note 3 neo (sm-n7505) by rooting attempt without getting proper education or necessary backup and tools!
If someone can help, pls....
i am not going to explain EVERYTHING what i did but important.(i think)
1 Rooted
2 Verified with ROOT CHECK
3 Installed BUSY BOX
5 TWRP installation failed. (Installed a Fake one!. It damaged everything)
4 NO BACKUP ( I made a backup but somehow it wiped away!) (forgot to double check!)
6 "NAND ERAZE ALL" CHECKED IN ODIN AND EXECUTED while CF-Autoroot! (wrong! wrong! wrong!)
CURRENT SITUATION/WHAT I HAVE NOW/WHAT CAN I DO ?
SYSTEM IS NOT DEAD COMPLETELY(?)
I CAN 'ON' IT BUT END WITH A BOOT LOOP
I CAN GO TO RECOVERY MODE
I CAN GO TO DOWNLOAD/ODIN MODE
I HAVE ACCESS IN EXTERAL SD CARD
EXTERNAL SD CARD HAS THE FOLLOWING:
CF AUTOROOT hllte-hlltexx-smn7505.zip
kyleopen-cwm-v3.tar.md5
Super SU V2.52.zip
BETA-SuperSU-v2.52.zip
SR3-SuperSU-v2.79-SR3-20170114223742.zip
---------------------------------------------------------------------
me.twrp.twrpapp-22.apk.md5
---------------------------------------------------------------
BOOT LOADER
SM-N7505-4.4.2.zip
SM-N7505_BOOT_5.1.1.ZIP
SM-N7505_BOOT_5.1.1.ZIP
-------------------------------------------------------------
StockROM and Custom ROM
Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip
Note-4-Mini10 N7505.zip
Note-5-ROM.zip
NoteRom V4 SM-N750 Only.zip
cm-12.1-20160809-UNOFFICIAL-hllte.zip
----------------------------------------------------------------------------
There is "full budle of the ANDROID SDK
(Android-studio-bundle-162.3871768-windows)
There is "minimal_adb_fastboot_v1.4.2_setup on my pc"
installed samsung usb driver
--------------------------------------------------------------------------------
I Cannot Successfully Execute ANY of the above in Recovery Mode
Here the the text at the top of the reovery Screen
[Andorid system recovery (3e> LMY47X.N7505POUDOK2 ]
and
Here is the info at the bottom
#MANUAL MODE #
--Applling Multi-CSC...
Applied the CSC-code : KSA
Successfully applied multi -CSC.
---------------------------------------------------------------
When i execute any zip, it end-up with some error messages
"Signature verification failed"
"footer is wrong"
and restart the device or bootloop!
-------------------------------------------------------------
CAN I FIX THE DEVICE? OR NO NEED TO WASTE MY TIME AND BUY A NEW ONE?
Thank you
Shihab
here is the link it lead me here
trendblog(dot)net(slash)fix-soft-bricked-android-device-first-aid-guide

@1978shihab
Hi
Try downloading your firmware from sammobile.com based on your country code and flash it with Odin while your phone in Download Mode, in Odin, check f.reset time and auto reboot, don't check any thing else.
The firmwares link:
https://www.sammobile.com/firmwares/sm-n7505/SM-N7505/

SAM MOBILES FILE FAILED BUT "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip "
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab

1978shihab said:
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
Click to expand...
Click to collapse
Hi Mr-Shihab
To flash a zip with recovery, then it has to be a flashable zip, it should be built in a specific way so the recovery can work with it, and the zip you have is a normal compressed files, so it can't be flashed at all with recovery, also note that the zip you downloaded from sammobile might be corruptedly downloaded, because sammobile offer a clean roms, anyway, you can also use samsung-firmware.org, it's a trusted site as well.
Ps: that md5 file you got works the same as the 4 files you downloaded after.
God bless you too

Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.

RAZERZDAHACKER said:
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
Click to expand...
Click to collapse
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?! ?
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!

MigoMujahid said:
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?!
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
Click to expand...
Click to collapse
There is a recovery mode (not the one where you flash your roms and replace with twrp) in kies (my bad for not saying that) that reflashes the whole phone, you could literally erase the recovery or the kernel and you'd still be able to recover it which you can check out here