Welcome.
I have big problem, and I hope You will help me
Couple days ago, I tried Install bootanimation on following way:
-rename the animation you download to "bootanimation.zip"
-paste the bootanimation.zip you downloaded into your sdcard,anywhere is fine
-use root explorer open the system/bin
-look for the "samsungloop" file, move it to your sdcard first, just in case, you can either move it or copy it again to another place, (in my case, i copy it into system/ and another to my sdcard)
-go to system/bin ,look for "bootanimation", and rename it to "samsungloop", if you use ROOT explorer, don't forget to change the previlege first, change R/W permission first to R/O,,,(the bootanimation is not the file where you rename your animation you downloaded to be bootanimation.zip)
-put the "bootanimation.zip" (the file you downloaded and rename it's names) to
system/media
-in system/media, there are 2 files if i'm not mistaken, bot of the files are with the extension .qmq, just rename it with root explorer to .qm extension file
-reboot your galaxy ACE
-done
I know it's for Galaxy Ace but I thought it will work.
Unfortunately in not. Moreover I became like fool because I didn't made backup. And Now I have problem.
So what I've done:
- in systen\bin, copy file samsungani (there wasn't samsungloop file) to other folder, and change name bootanimation file on samsungani
-in system\media, I made that change: -in system/media, there are 2 files if i'm not mistaken, bot of the files are with the extension .qmq, just rename it with root explorer to .qm extension file
- and copy bootanimation.zip to system\media
Then I reboot my SGS2 and I since that time I have bootloop.
I tried get to my system files by pc through total commander with adb plug, through adb shell, through android commander. All that programs can't see my phone. Moreover my pc see phone, but if I get into phone folder, every file has 0b
I thought "I install another ROM", so I tried through Odin3 v1.85 install that ROM, but it stopped on it:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
Here I tried install ROM downloaded directly from samsung site: I9100BVLPH_I9100TMULPH_TMU
I tried install ROM directly from sdcard through RECOVERY, but there is communicate: E:signature verification failed
Here I tried install ROM download from that forum: http://forum.xda-developers.com/showthread.php?t=1824586
And now I don't know what to do.
Please could You help me with that?
Leonkrwawy said:
Welcome.
I have big problem, and I hope You will help me
Couple days ago, I tried Install bootanimation on following way:
-rename the animation you download to "bootanimation.zip"
-paste the bootanimation.zip you downloaded into your sdcard,anywhere is fine
-use root explorer open the system/bin
-look for the "samsungloop" file, move it to your sdcard first, just in case, you can either move it or copy it again to another place, (in my case, i copy it into system/ and another to my sdcard)
-go to system/bin ,look for "bootanimation", and rename it to "samsungloop", if you use ROOT explorer, don't forget to change the previlege first, change R/W permission first to R/O,,,(the bootanimation is not the file where you rename your animation you downloaded to be bootanimation.zip)
-put the "bootanimation.zip" (the file you downloaded and rename it's names) to
system/media
-in system/media, there are 2 files if i'm not mistaken, bot of the files are with the extension .qmq, just rename it with root explorer to .qm extension file
-reboot your galaxy ACE
-done
I know it's for Galaxy Ace but I thought it will work.
Unfortunately in not. Moreover I became like fool because I didn't made backup. And Now I have problem.
So what I've done:
- in systen\bin, copy file samsungani (there wasn't samsungloop file) to other folder, and change name bootanimation file on samsungani
-in system\media, I made that change: -in system/media, there are 2 files if i'm not mistaken, bot of the files are with the extension .qmq, just rename it with root explorer to .qm extension file
- and copy bootanimation.zip to system\media
Then I reboot my SGS2 and I since that time I have bootloop.
I tried get to my system files by pc through total commander with adb plug, through adb shell, through android commander. All that programs can't see my phone. Moreover my pc see phone, but if I get into phone folder, every file has 0b
I thought "I install another ROM", so I tried through Odin3 v1.85 install that ROM, but it stopped on it:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.bin
Here I tried install ROM downloaded directly from samsung site: I9100BVLPH_I9100TMULPH_TMU
I tried install ROM directly from sdcard through RECOVERY, but there is communicate: E:signature verification failed
Here I tried install ROM download from that forum: http://forum.xda-developers.com/showthread.php?t=1824586
And now I don't know what to do.
Please could You help me with that?
Click to expand...
Click to collapse
Have you made a nandroid backup?
Sent from my potato running a potato.
Related
This is a quick guide for anyone who needs instructions on how to return to stock or unbrick using a Mac (OSX) as I know I've seen a lot of people ask how. Since I just got rid of my Windows machine permanently, I figure I'd share my methods with others.
THIS GUIDE CAN GLADLY BE ADDED TO OTHER "HOW-TO" GUIDES, AND I WILL DELETE THIS ONE AFTER THAT, IF NEED BE.
This is actually much much simpler than I originally thought it would be.
RETAIL EDITION INSTRUCTIONS
Downloads:
Heimdall: http://glassechidna.com.au/heimdall/ Credit Benjamin Dobell
Factory Images for VZW Note 3: http://www.androidfilehost.com/?fid=23269279319196106 Credit Beanstown106
Unarchiver (or equivalent): Search your Mac App Store or google search - Its free - https://itunes.apple.com/us/app/the-unarchiver/id425424353?mt=12
Pre-install and unpack stuff:
Double click and install Heimdall. Self explanatory instructions, nothing special. Reboot if requested.
Double click and install The Unarchiver. Also self explanatory instructions. Reboot if requested.
Double click the ALL_N900.....7z file from beans to extract the files out of it. It will become .tar.md5 file. (select open with -> Unarchiver if nec.)
Double click the .tar.md5 file you just created to extract its contents as well. This will become a desktop folder with the actual images inside it.
Move those factory images you just unpackaged to your root user folder (or wherever you choose for this magic to happen).
Open Terminal (comes pre-installed in OSX)
Ready to Rock-N-Roll:
DO NOT FLASH THESE YET, this is just to show you the commands you are performing.
Code:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --MODEM modem.bin
heimdall flash --SBL1 sbl1.mbn
heimdall flash --DBI sdi.mbn
heimdall flash --ABOOT aboot.mbn
heimdall flash --RPM rpm.mbn
heimdall flash --TZ tz.mbn
heimdall flash --BOOT boot.img
heimdall flash --RECOVERY recovery.img
heimdall flash --PERSIST persist.img.ext4
heimdall flash --SYSTEM system.img.ext4
heimdall flash --CACHE cache.img.ext4
The reason you do not want to flash ^^^those yet is that Heimdall will reboot the phone between each flash, so why not just do it all in one command, right?
Here (make sure you get the whole thing, it scrolls to the right):
Code:
heimdall flash --APNHLOS NON-HLOS.bin --MODEM modem.bin --SBL1 sbl1.mbn --DBI sdi.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --BOOT boot.img --RECOVERY recovery.img --PERSIST persist.img.ext4 --SYSTEM system.img.ext4 --CACHE cache.img.ext4
I have not done this with retail version yet, only dev edition (instructions below).
All done. Make sure to boot to recovery and wipe data / factory reset before usage.
Enjoy.
DEV EDITION INSTRUCTIONS
Downloads:
Heimdall: http://glassechidna.com.au/heimdall/ Credit Benjamin Dobell
"Factory" Images for VZW Dev Edition Note 3: http://www.androidfilehost.com/?fid=23269279319196402 Credit Beanstown106 - created package
Unarchiver (or equivalent): Search your Mac App Store or google search - Its free - https://itunes.apple.com/us/app/the-unarchiver/id425424353?mt=12
Pre-install and unpack stuff:
Double click and install Heimdall. Self explanatory instructions, nothing special. Reboot if requested.
Double click and install The Unarchiver. Also self explanatory instructions. Reboot if requested.
Double click the DevEdition.7z file from beans to extract the files out of it. It will become .tar.md5 file. (select open with -> Unarchiver if nec.)
Double click the .tar.md5 file you just created to extract its contents as well. This will become a desktop folder with the actual images inside it.
Move those factory images you just unpackaged to your root user folder (or wherever you choose for this magic to happen).
Open Terminal (comes pre-installed in OSX)
Ready to Rock-N-Roll:
DO NOT FLASH THESE YET, this is just to show you the commands you are performing.
Code:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --BOOT boot.img
heimdall flash --MODEM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --SYSTEM system.img.ext4
heimdall flash --CACHE cache.img.ext4
The reason you do not want to flash ^^^those yet is that Heimdall will reboot the phone between each flash, so why not just do it all in one command, right?
Here (make sure you get the whole thing, it scrolls to the right):
Code:
heimdall flash --APNHLOS NON-HLOS.bin --BOOT boot.img --MODEM modem.bin --RECOVERY recovery.img --SYSTEM system.img.ext4 --CACHE cache.img.ext4
All done. Make sure to boot to recovery and wipe data / factory reset before usage.
Enjoy.
That was a really good post
Thank you for awesome guide. I have been struggling with mac for a really long time, I had to bootcamp for all of my Android needs. This definitely starts to break that barrier.
jmichaels1982 said:
Thank you for awesome guide. I have been struggling with mac for a really long time, I had to bootcamp for all of my Android needs. This definitely starts to break that barrier.
Click to expand...
Click to collapse
No problem. Same for me, this was my way of finally getting rid of my bootcamp partition :good:
Sent from my Galaxy Note 3 Developer Edition
Good Job!! Mac users needed some Luv
droidstyle said:
Good Job!! Mac users needed some Luv
Click to expand...
Click to collapse
Speaking of which....didn't I read somewhere that fastboot commands actually work on Dev Edition devices? I'd just try it but I'm at work right now...
EDIT: Nope, they don't work.
Sent from my Galaxy Note 3 Developer Edition
OP modified to add full retail instructions as well.
Hi, was wondering if this would work for my Sprint Note 3?
My phone is currently soft bricked.
Thank you so much to anyone who can answer this. Needless to say, it's been frustration so far with my limited knowledge.
???
Greetings
I need some help with packing a compiled image of the Samsung Source into a flashable image. After that I downloaded the stock image of my phone from SamMobile, and unpacked it. I then used an script called umkbootimg to replace the zImage in boot.img with mine and can created another boot.img. Here is what I have now:
stock3$ ls
aboot.mbn recovery.img
boot.img rpm.mbn
cache.img.ext4 sbl1.mbn
initramfs.cpio.gz sdi.mbn
modem.bin SS_DL.dll
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 system.img.ext4
N900PVPUCNC5_N900PSPTCNC5_SPR.zip tz.mbn
NON-HLOS.bin zImage
I have tried to use tar –H ustar –C command to pack the files into a tar ball. I then added md5, and zipped the whole thing with zip command. But could not use twrp to flash it. I have also looked into Odin and Heimdall. The greatest success I have had so far has been an image that puts my phone into boot loop, and I had to recover. What is the fastest way I can create an image from this?
[Q&A] [APP] Updated: 31/10/12 - PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Ana
Q&A for [APP] Updated: 31/10/12 - PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [APP] Updated: 31/10/12 - PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Bad link
lyriquidperfection said:
PIT Magic is the All In One solution for Creating, Editing and Analyzing Samsung PIT Files.
What are Samsung PIT Files?
PIT files contain the Partition Information Table (PIT) for Samsung Android phones. Different firmware versions may require different partition layouts so the necessary PIT file 'tells' Odin how to set up the phone partitions correctly for the specified firmware to be installed.
The PIT file contains all the relevant information for each required partition such as Partition Name, Flash File Name, Block Size, Block Count etc. and also contains some unknown properties that maybe identifiers or flags of some sort.
PIT Magic's Main Features:
Create New PIT Files from scratch.
Edit Existing PIT Files and change all available properties.
Analyze a PIT File and create a human readable report of all Partition entries.
Export PIT Analysis to Text File or Copy to Clipboard direct from the User Interface.
Add or Remove Partition entries to a New or Existing PIT File.
Save options to write changes to Existing PIT File or write a New PIT File altogether.
Whats NEW in PIT Magic v1.3.10
1. Removed Unknown PIT File Properties #1 to #8 and replaced with 5 Dummy Data Blocks consisting of 4 bytes each as per the Samsung PIT File Specification.
2. Changed the 'Unknown PIT File Properties' Group to PIT File Header Information.
3. Added Option to Display Dummy Data in String or Hexadecimal Format.
4. Fixed a bug with the Reset Form Button. Now it will undo changes made to the PIT File Header Dummy Data fields as well as the currently selected PIT Entry.
5. Changed the layout of the User Interface and made a few slight cosmetic adjustments.
6. Changed the layout of the PIT File Analysis Report to reflect the changes to the PIT Header Information.
7. Fixed a few bugs regarding loading and saving of PIT Files in the User Interface.
8. Removed some redundant and duplicated code and tidied it up in a few places.
9. Fixed PIT File Modified prompt when Creating New / Open Existing / Exit Application. Changes made are now detected properly including to PIT Header Information.
Whats NEW in PIT Magic v1.1.4
1. Changed File Name to Flash File Name and Added FOTA File Name.
2. Changed Chip Identifier to Binary Type.
3. Changed Partition Identifier to Device Type.
4. Changed Partition Flags to Identifier.
5. Changed Unused to Attribute.
6. Changed Unknown #1 in PIT Entry to Update Attribute.
7. Changed Unknown #2 to File Offset and Unknown #3 to File Size. (Obsolete PIT Parameters).
8. Added Thousand separator text formatting to Block Size and Block Count in the User Interface and Analysis UI.
9. Updated User Interface and fixed a few file modified detection bugs that failed to prompt user to save changes on Exit / Open / New.
10. Fixed a Null Reference bug when cancelling 'Save As...' Dialog.
Whats NEW in PIT Magic v1.0.8
Initial Release.
Click to expand...
Click to collapse
The Link is Bad (as of today - 12/29/2014) -- Link: PIT_Magic_v1.3.10_Release.zip (Dev-Host) if goes to website "d-h.st/2CW" which is an EZdownload executable.
Quote:
Download Link: PIT_Magic_v1.3.10_Release.zip (Dev-Host)
Hey, just downloaded PIT Magic to try to fix Samsungs idiocy with the storage partitions, and it seems like I'm in over my head..
I want to change it so that instead of having 2.5Gb for System (I only use 600Mb), to have 1Gb for system, and then move that other 1.5 Gb to usable storage. It seems kinda silly to have all that free space that I can't really use!
If anyone could help me, I would very greatly appreciate it.
Device is S4, JFLTE, i9505.
I've added a screenshot of my disk info to help. Also I'm running CarbonROM if that makes any difference.
Thanks again!
dont't work
this don't work on samsung galaxy s5 model sm-g900f . i tryed to load original pit and re-save ,without modify nothing , but odin write error :
FAIL!
Re-Partition operation failed.
on phone write secure cecheck fail : pit
how do I fix?
win8
wil pit magic work on windows 8?
Anyone have pit 16gb for I8190? Or how to make it from 8gb pit file? which one do i need to edit?
Hi,
How to extract modem.bin ? I extract rom but i don't see the modem.bin...
Just :
boot.img
cm.bin
recovery.img
sboot.bin
system.img
thx
Edit : i use izarc and is bad, with 7zip i can see all files and folders, and modem.bin, sorry.
Now i can extract the modem and bootloader from french providers.
Hi xda, this is my algorithm about best thing that you can to bypass frp (that acutally i follow) in order to flash system.img also questionning to resolve my problem, thanks for reading.
PART1 - Download the stock firmware full factory including, BL | AP | CP | CSC.
PART2 - Using ImgExtractor and editing file as needed means remove bloatware[...]
[Q] If you modify content of system.img, do you must absolutely repack to same bytes plus 100M, in order to flash it?
PART3 - Using make_ext4fs to repack system.img
[Q]Do i need pit file for ext4 partition cause odin3 throw me the following :
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> system.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
PART4 - MAKING THE FLASHABLE TAR FILE
[Q]What type of odin3 accept ?
1. So now you should have the image file you want to flash but you need to get it in to a .tar format that can be flashed by Odin. Copy the .img file to the INPUT folder in the Toolkit (v1.2.7 or later) and start the Toolkit. Type option ’99’ to load up the Basic Toolkit. In the Main Menu of the Basic Toolkit select option ‘8’ (Create an Odin flashable tar). In the next menu choose option 2 to make a single tar file from multiple images (it doesn’t matter that you only have 1 image).
2. Make sure that ONLY the image you need to flash is displayed in the list (.img or .img.ext4) and type yes to start. If the file is a system image then it will take a while to convert but eventually it should say completed and you will have a .tar file in the OUTPUT folder. This is your flashable file.
PART5 - – FLASHING THE TAR FILE
1. Once you are back in the Main Menu of the Basic Toolkit select the ‘Device Reboot Options’ section and ‘Reboot to Download Mode and Start Odin’. If you can not boot your device in to Android with adb debug enabled (needed for this option) then just unplug your usb cable, hold Volume Down, Home and Power buttons until you get a warning screen and press Volume Down to get in to Download Mode. Then you can run Odin3_v3.09.exe from Toolkit folder. Now connect your usb cable and the box under ID:COM should be blue.
2. Make sure ‘Auto Reboot’ and ‘F. Reset Time’ is ticked.
3. Click on ‘PDA’ / ‘AP’ and browse to the Toolkit, OUTPUT folder. Click on the tar file (it will start with CREATED-TAR) and then click on Open. When you are ready hit the “Start” button and the flash process should start. This may take a while depending on the image you are flashing. A progress bar will be displayed on the device and on Odin to let you know how it’s going.
4. After the flash finishes your device will reboot and if everything went fine the new image will be flashed and your device should boot without any problems.
-PART6 - Deal with XDA (lol) when odin3 throws FAIL(<ID:0/004> Complete(Write) operation failed.)
Well as extra, there a pit file for hidden img that fix FAIL(<ID:0/004> Complete(Write) operation failed.)
WHAT CAN I DO FOR SYSTEM.IMG ? :fingers-crossed: