Related
<KANE>How to make i9003 straight flash pack (system embedded cf-root, ext4, deodex)
Most of the theme is zip format and flash with CWM,but so many people still don't know how to made the zip.So I make one tutorials for the people who don't know (EX:CF-Root,ext4,deodex and bla bla bla)
1.First,wipe data and cache
2.Flash the rom that you want via odin
3.Flash CF-Root(UC kernel also can)via odin
4.Open CWM,flash the deodex(zip)(how to make?google search )
5.When you want to convert you system to ext4 format,backup your rom via CWM firstAfter backup finnish,back to main menu,flash the ext4 format file(zip),restore the rom,than your system are fully convert to ext4 format!
6.After finnish first 5 step,use ADB tool
7.Go to wireless and network/USB setting,select "mass storage" ,and then Open "USB debugging" at applications/development ，open CMD(computer)
type “adb shell” and then connect to computer via USB,press enter,and than type
"dd if=/dev/block/stl9 of=/sdcard/system.rfs bs=4096" then system.rfs will copy to internal SDcard（The system.rfs copy at here is included cf-root，ext4 and deodex）
8.Package it need to use linux system（Virtual Machine also can），at least linux 6 or Ubuntu 10
only linux 6 or above support ext4 format system file! If the version lower than 6 that the system.rfs cannot be mount
9.If you want further modify system.rfs, use terminal,type
mount：mount -o loop system.rfs /root/system/
unmount：umount /root/system/
note：(the path above is me own use! I create folder at / , switch to my new file directory, execute this command!
mount before modify，then after unmount it can be save
10.Package it ，must be add boot.bin Sbl.bin param.lfs normalboot.img system.rfs modem.bin and cache.rfs of the original rom,only can flash with this
now we need to cover the system.rfs with after modify one
Cover the normalboot.img in CF-ROOT into it.And cover the cache.rfs with after convert to ext4 one,and add userdata.rfs file
（you can get the cache.rfs and userdata.rfs at attachment, all rom also can use it!）Now you can package it
go to terminal with linux，cd Command change to the folder you create before this, put the boot.bin Sbl.bin param.lfs normalboot.img（cf-root one） system.rfs（modify one） modem.bin cache.rfs（cover one） userdata.rfs（add one）to the folder
Execute the command "tar cf PDA.tar boot.bin Sbl.bin param.lfs normalboot.img system.rfs modem.bin cache.rfs userdata.rfs" to package it！
PDA.tar is the file after synthesis ，and you can add other file if you want
11.And then copy the PDA.tar to desktop，flash with odin！dont forget to flash with pit file!Why must use pit file and userdata.rfs? Because pit file and userdata.rfs will re-partition and reset all user data ! So all version also can flash the zip file and no need to rely on other versions(pit can get at attachment)!
If it is not very good please tell me! Thanks for your support!
Hopes：
1.most of the XDA people are very pro，and I hope you can make a tutorials when you make a new thing
2.At china,so many people use I9003,so many people at XDA too!!so we hope when you create a new thing can add chinese!
（only hope,not force you!thank you!）
Wow i was sear hing just this in all the forum!! Thanks!!
Enviado desde mi GT-I9003 usando Tapatalk
thank you!!
This is awesome. Thanks
Sent from my GT-I9003 using XDA App
I am reading everything a lot of times, to be sure of that I understand everything. Could anybody explain me this? I don't understand...
go to terminal with linux，cd Command change to the folder you create before this, put the boot.bin Sbl.bin param.lfs normalboot.img（cf-root one） system.rfs（modify one） modem.bin cache.rfs（cover one） userdata.rfs（add one）to the folder
Click to expand...
Click to collapse
Hello Kane, if i understood you, with this procedure i can make a PDA.tar file to flash with ODIN but i also need a pit file althaugh it's a single file. Am i wright?
I could use this method to get a full pda.tar with the firmware i am looking for (i mean, if i get an i9003 phone with that firmware)?
I will explain myself:
recently i poste this question in here http://forum.xda-developers.com/showthread.php?p=20360464#post20360464:
Uan_ar said:
Hi people, i'm looking for the firmware UBKPD (2.3.6) wich is the one that is the update from UBKB1 (2.2.1) by kies in Argentina. I would like to get the official and unbranded, but in the official roms threads of sammobile or sampro.pl it didn't appear yet (like the XXKPQ in sammobile).
If anyone get it or if is possible to get it from Samsung i would be pleased.
On the other hand, if anyone can tell me if it's possible to extract it from a updated phone and to make a .tar file to flash to others it would be helpful also.
Thank you very much in advance.
Click to expand...
Click to collapse
If i get a phone with the UBKPD firmware, can i make a "UBKPD_PDA.tar" file? What else do i need to put it in my phone (i got now intalled the XXKPQ)? Should i flash it over XXKPE (ginger, 4 files) or mi old official froyo (UBKB1)?
Thank you very much in advance. Greetings from Argentina.
HI，luiseteyo！Steps should be so!
put the “boot.bin” “Sbl.bin” “param.lfs” “normalboot.img”（cf-root one） “system.rfs”（modify one） “modem.bin” “cache.rfs”（cover one） “userdata.rfs”（add one）to a new folder, then go to terminal with linux，use "cd" Command change to this folder and type :
"tar cf PDA.tar boot.bin Sbl.bin param.lfs normalboot.img system.rfs modem.bin cache.rfs userdata.rfs"
hi，Uan_ar
yes,u need a pit file..it can be found everywhere lol
sure,there is no doubt that u can make a "UBKPD_PDA.tar" file use this method..and u can flash it over every rom
i just wan to say about the ugly typesetting...= - =
and it's nice ... good job...haha
CHINA-KANE said:
hi，Uan_ar
yes,u need a pit file..it can be found everywhere lol
sure,there is no doubt that u can make a "UBKPD_PDA.tar" file use this method..and u can flash it over every rom
Click to expand...
Click to collapse
OOkey, now I understood. But one more thing. I put the device in debugging mode and massive also. I conect it, I open cmd, I write the location of the adb with:
Code:
C:\Users\***\Desktop\ADB
Then I type:
Code:
adb shell
and then the code to backup system.rfs, but it does nothing in the phone and nothing in the cmd, do I have to wait? Thank you very much!!
EDIT: I answer myself. You have to wait despite it doesn't say nothing. The system.rfs backup is in the internal card (in my case)
CHINA-KANE said:
hi，Uan_ar
yes,u need a pit file..it can be found everywhere lol
sure,there is no doubt that u can make a "UBKPD_PDA.tar" file use this method..and u can flash it over every rom
Click to expand...
Click to collapse
Thank you very much Kane. I don't have any difficulties to find the pit, as you said is everywhere. However, my question was made in base that i never used pit when flashing just one pda.tar file.
What happens if i don't add the userdata.rfs? this pda.tar will work also on any other phone? which is te data that goes there? I´m asking you this because i don´t need/want the data from other phones (personal data, imei, etc.) i just want try to make a flashable update firmware for all the argentinian android i9003 comunity.
thanks again, and again
Interesting and useful. I thing the next link is useful: http://forum.xda-developers.com/showthread.php?t=1132724
userdata.rfs must be added, when the district needs it! Any ROM like this!
After connecting phone, enter the command directly in the CMD adb shell, do not brush into the ADB!
my bad ,,,,,,,,
sakindia123 said:
my bad ,,,,,,,,
Click to expand...
Click to collapse
for what?
hey,do u need to like 'sign' the system.img after combining it with pda?coz i always get 'PDA Invalid"
GOOD NEWS
NO MORE NEED THIS PIT FILE FOR BIG HIDDEN, (for now):
Because have Members that notice have flashed UK Rom's Multi.CSC VFG after flash the Germany DBT Pit file, I tried the same:
After a full wipe I flashed this Pit file attached and link. After I have installed a XXUENB4 VFG TCL Rom that have a hidden file = 86.661 KB.
The install work well without hidden issues, no "FAIL! (Size)". Work well whit a HIDDEN partition whit Block Count = 204.800.
I renamed it because inside PIT partition we have Flash FileName = MSM8974.pit like we can see here:
Identifier: 71 <- Partition Number
Attribute: 5
.............
Partition Name: PIT
Flash FileName: MSM8974.pit
Here the DBT Pit file: https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT+VFG-UK-MSM8974.zip/
This Pit file is for Note3's from 32 GB, may be to more also, not tried.
Good work whit this Pit File
==================================================
:good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good:
==================================================
OLD METHOD CONTINUE HERE LIKE BACKUP:
PIT File whit a biggest HIDDEN partition to flash all Rom's. XEO_OXX.csc, DBT_DBT.csc and UK ROM's_ VFG.csc.
We have on first Kikat to Note3 N9005, the leaked Rom OXXUENA6, the next Pit file: CSC_Signed_HLTE_EUR_OPEN32G_0718.pit.
I analyzed it whit PIT Magic. It have a big HIDDEN partition whit Block Count = 471.070 ( From XEO rom it is = 20.480 <file size=8.441 KB>, from DBT Rom after have flashed the Germany DBT pit file it is = 204.800 <file size=53.125 KB> and from UK_VFG Rom's the file size is 86.661 KB).
If we flash a ROM DBT or UK VFG whit the partition from 20.480 we have this fail in Odin:
.....
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
FAIL! (Size)
TESTING THIS PIT FILE:
After full wipe data + cache + dalvik and format system on mount and storage on costumer recovery...
I flashed this PIT File alone on Odin 3.09, ticked Re-Partition, and not ticked Auto-Reboot and F. Reset Time.
Power off and new Download Mode to flash a new Rom, first from 20.480. At first reboot it had bootloop on Samsung logo.
New Power off and Download Mode to flash the Customer Recovery kk(0125) from Chenglu. This recovery can't mount the sdcard (I had pull out the ExtSdCard after make to it a backup from the Internal Sdcard). Then, I not had sdcard.
In my opinion the big HIDDEN partition from this pit file was need expand your size using internal storage space, Then, deleted the sdcard partition and your content.
Solution:
On Customer Recovery, Mount and Storage, format /data and /data/media (/sdcard). Not had sdcard but the space was there.
Reboot on recovery and good, now the Rom started well.
And to try, (always after full wipe before) I flashed the DBT NB7, rooted it to see the /efs/imei/mps_code.dat. The DBT was here. Good install.
Flashed also after, the Portugal (Vodafone) NB4 Rom TCL (That not have TCL but ATL from Spain by default, like problem from XEF Rom's) and flashed well. No issues in Odin "hiden.img.ext4 -> FAIL! (Size)" like before. Rooted also and on /mps_code.dat ATL now. Good install also.
After my try's I have decided to not attach here this PIT file.
It have some dangers and change the Knox flag to 0x1, because the need to flash a Customer Recovery (For me no problems, I have my 0x1 from begin).
May be You have that leaked Rom NA6 on Your Pc like me. If not, You can download it from SamMobile, it is always there. (Search, write on white box top right, Leaked Rom N9005 and You see it).
On that leaked are two, only the _0718.pit have a big HIDDEN. The _0805.pit have a small HIDDEN.
THIS IS ONLY ONE IDEA.
If You want try this...
PS: My Note3 work well whit that big HIDDEN partition and I must not have more hidden issues in future Rom's.
Like the pit say this is for Note3 from 32GB only.
In leaked xeo na6 rom there is one pit file
Sent from my SM-N9005 using Tapatalk
newstar said:
In leaked xeo na6 rom there is one pit file
Click to expand...
Click to collapse
Write the name of that, please.
Attach it here.
Thanks
Checking, will report
Sent from what ever device I got my hands on via Tapatalk
Well i got the hidden.img fail message on Odin 3.09...
Anyone can get me that pit file? to fix it?
Edit: Read OP and saw the solution there... going to try and flash the DBT NB7 to see if it does fix it
http://forum.xda-developers.com/showthread.php?t=1916936 May be you should look into this as well.
Flashed XXEUNB4 and it flashed flawlessly
Sent from my SM-N9005 using Tapatalk
joluke said:
Well i got the hidden.img fail message on Odin 3.09...
Anyone can get me that pit file? to fix it?
Edit: Read OP and saw the solution there... going to try and flash the DBT NB7 to see if it does fix it
Click to expand...
Click to collapse
To DBT NB7 + NB4 You have here the Germany Pit.file: http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77 It work well according some Members that flashed it.
Rename the pit file to MSM8974.pit . See next post.
zocster said:
http://forum.xda-developers.com/showthread.php?t=1916936 May be you should look into this as well.
Click to expand...
Click to collapse
This is the Tool that I use to analyze the Pit files, I never created any.
Attached the PIT Magic analyze from CSC_Signed_HLTE_EUR_OPEN32G_0718.pit. Identifier is Partition Number.
You see on HIDDEN partition the Block Count = 471.070. Big enough to all hidden files.
You see also on partition PIT the Flash FileName: MSM8974.pit. Then that name CSC_S... usually work but I prefer rename it always to MSM8974.pit like the partition PIT like, to flash by Odin. Whit this name I'm sure that it work well.
Identifier: 71
Attribute: 5
..........
Partition Name: PIT
Flash FileName: MSM8974.pit
GOOD NEWS
NO MORE NEED THIS BIG PIT FILE, (for now):
See in OP.
ValenteL said:
GOOD NEWS
NO MORE NEED THIS PIT FILE FOR BIG HIDDEN, (for now):
Because have Members that notice have flashed UK Rom's Multi.CSC VFG after flash the Germany DBT Pit file, I tried the same:
After a full wipe I flashed this Pit file attached and link. After I have installed a XXUENB4 VFG TCL Rom that have a hidden file = 86.661 KB.
The install work well without hidden issues, no "FAIL! (Size)". Work well whit a HIDDEN partition whit Block Count = 204.800.
I renamed it because inside PIT partition we have Flash FileName = MSM8974.pit like we can see here:
Identifier: 71 <- Partition Number
Attribute: 5
.............
Partition Name: PIT
Flash FileName: MSM8974.pit
Here the DBT Pit file: https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT+VFG-UK-MSM8974.zip/
Good work whit this Pit File
Click to expand...
Click to collapse
Excelent work my friend
Enviado do meu SM-N9005 através de Tapatalk
fRIK
ValenteL said:
GOOD NEWS
NO MORE NEED THIS PIT FILE FOR BIG HIDDEN, (for now):
Because have Members that notice have flashed UK Rom's Multi.CSC VFG after flash the Germany DBT Pit file, I tried the same:
After a full wipe I flashed this Pit file attached and link. After I have installed a XXUENB4 VFG TCL Rom that have a hidden file = 86.661 KB.
The install work well without hidden issues, no "FAIL! (Size)". Work well whit a HIDDEN partition whit Block Count = 204.800.
I renamed it because inside PIT partition we have Flash FileName = MSM8974.pit like we can see here:
Identifier: 71 <- Partition Number
Attribute: 5
.............
Partition Name: PIT
Flash FileName: MSM8974.pit
Here the DBT Pit file: https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT+VFG-UK-MSM8974.zip/
Good work whit this Pit File
==================================================
:good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good:
==================================================
OLD METHOD CONTINUE HERE LIKE BACKUP:
PIT File whit a biggest HIDDEN partition to flash all Rom's. XEO_OXX.csc, DBT_DBT.csc and UK ROM's_ VFG.csc.
We have on first Kikat to Note3 N9005, the leaked Rom OXXUENA6, the next Pit file: CSC_Signed_HLTE_EUR_OPEN32G_0718.pit.
I analyzed it whit PIT Magic. It have a big HIDDEN partition whit Block Count = 471.070 ( From XEO rom it is = 20.480 <file size=8.441 KB>, from DBT Rom after have flashed the Germany DBT pit file it is = 204.800 <file size=53.125 KB> and from UK_VFG Rom's the file size is 86.661 KB).
If we flash a ROM DBT or UK VFG whit the partition from 20.480 we have this fail in Odin:
.....
system.img.ext4
modem.bin
cache.img.ext4
hidden.img.ext4
FAIL! (Size)
TESTING THIS PIT FILE:
After full wipe data + cache + dalvik and format system on mount and storage on costumer recovery...
I flashed this PIT File alone on Odin 3.09, ticked Re-Partition, and not ticked Auto-Reboot and F. Reset Time.
Power off and new Download Mode to flash a new Rom, first from 20.480. At first reboot it had bootloop on Samsung logo.
New Power off and Download Mode to flash the Customer Recovery kk(0125) from Chenglu. This recovery can't mount the sdcard (I had pull out the ExtSdCard after make to it a backup from the Internal Sdcard). Then, I not had sdcard.
In my opinion the big HIDDEN partition from this pit file was need expand your size using internal storage space, Then, deleted the sdcard partition and your content.
Solution:
On Customer Recovery, Mount and Storage, format /data and /data/media (/sdcard). Not had sdcard but the space was there.
Reboot on recovery and good, now the Rom started well.
And to try, (always after full wipe before) I flashed the DBT NB7, rooted it to see the /efs/imei/mps_code.dat. The DBT was here. Good install.
Flashed also after, the Portugal (Vodafone) NB4 Rom TCL (That not have TCL but ATL from Spain by default, like problem from XEF Rom's) and flashed well. No issues in Odin "hiden.img.ext4 -> FAIL! (Size)" like before. Rooted also and on /mps_code.dat ATL now. Good install also.
After my try's I have decided to not attach here this PIT file.
It have some dangers and change the Knox flag to 0x1, because the need to flash a Customer Recovery (For me no problems, I have my 0x1 from begin).
May be You have that leaked Rom NA6 on Your Pc like me. If not, You can download it from SamMobile, it is always there. (Search, write on white box top right, Leaked Rom N9005 and You see it).
On that leaked are two, only the _0718.pit have a big HIDDEN. The _0805.pit have a small HIDDEN.
THIS IS ONLY ONE IDEA.
If You want try this...
PS: My Note3 work well whit that big HIDDEN partition and I must not have more hidden issues in future Rom's.
Like the pit say this is for Note3 from 32GB only.
Click to expand...
Click to collapse
fRIK I cant understand what your saying
I've flashed the UENB4 rom tried the msm8974.pit with the new NB5 rom..
still get the EXT4 error, I've never felt this helpless... I know your doing everything to help but I'm confused..
Fade777 said:
fRIK I cant understand what your saying
I've flashed the UENB4 rom tried the msm8974.pit with the new NB5 rom..
still get the EXT4 error, I've never felt this helpless... I know your doing everything to help but I'm confused..
Click to expand...
Click to collapse
The NB5 Rom is from Taiwen an Hongkong right? And Your Note3 is from 16 GB right?
You know what ValenteL
I'm an idiot.. my note 3 is a UK 32gb
I think I was trying to put a 16gb rom on a 32gb note 3..
Sent from my SM-N9005 using Tapatalk
Fade777 said:
You know what ValenteL
I'm an idiot.. my note 3 is a UK 32gb
I think I was trying to put a 16gb rom on a 32gb note 3..
Click to expand...
Click to collapse
Well, the NB5 Rom's have a Hidden file from 7.865 KB only. It's sure to 16 GB because the smaller to 32 GB is 8.441 GB like on XEO Rom to Poland.
The Pit file from here is only to Germany DBT Rom's, having a hidden file = 53.125 KB and to UK VFG-csc Rom's having a hidden file = 86.661 KB.
You not have need to flash the Pit file. But now You are alright to try DBT and UK VFG Rom's.
Hi I think australian NOTE 3 32g rom has the biggest Hidden.img.. I tried using almost all the PIT file still not luck with flashing the aussie 4.4.2 rom to my UK device..
Still getting the hidden.img.ext4 error..
Now I'm using UK BTU rom.. I would really want to flash australian XSA rom to my note 3.. can anyone help??
below is the post.
http://forum.xda-developers.com/showpost.php?p=56515739&postcount=1280
WARNING!
I'm not responsible for anything that happens to your device after using this guide
Use at your own risk!
CREDITS to @lch920619x for the original guide, @aboodyaiman for teaching me how to convert the ROM in the first place. This small guide is simply a newer one with updated links and steps on converting ROMs to work with 11GB pit. I'll add images when I have time yay
You will need THIS PACKAGE for converting between 8GB and 11GB pits, THIS PACKAGE for converting the ROMs you want to work with 11GB pit.
If you haven't download Odin yet then here is ODIN 3.12.3 ( you will need it to convert PIT between 8GB & 11GB
Installing the PIT files
1. Download the PIT Package
2. Flash pit your desired pit (PIT)
<8GB.pit to convert to the standard 8GB data partion - RECOMMENDED>
<11GB.pit to convert to the 11GB data partition>
3. Flash CF-Auto-Root (AP)
4. Wipe Cache & Data in stock recovery.
5. Flash modem (AP)
6. Flash param.bin (CP)
7. Flash custom recovery (AP)
8. Format all partitions using TWRP
9. Optional: Update to latest TWRP if you wish
Converting ROMs to work with 11GB pit
<Haven't test on Alberto's Lineage since I don't have the device anymore, REMEMBER that Alberto said he is NOT supporting 11GB pit for now>
1. Head to Python website, download and install Python
2. Download ROM CONVERT PACKAGE and extract it anywhere
3. Extract File context, system.new.dat and system.transfer.list from the ROM zip you want to convert in to where you extract the ROM CONVERT PACKAGE
4. Execute extractor and press 1, then press Enter three times
5. It will provide system folder when it's done
6. Extract boot.img, meta folder and file context from the original ROM zip again.
7. Replace updater-script with the one in the ROM COVERT PACKAGE
8. Add all to zip archive and flash your new 11GB pit compatible ROM
sry i am a newbee for packing and unpacking rom. I want to flash ALE95 n5 7.1. but since it doesnt supports 11gb pit. i am giving a try.
1. i downloaded and install python 2.x.x
2. now i am stuck at how to extract file context, system.new.dat, system.transfer.list from ALE95.
i googled much, i downloaded filecontext tools, system.extractor.win, rom convert package all. but how to use python and extract those files and repacking i duuno. i did bit of research in google also.. but need some guidance please
can you make video review about how to convert roms from 8 gb to 11gb
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
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
gian20 said:
device soft bricked but can enter download mode (Vol Up + PWR + Home). I did a:
# dd if=/dev/mmcblk0p16 of=/storage/emulated/0/param.lfs
before flashing the custom param. I restored the device using heimdall (GNU/Linux PC)
$ sudo heimdall flash --PARAM param.lfs
device rebooted and worked
Click to expand...
Click to collapse
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
gian20 said:
the logo.jpg I used is about 600KB in size it may be the problem. What must be the right size so I do not overwrite anything?
I have dumped the partition /dev/block/mmcblk0p16 to a param.lfs
then the param.lfs appears to be a POSIX TAR Archive (GNU) can we just repack the file and modify only the logo.jpg? (the recovery script will repack the tar archive)
after modifying can we just write it with dd?
# dd if=./paramodified.tar of=/dev/block/mmcblk0p16
Click to expand...
Click to collapse
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
gcrutchr said:
The original logo.jpg is under 100kb, so a 600kb file would be too big.
I would keep the file under 150kb just to be safe.
Yes, you can use dd to write the modified param file...that is what the logo changer script does.
Click to expand...
Click to collapse
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Unable to change Boot Logo
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
gcrutchr said:
Boot Logo Changer
Change the boot image (NOT the bootanimation) that shows BEFORE the boot animation.
This has only been tested on the T285, but should work on the T280.
If in doubt, check to see if your PARAM partition is mmcblk0p16.
There are programs on the Play Store that can show the partitions, there names and other info.
This app does make a backup of the original PARAM partition and stores it on your /sdcard as PARAM.bak.
MAKE SURE YOUR SDCARD IS MOUNTED WHEN YOU GET INTO TWRP or CWM.
(Have NOT tested in CWM as I have TWRP installed).
Many thanks to [email protected] for the original script for the Samsung Galaxy Tab 3 8.0.
He has kindly allowed me to modify his script for the Tab A (SM-T285).
His xda page is: Samsung Galaxy Tab 3 8.0 Boot Logo
To change the logo (.jpg file), replace the logo.jpg in the tmp folder with your own .jpg file.
Remember the Galaxy TAB A (SM-T285) display is 720x1280.
Steps to install:
- Reboot into recovery
- Select Install from recovery menu
- Select TAB-A-T285-LogoChanger.zip
- Follow recovery install prompts
- Reboot and enjoy!
If you need a restore script, please contact me or post a message.
Downloads:
Google: T285 Boot Logo Changer
Mega: T285 Boot Logo Changer
Click to expand...
Click to collapse
SM T285 flash wrong bootlogo.zip
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
hassansys2 said:
Hi,
I tried to change boot logo but failed. When i change mmcblk0p16 partition file with modified version of partition with my logo it doesn't work. I dig in to find out issue. I saw when ever devices restarts it have fresh copy of all partition files in /dev/block/ folder. I check modified dates of all partition files it always have last date when it was restarted. i don't know what is issue can you help out.
any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
soaib333 said:
Sir, I have Samsung Galaxy TAB A SM T285 ,I have a zip file of boot logo changer ...so i flash via TWRP Recovery .. and it works fine.. then some day later, I make a change in the zip file, I replace logo.jpg to another image then I flash the zip... and it"s flash successfully no error.. but then I reboot the system.. it shows black nothing will happen.. only download mode is in working condition.. so I flash stock rom via Odin but nothing will happen.... the TAB don't start Sir please help me....:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
gcrutchr said:
I no longer have a T285. All my T285 files are deleted.
But, my guess is you made the .jpg logo too big.
Click to expand...
Click to collapse
yes sir the jpg file is around 600 kb..... sir please help me..... :crying::crying::crying::crying::crying::crying:... please tell me sir what can i do for recover my device... sir please...... please sir :crying::crying::crying::crying::crying::crying::crying:
gcrutchr said:
Should have no problems with the .zip file. I used on my T285.
It will make a backup of the PARAM block and store it on you internal sdcard before changing the bootlogo.
All that had to be done was replace the logo.jpg file in the zip file (drag and drop). Install it in TWRP.
Obviously, if the logo.jpg file you put into the .zip file is very large, you may end up overwriting something.
Click to expand...
Click to collapse
sir please, can you send me stock boot logo tar.md5 file for SM-T285 ...... beacuase my phone is bricked.. only download mode is working...... if i flash the orignal bootlogo.tar.md5 i hope it will recover please sir help me.... i request you sir please :crying::crying::crying::crying::crying::crying:
I have a huge problem. I made the .jpg file too big and now the tablet won't boot except for DOWNLOAD MODE. I wasn't able to backup so I just downloaded the param.ifs from this reply.
gian20 said:
The script works now, I've reduced the jpeg to 50KB but it is blurry. Thank You
I have uploaded my param.lfs (it is compressed with 7z to reduce size from 2MB to 420KB, 26193062 is a CRC32 hash checksum of the file to verify that it is not corrupt) from mmcblk0p16 that can be flashed with heimdall ($ sudo heimdall flash --PARAM param_26193062.lfs) if someone else messes up.
1. download param_26193062.lfs
2. decompress with 7z (7z x param_26193062.lfs.7z)
3. flash with device ($ sudo heimdall flash --PARAM param_26193062.lfs)
Click to expand...
Click to collapse
Now I am using Windows 7 Heimdall to flash this. Except with this I am unable to flash because it's showing "Error: Failed to retrieve config descriptor."
Need help ASAP
Update: After a few tries, now it says
"Initializing Protocol...
Error: Failed to send data!Releasing device interface...
Solution: Used Odin. Basically, using 7zip, packed the param.lfs to a tar file, then packing that to a gzip file, then prooding to flash via ODIN
Any one have stock param.tar file for flashing on sm-t285?? Plz help me? ? ?
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Darksnite said:
Can anyone help me i have installed that zip that u said using twrp and i thought when u said follow recovory install prompts i thought it will tell me to chose an image for boot logo and i have to select it so i prepared an image but i didnt know i have put the image in that zip so i have a boot logo of minions so after that i again installed the zip with the correct image but at the top it said fail and the boot logo is still minions and i dont know how to change back and tablets still working
Click to expand...
Click to collapse
How big is the image you are trying to install?
gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 150 kb i dont have it now but i can get it again but i did make sure the picture was below 200 kb
And when i factory data reseted the phone it still have the same logo
gcrutchr said:
How big is the image you are trying to install?
Click to expand...
Click to collapse
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Darksnite said:
Below 200 kb and i factory data reset the tablet but still the logo is there and i think my twrp is broken thats why because when i flash a file it says cant find e partion some thing but idk cuz i flashed super su again after flashing its firmwate and it worked
Click to expand...
Click to collapse
You need yo rename your image to: logo.jpg
Then use 7zip or winrar to open bootlogochanger. replace the logo.jpg in the zip file with your logo.jpg