Database Develop

Trying to flash back to stock. Bricked.

I have the WOOT sprint G tab.
I am trying to flash back to stock EA24. however i think i bricked my phone.
now i am getting a "phone triangle computer" picture on the phone and it wont do anything.. from there i have been trying to flash with odin
i installed that sprint drivers, opened odin, select the 512 pit file, select the correct binary under the "pda" option, select re-partition. but every time it gets only to this stage and fails, it also failed like this when i was in download mode.
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Enter CS for MD5..
<ID:0/005> Check MD5.. Do not unplug the cable..
<ID:0/005> Please wait..
<ID:0/005> Checking MD5 finished Sucessfully..
<ID:0/005> Leave CS..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.bin
<ID:0/005> Sbl.bin
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005> recovery.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
when it gets to this part there is part of a a small progress bar on my screen.
i then have to shut the phone off and turn it back on for odin to work at all.
kinda scared i screwed my self here.

Turn off the phone by disconnecting the USB cable, holding the power button down until the screen goes off.
Open Odin and select the tar file in the PDA slot only.(You should have remove the MD5 extension already). Do not select re partition, leave everything as it is.
Connect the USB and the device should turn on to the same PC connection to phone error screen. Wait till Odin detects the com Port and flash. Repeat until successful.

I have done this 10 times now exactly like you said, and i still get the same error.
odin 1.7 or 1.3 only selected the file SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar
everytime it shows part of a blue progress bar and odin says
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<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
<ID:0/005> Sbl.bin
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005> recovery.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I can get into recovery by using heimdall and a zimage
but from there i get a
checking /system..
E:failed to mount /system (invalid argument)
/system may be rfs. Checking...
checking /data...
checking /datadata...
E:failed to mount /datadata (invalid argument)
/datadata may be rfs. checking...
checking /cache
done!
and then e: Can't mount /sdcard
when i try to choose zip from sdcard.

Phone - triangle - computer is another download. You get that screen when you have a bad flash. Redownload your files - sometimes there is a corrupted file, causing success, but the tab won't boot, so you get the phone - triangle - computer.

I see from your computer output you are missing the dbdata.rfs file. That would explain the blank line.

[GUIDE] EFS/NV_DATA full backup and restore manually -- Extract / Post your pit file

Here i will show you how to backup & restore EFS and NV_data manually for some variants of Galaxy S5 without a third party app or tool.
Sure a third party app or tool will do the job, but it is good to learn something.....
Backuping efs partition is an essential step to keep it safe after rooting since a bad flashing/modding of your S5 may result in a corruption of that partition. so it is better to be safe than sorry, so any disturbance in the EFS data might result in null IMEI and baseband version.
This will backup data like device specific essential information such as the IMEI (International Mobile Station Equipment Identity), wireless device MAC address, baseband version, product code, system ID and NV data.
You must have a proper root access in addition to busybox installed (preferred)
you can dump these partitions also using adb shell command. but here i will show you how to backup using a terminal emulator.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to do it ​
Backup EFS/NV_data for SM-G900F/T/P/A/I/M/W8 variants:
Download "terminal emulator" app from play store and install it.
Open the app and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard/efs.img.ext4
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/modemst1.bin
dd if=/dev/block/mmcblk0p14 of=/mnt/sdcard/modemst2.bin
copy images from internal sdcard to a safe place such as pc.
Note that the size of .img and .bin must be as follow: efs (14MB) modemst1/2 (3MB each)
Restore EFS/NV_data for SM-900F/T/P/A/I/M/W8 variants:
Make sure Backuped images are in your internal sdcard (not in any folder).
open terminal emulator and type (HERE DONT MAKE MISTAKES!) :
Code:
su
dd if=/mnt/sdcard/efs.img.ext4 of=/dev/block/mmcblk0p12
dd if=/mnt/sdcard/modemst1.bin of=/dev/block/mmcblk0p13
dd if=/mnt/sdcard/modemst2.bin of=/dev/block/mmcblk0p14
​Backup EFS/NV_data for SG-900H variant:
Download "terminal emulator" app from play store and install it.
Open the app and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/efs.img.ext4
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/m9kefs1.bin
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/m9kefs2.bin
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/m9kefs3.bin
copy images from internal sdcard to a safe place such as pc.
Note that sizes of .img and .bin must be as follow: efs (20MB) m9kefs1/2/3 (4MB each)
Restore EFS/NV_data for SG-G900H variant:
Make sure Backuped images are in your internal sdcard (not in any folder).
open terminal emulator and type (HERE DONT MAKE MISTAKES!):
Code:
su
dd if=/mnt/sdcard/efs.img.ext4 of=/dev/block/mmcblk0p3
dd if=/mnt/sdcard/m9kefs1.bin of=/dev/block/mmcblk0p4
dd if=/mnt/sdcard/m9kefs2.bin of=/dev/block/mmcblk0p5
dd if=/mnt/sdcard/m9kefs3.bin of=/dev/block/mmcblk0p6
​

pit files
Extract / Post your pit file​
Pit file is needed to be flashed when the partition table of your device is corrupted due to some reason such as a wrong flash of your variant.
When partition table is corrupted or missed from your device, odin will tell you when flashing firmware that there is "no pit partition" or "Re-Partition operation failed", in this case pit file must be flashed along with the stock firmware (or alone) with "re-partition" ticked in odin.
--DO NOT flash pit file if there is no need for it--
There is some ways to extract pit file from your device such as using "heimdall" or some tools.
Here i will show you how to extract the pit file manually with a simple way using terminal emulator or adb shell command.
your phone must have a proper root access, with busybox installed (preferred).​
how to do it​
With terminal emulator:
Download and install terminal emulator from play store.
Open it and type:
Code:
su
Grant permission
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
See the pit file in your internal sdcard, move it to pc
With adb shell:
You must have android sdk installed in your pc.
Enable "usb debugging" in "developer options", connect your phone to pc, open a cmd window (shift+right mouse click) and type:
Code:
adb devices
adb shell
su
Grant permission
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
See your pit file in your internal sdcard and move it to pc.
​Please attach the extracted pit file in a zip in this thread and mention your S5 variant name and storage (16/32GB) that other users can benefit from it
THX to
@linty
@xtechx
@fffft
@jeffreylin_
@tdunham
@ratatouille
@LoSt180
@babygau
@felstar
@born4trance
@demdix
@qwerty22
@/ofAllEvil
@Max One
@hawst
 @androidrouen

reserved

attachment and content removed, can delete post if desired.

xtechx said:
thanks! I've attached a PIT from my phone, if anyone needs it
Click to expand...
Click to collapse
hmm... can not open it with pit magic tool
there is something wrong.
can you post outcome of
Code:
cat /proc/partitions

attachment and content removed, can delete post if desired.

xtechx said:
weird. I'm running it from Ubuntu 14.04, x64, but I don't think that should matter. I have a couple Windows systems here too... I'm suspect of this cable, it seemed to damage a zip file I tried to flash once (was supposed to be 570MB< but it only copied 70MB)...but everything else has copied fine, including that file when I did it a second time...so not sure...
I re-ran the command, just in case. I've also included the output from /proc/partitions
addition: this time I zipped it on my computer, where as last time I zipped it with root explorer
Click to expand...
Click to collapse
ok, try with this command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176

samersh72 said:
ok, try with this command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
Click to expand...
Click to collapse
Done

xtechx said:
Done
Click to expand...
Click to collapse
:good: yes it worked!
thank you
i will add it to second post

samersh72 said:
:good: yes it worked!
thank you
i will add it to second post
Click to expand...
Click to collapse
You're welcome! I'll edit my posts to remove the bad zip files, so that no one downloads them by mistake.

SM-G900F pit file added.

Looking for someone rooted that is willing to create an SM-G900T (Tmobile) PIT that can be used with Heimdall or JOdin. No Windows machines in my house.
Thanks!

i have this error msg with SM-G900F pit
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANCE_G900FAUT1ANC7_G900FXXU1ANCE_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

joeknoob said:
i have this error msg with SM-G900F pit
Click to expand...
Click to collapse
I see problem in connection at first flash
But in second step Pit is set properly.
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Try another computer
Why you are flashing with pit?
Sent from my N91

It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance

..

samersh72 said:
It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance
Click to expand...
Click to collapse
i need pit for my G900F - 16GB AUT (Switzerland)
this is reason for my flashfail
(sorry for my bad english)

jeffreylin_ said:
.pit file for the SM-G900H 16 GB variant.
Click to expand...
Click to collapse
thank you, but the zip is empty!?

jeffreylin_ said:
Huh, that was weird. Let me try that again.
Click to expand...
Click to collapse
Pit Zip added! thank you :good:

samersh72 said:
It seems that certain G900F S5 had a different partition layout that could cause flashing to fail on the "size" of Hidden.img. (as Note 3 phone)
I need some users from different countries with a SM-G900F (16GB) to extract pit file from their rooted phones (follow second post of this thread).
thanks in advance
Click to expand...
Click to collapse
Hi.
I have this problem too. I`m searching pit file g900f for firmware (SER) region Russia. Maybe you have this file?

Flashing ROM is failed

Hi,
I have Samsung Galaxy S3 I9305 LTE phone made in Vietnam. Initially I got the Samsung Logo stuck issue. In the stock recovery mode i got the following error.
"E:failed to mount /efs (Invalid argument)".
I tried to wipe cache partition and checked. but no luck.
Then I rooted the phone using the following file:
CF-Auto-Root-m3-m3zh-gti9305.tar.zip
Then i installed the CWM recovery using the following file:
CWM_touch_6.0.4.7_i9305.tar
Then I went to CWM recovery and did the following things:
back up to /SD card
wipe data/factory reset
format /system
format /data
wipe dalvik cache
then First I tried to flash the 2 ROMs(I9305XXUFNL1_I9305H3GFNL1_I9305XXUFOA1_HOME.tar.md5 and I9305XXUFNL1_I9305ORLFOB1_I9305XXUFOA1_HOME.tar.md5) . Both are installed. but logo issue was still there. Then I found the ROM(I9305XXUENH1_I9305FTMENJ1_I9305XXUENG1_HOME.tar.md5) using KIES using model no and serial no.
I flashed that ROM using ODIN and ROM installation is failed. Following is the ODIN Log.
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007> tz.img
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed.
Then I went to Android Recovery Mode and still I'm getting the following error:
"E:failed to mount /efs (Invalid argument)".
Note: I did not do any mount in recovery mode
Please help me on this.

Help with extracting AT&T S5 G900A Stock Rom and change Language

hi guys i need your help
my phone S5 G900A AT&T Rom 5.1.1 With no root and can't downgrade or add custom recovery
i need unpack to change my phone language and delete AT&T Programs in lollipop ROM 5.1.1 stock ROM
I made the next steps.. if could clarify the wrongs in those steps .. thank you very much
i am using ubuntu 16.04 LTS
first : i have stock ROM with 4 files AP - BL - CP - CSC
G900AUCU4COI5_CL5869384_QB6398515_REV00_user_low_s hip_MULTI_CERT
i need to extract AP_G900AUCU4COI5_CL5869384_QB6398515_REV00_user_lo w_ship_MULTI_CERT.tar.md5
and edit system.img.ext4
by right click on file system.img.ext4 and open with ARK and extract it
now i have those files boot.img - persist.img.ext4 - recovery.img - system.img.ext4
I've downloaded "img-tools" to change ext4 to img
i take a system.img.ext4 file and but it in img-tools folder in my home and do this commands
right click and chose Open in Terminal in img-tools folder
sudo su
enter password
simg2img system.img.ext4 system.img
makdir system
mount -t ext4 -o loop system.img system/
Click to expand...
Click to collapse
now i have mounted system.. i well open it with this command
sudo nautilus
enter password
Click to expand...
Click to collapse
and delete APK files >
Code:
system/APP/*.APK
system/framework/framework-res.apk
system/framework/twframework-res.apk from the same ROM
and replace it with the same files from other ROM S5 G900H lollipop 5.1.1 with national language
when finished i need to repack files with this command
tune2fs -l system.img | grep "Block size"
Block size: 4096
tune2fs -l system.img | grep "Block count"
Block count: 656384
ech $((4096 * 656384))
2688548864
make_ext4fs -s -l 2688548864 -a system system.img.ext4 system
Click to expand...
Click to collapse
now i have my edited sysytem.img.ext4
i need to but it back in the same folder with the next files to repack it in "tar.md5" file to flash it
Code:
boot.img
persist.img.ext4
recovery.img
this commands well do it
tar -H ustar -c boot.img persist.img.ext4 recovery.img system.img.ext4 > my_final_packeg.tar
md5sum -t my_final_packeg.tar >> my_final_packeg.tar
mv my_final_packeg.tar my_final_packeg.tar.md5
Click to expand...
Click to collapse
finally i have the last file to flash it ((my_final_packeg.tar.md5))
the problem is when i flash it by odin3 v3.11 i have this massage
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> persist.img.ext4
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL (auth)!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
i need your help and Sorry about my bad language

Softbricked my old Galay GT P1000 - can anyone help.

Heyas. I'm hoping someone can point me in the right direction. I'm trying to refresh an old Galaxy Tab (GT-P1000) for my son. Not the first time I've done this but the first time I've hit a deadlock.
I've reviewed the [Guide]How to unbrick your galaxy tab. Not helping unfortunately.
Background:
I've installed TWRP (CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar) on the device using ODIN. Installed OK. Booted into the OS fine afterwards.
I copied the firmware (cm-13.0-20160519-UNOFFICIAL-p1.zip) and GAPPS from the microsd card to the /download folder as I've had issues seeing the card from the recovery app.
Booted into recovery - did a system, data and dalvik cache wipe. Installed the CM13 image and rebooted. The message I got was:
failed to mount '/system' (invalid argument)
failed to mount '/data' (no such device)
In an attempt to fix the mount issues I reflashed including a PIT. Now nothing is mounting - I'm guessing I've blown away the partitions.
I can get to the Clockwork recovery application but I can't flash from the SD card as it needs a file system to mount to I'm guessing.
Can anyone point me in the right direction to begin troubleshooting this?
If I try to reflash using ODIN, a PIT file and GB_Stock_Safe_v5.tar
ODIN zips through till it gets to:
<ID:0/004> factoryfs.rfs
At which point it seems to hang up.
eventually ODIN times out with a Fail message. If I reboot I get the soft brick logo of the mobile and PC with the yellow triangle. From this point I can reflash Clockwork Recovery Mod (CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar) and get to the download screen again if need be.
I just don't seem to be able to get a working OS up.
Message log reads:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> cache.rfs
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> Removed!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)