Database Info

[new odin](3.09.3)

We got a new version of ODIN-3 - (3/09/3)
Version came with firmware service for S4
http://4pda.ru/pages/go/?u=https://mega.co.nz/#!AUJGABDS!QHrlq0_jaUsqpi1lJNE8ggVgH-x-053kETte7ySzilk
{
"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"
}
use please))
View attachment 2436518

I wonder what's different...
Sent from my SM-N9005 using Tapatalk

Where You see 3.9.3? I see Odin3 v3.09

<id:0/004> fail!
Hi Everyone!
This is my 1st post in any fourms ever. I always get solutions by searching, but i guess am umable to find a correct solution for this . Am hoping if someone could re-direct me to fix my phone.
Issue:
My screen is stuck on the boot screen ( Galaxy Note 2 N7100 - screen). It doesnt go further.
Background:
I was using Diamond ROM for quite a long time. I have no clue, last night i was talking to someone and later i kept my phone in pocket and since then its stuck on that screen. I am not sure what happened or what caused it
I am using Philz Recovery, but when am booting to it
it has the below Error:
PhilX Touch 6.26.6
Clockworkmod v6.0.4.8
E:Could not mount /data to setup /data/media path!
E:Can't mount /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
I Tried everything possible (restarted may times, tried to wipe off the cache - it was not wiping)
Then i thought to reinstall PhilZ.
WHen i went to the download recovery on my phone and connected to odin v3.09 (which i used last time when installing custom ROM and it worked) phone is getting added.
But when i select AP to the PhilZ recovery file (philz_touch_6.26.6-n7100.tar.md5) and click on Start it is giving me error and it failed
Error:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.26.6-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Someone Please Help me

ajithravi said:
Hi Everyone!
This is my 1st post in any fourms ever. I always get solutions by searching, but i guess am umable to find a correct solution for this . Am hoping if someone could re-direct me to fix my phone.
Issue:
My screen is stuck on the boot screen ( Galaxy Note 2 N7100 - screen). It doesnt go further.
Background:
I was using Diamond ROM for quite a long time. I have no clue, last night i was talking to someone and later i kept my phone in pocket and since then its stuck on that screen. I am not sure what happened or what caused it
I am using Philz Recovery, but when am booting to it
it has the below Error:
PhilX Touch 6.26.6
Clockworkmod v6.0.4.8
E:Could not mount /data to setup /data/media path!
E:Can't mount /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
I Tried everything possible (restarted may times, tried to wipe off the cache - it was not wiping)
Then i thought to reinstall PhilZ.
WHen i went to the download recovery on my phone and connected to odin v3.09 (which i used last time when installing custom ROM and it worked) phone is getting added.
But when i select AP to the PhilZ recovery file (philz_touch_6.26.6-n7100.tar.md5) and click on Start it is giving me error and it failed
Error:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.26.6-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Someone Please Help me
Click to expand...
Click to collapse
OK so 1st question, is debugging mode on? 2nd, have you tried another recovery? Cwm or twrp? 3rd) have you tried a factory reset? Do you have a backup? If so try to restore it, failing all of the above try to flash stock ROM via Odin (as long as debugging mode is on)
Sent from my GT-I9195

I use Odin 3.10.6
http://forum.xda-developers.com/showthread.php?t=2711451
N9005 HLTE:
Rom: Audax_L
Kernel: Fulgor
Recovery: TWRP

jimbomodder said:
OK so 1st question, is debugging mode on? 2nd, have you tried another recovery? Cwm or twrp? 3rd) have you tried a factory reset? Do you have a backup? If so try to restore it, failing all of the above try to flash stock ROM via Odin (as long as debugging mode is on)
Sent from my GT-I9195
Click to expand...
Click to collapse
Thanks for your kind response
So for the 1st one: Am not sure as my phone is not booting (It is stuck at Samsung Galaxy N7100 screen).
2nd: I tried to put another recovery via odin, it still didnt work ( got the same error as mentioned earlier)
3rd: In PhilZ recovery i tried all the possible options (wiping everything/factory reset but nothing works .... it gives Installation aborted .... or format aborted.....and above that it fails on opening the recovery path (E: )
and next:
I tried everything possible with the current recovery, but it fails on every step as its unable to access.
And i tried to flash it again with Odin, but it fails. I guess if am able to flash via Odin, the issue could be resolved. But itsays fail as mentinoed on the earlier error (under Odin error)
Hoping you could help me how to get another recovery installed or something.
---------- Post added at 07:51 PM ---------- Previous post was at 07:32 PM ----------
Ryya said:
I use Odin 3.10.6
http://forum.xda-developers.com/showthread.php?t=2711451
N9005 HLTE:
Rom: Audax_L
Kernel: Fulgor
Recovery: TWRP
Click to expand...
Click to collapse
Tried with all versions of Odin .... nothing worked

ajithravi said:
Thanks for your kind response
So for the 1st one: Am not sure as my phone is not booting (It is stuck at Samsung Galaxy N7100 screen).
2nd: I tried to put another recovery via odin, it still didnt work ( got the same error as mentioned earlier)
3rd: In PhilZ recovery i tried all the possible options (wiping everything/factory reset but nothing works .... it gives Installation aborted .... or format aborted.....and above that it fails on opening the recovery path (E: )
and next:
I tried everything possible with the current recovery, but it fails on every step as its unable to access.
And i tried to flash it again with Odin, but it fails. I guess if am able to flash via Odin, the issue could be resolved. But itsays fail as mentinoed on the earlier error (under Odin error)
Hoping you could help me how to get another recovery installed or something.
---------- Post added at 07:51 PM ---------- Previous post was at 07:32 PM ----------
Tried with all versions of Odin .... nothing worked
Click to expand...
Click to collapse
Sounds like debugging may be off which is stopping you flashing anything, have you tried downloading stock firmware?
Sent from my GT-I9195

Try to flash TWRP 2.6.0.1, before flashing pull the battery out of the phone for a good minute.
N9005 HLTE:
Rom: Audax_L
Kernel: Fulgor
Recovery: TWRP

E:Can't mount /dev/block/mmcblk0p1

Has anyone figured out how to repair this error yet??? i've spent 4 days reading forums and google and whatnot and still i cant get this problem fixed. either solutions are for i9000 and not for infuse so procedures and roms are different. those who have infuse have not solved this error so i have no steps to follow. i've flashed like 7 different roms (some stock some modded) and nothing! i'm at my wits end i've been on and off on fixing this phone since 2013..... and anyone help me figure this out?? i'll answer all questions asap!

marielacvn said:
Has anyone figured out how to repair this error yet??? i've spent 4 days reading forums and google and whatnot and still i cant get this problem fixed. either solutions are for i9000 and not for infuse so procedures and roms are different. those who have infuse have not solved this error so i have no steps to follow. i've flashed like 7 different roms (some stock some modded) and nothing! i'm at my wits end i've been on and off on fixing this phone since 2013..... and anyone help me figure this out?? i'll answer all questions asap!
Click to expand...
Click to collapse
What's the consequence of this error? What are you doing when this error comes up? Any other messages?
I remember this one popping up before while flashing and it not meaning anything. Everything flashed fine. Mind you, this may have been with my primary phone, I cannot remember.
This Infuse thread may be of some help (or not, let me know):
http://forum.xda-developers.com/showthread.php?t=1581977

joel.maxuel said:
What's the consequence of this error? What are you doing when this error comes up? Any other messages?
I remember this one popping up before while flashing and it not meaning anything. Everything flashed fine. Mind you, this may have been with my primary phone, I cannot remember.
This Infuse thread may be of some help (or not, let me know):
http://forum.xda-developers.com/showthread.php?t=1581977
Click to expand...
Click to collapse
Consequence of the error is odd... I plugged my phone one night and left it charging in the morning the phone was off... When I wanted to turn it back on I got this error. This is not the only error.... I get another one E:copy_dbdata_media:Can't mount SDCARD
As for the link I've read that thread over and over and it was of no help because I did everything he did and still no results

marielacvn said:
Consequence of the error is odd... I plugged my phone one night and left it charging in the morning the phone was off... When I wanted to turn it back on I got this error. This is not the only error.... I get another one E:copy_dbdata_media:Can't mount SDCARD
As for the link I've read that thread over and over and it was of no help because I did everything he did and still no results
Click to expand...
Click to collapse
Sounds like a hardware error. Are you able to go into download mode? How about recovery? Do you have CWM, TWRP, or stock recovery? If you have the first two are you able to make and restore backups, and otherwise access the SD cards?
Finally, are you running stock, or a custom ROM? I see you mentioned earlier that you switched ROM's so even if it's happening with stock, then it's becoming less of a software issue in my thoughts. But if you have full access in recovery, then that would squash those thoughts. At that point, I would try to find a working ROM.

joel.maxuel said:
Sounds like a hardware error. Are you able to go into download mode? How about recovery? Do you have CWM, TWRP, or stock recovery? If you have the first two are you able to make and restore backups, and otherwise access the SD cards?
Finally, are you running stock, or a custom ROM? I see you mentioned earlier that you switched ROM's so even if it's happening with stock, then it's becoming less of a software issue in my thoughts. But if you have full access in recovery, then that would squash those thoughts. At that point, I would try to find a working ROM.
Click to expand...
Click to collapse
Yes I can go into Download mode and I'm able to flash successfully it just won't reboot afterwards.... It gives me the errors. The only recovery I can go into is the stock Android blue text menu. My phone is rooted and before this error I had cwm... After the error and trying to flash and recover I can't access cwm. I've tried gtgs unbrick stock rom, entopy's kernel, a couple of modded roms like aeon or legend and nothing I get the same results... Same error. But all flash successfully. Right now I'm in stock GB rom

marielacvn said:
Yes I can go into Download mode and I'm able to flash successfully it just won't reboot afterwards.... It gives me the errors. The only recovery I can go into is the stock Android blue text menu. My phone is rooted and before this error I had cwm... After the error and trying to flash and recover I can't access cwm. I've tried gtgs unbrick stock rom, entopy's kernel, a couple of modded roms like aeon or legend and nothing I get the same results... Same error. But all flash successfully. Right now I'm in stock GB rom
Click to expand...
Click to collapse
If you don't have ClockWorkMod I am assuming you are flashing all your ROMs through download mode. I thought that only stock ROMs were available for that. I learn something new everyday.
Anyways, it may be that Download mode is silently getting the write error when it comes to that partition. Did you try putting CWM back on?:
http://forum.xda-developers.com/showthread.php?t=1107881
I am really curious if you can access your (internal) SD card outside the boot process. If the partition table is shot, there is a process that repartitions everything, which in theory gets everything back to normal. It involved Odin, but I forget what the file was called. Pretty sure it was CWM itself, but I'm not sure (first reboot after installed whatever through Odin, I remember a voice alerting me to please wait while partitions are updated - about 5 minutes). I will have to look it up when I get home.

joel.maxuel said:
If you don't have ClockWorkMod I am assuming you are flashing all your ROMs through download mode. I thought that only stock ROMs were available for that. I learn something new everyday.
Anyways, it may be that Download mode is silently getting the write error when it comes to that partition. Did you try putting CWM back on?:
http://forum.xda-developers.com/showthread.php?t=1107881
I am really curious if you can access your (internal) SD card outside the boot process. If the partition table is shot, there is a process that repartitions everything, which in theory gets everything back to normal. It involved Odin, but I forget what the file was called. Pretty sure it was CWM itself, but I'm not sure (first reboot after installed whatever through Odin, I remember a voice alerting me to please wait while partitions are updated - about 5 minutes). I will have to look it up when I get home.
Click to expand...
Click to collapse
i tried putting cwm in by itself and it stays in starting connection indefinitely....this is when i just put a /tar file in odin under PDA. if i put the whole rom in with pit included and pda and phone files it's successful. this is the report i get after installing a rom with cwm included:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex-extras.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!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I997UCLB3-CWM-root-deodex-extras.tar.md5 is valid.
<OSM> PHONE_UCLB3.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..
<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> cache.rfs
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.rfs
<ID:0/004> modem.bin
<ID:0/004> zImage
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
after my phone reboots i get this message in the screen:
---installing package...
finding update package...
opening update package...
verifying update package...
installing update...\
successfully installed package.
---copying media files----
E: failed to mount/dbdata (file exists)
E:copy_dbdata_media: Can't mount/db data your storage not prepared yet, please use UI menu for format and reboot actions.
media files copy failed.
--wiping cache...
formatting/cache...\
cache wipe failed.
----appling multi-csc...
installing multi-csc
applied the csc-code 'att'
successfully applied multi-csc.
from here i proceed to wipe data/factory reset from the menu.
----wiping data...
formatting/data...
formatting/dbdata...
E: format_volume: rfs format failed on /dev/block/stl10
Deleting meta data
formatting /cache...
data wipe complete.
if i try anything else i get
E:failed to mount/sdcard (file exists)
that's pretty much where i'm at right now....... it seems i have little to no communication with the internal sd card.

marielacvn said:
that's pretty much where i'm at right now....... it seems i have little to no communication with the internal sd card.
Click to expand...
Click to collapse
That's what it's looking like. Your cache partition looks fine, so must be your root partition (or whatever holds kernel and core bootstrap). If it was a desktop computer I would say either the partition table is bunged up or the tail end of the hard drive is inaccessible. I am stumped on how to get to the former. I will look at home for the Odin CWM file I had so you don't have to flash a whole ROM. It may just sit still forever like the CWM install you have (or it may not work at all because mine may be designed for i997R - Rogers kernel), but it's worth a try, since it's the only thing I can think of.

joel.maxuel said:
That's what it's looking like. Your cache partition looks fine, so must be your root partition (or whatever holds kernel and core bootstrap). If it was a desktop computer I would say either the partition table is bunged up or the tail end of the hard drive is inaccessible. I am stumped on how to get to the former. I will look at home for the Odin CWM file I had so you don't have to flash a whole ROM. It may just sit still forever like the CWM install you have (or it may not work at all because mine may be designed for i997R - Rogers kernel), but it's worth a try, since it's the only thing I can think of.
Click to expand...
Click to collapse
I'll pretty much try anything at this point.... Haven't used the phone in almost a year so I'll practically try anything. Kind of a bummer no solution still exists for this.... I'm thinking it might just be a hardware thing either way I'm standing by...

marielacvn said:
I'll pretty much try anything at this point.... Haven't used the phone in almost a year so I'll practically try anything. Kind of a bummer no solution still exists for this.... I'm thinking it might just be a hardware thing either way I'm standing by...
Click to expand...
Click to collapse
This is what I was thinking of:
http://forum.xda-developers.com/showthread.php?t=1197248
You are probably with AT&T so this would be a bad idea. It won't brick your phone, but weirdness occours like soft reboots. So with that in mind, try this link:
http://forum.xda-developers.com/showthread.php?t=1698367
...and download Entropy512's CWM red. If this doesn't load, I don't know where to go next.

joel.maxuel said:
This is what I was thinking of:
http://forum.xda-developers.com/showthread.php?t=1197248
You are probably with AT&T so this would be a bad idea. It won't brick your phone, but weirdness occours like soft reboots. So with that in mind, try this link:
http://forum.xda-developers.com/showthread.php?t=1698367
...and download Entropy512's CWM red. If this doesn't load, I don't know where to go next.
Click to expand...
Click to collapse
first link:
i downloaded Entropy512's Daily Driver / Red CWM Recovery, flashed it and this was the summary i got from odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> 2012.04.05-ODIN-Entropy_DD-GB-zImage.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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/005> Added!!
after reboot i get this error
E:failed to mount /dbdata (invalid argument)
----copying media files...
E:failed to mount /dbdata (file exists)
E:copy_dbdata_media:can't mount /dbdata your storage not prepared yet, please use UI menu for format and reboot actions.
media files copy failed.
i also tried the same for Zen Arcade's Infusion-Z / Red CWM Recovery
2012.05.20-ODIN-Infusion-GB-Zen-CoreA-16.rar
2012.05.20-ODIN-Infusion-GB-Zen-CoreB-14.rar
same results....
as for link 2 and rooting with rogers my results were.....
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> PDA_UXKG3_rooted_no_bootloaders_v2.tar.md5 is invalid.
<OSM> End...
it was a no go.....

Try the Infused Gingerbread kernel one, after putting an AT&T stock rom back on. Guess I should have been more specific, if you were to try the Rogers route. Think it will have the same issue, but the above file is the one I used for CWM.
Sent from my MyTouch 4G Slide using XDA Free mobile app

joel.maxuel said:
Try the Infused Gingerbread kernel one, after putting an AT&T stock rom back on. Guess I should have been more specific, if you were to try the Rogers route. Think it will have the same issue, but the above file is the one I used for CWM.
Sent from my MyTouch 4G Slide using XDA Free mobile app
Click to expand...
Click to collapse
Just did it...same result....i think i'm throwing the towel in.... maybe a year from now i'll come back to it and see if anything has changed... j/k but really i think we gave it a real go. i'm always open to more ideas but for now i think its possibly fried inside... thanks for all the help though!!

No problem. Best of luck!
Sent from my MyTouch 4G Slide using XDA Free mobile app

a bit late on the reply but you might want to use the unbrick / Return to stock method in http://forum.xda-developers.com/showthread.php?t=1705260. I had this issue too trying to install new rom. This should at least get you passed the error onto working phone if it's not hardware malfunction. From there you can install cwm and do whatever. Hope this help.

if your infuse is the AT&T one you can try this as well http://forum.xda-developers.com/showthread.php?t=1524081

Young_Azul said:
if your infuse is the AT&T one you can try this as well http://forum.xda-developers.com/showthread.php?t=1524081
Click to expand...
Click to collapse
I never tried the one click version of it before.. but the normal Heimdall was a bit confusing for me compare to Odin. If I had not use Odin before Heimdall then maybe I would have gotten used to it..

scmfxt said:
I never tried the one click version of it before.. but the normal Heimdall was a bit confusing for me compare to Odin. If I had not use Odin before Heimdall then maybe I would have gotten used to it..
Click to expand...
Click to collapse
normal Heimdall is confusing but the one click isn't confusing if you read what's on the OP but that sad this is that it doesn't have root :/ and what i have noticed is when odin doesn't want to recognize your phone heimdall will....and just to get root and recovery i flashed twice with heimdall second time for the boot loaders...then i flashed through odin for the root with recovery version

marielacvn said:
after my phone reboots i get this message in the screen:
---installing package...
finding update package...
opening update package...
verifying update package...
installing update...\
successfully installed package.
---copying media files----
E: failed to mount/dbdata (file exists)
E:copy_dbdata_media: Can't mount/db data your storage not prepared yet, please use UI menu for format and reboot actions.
media files copy failed.
--wiping cache...
formatting/cache...\
cache wipe failed.
----appling multi-csc...
installing multi-csc
applied the csc-code 'att'
successfully applied multi-csc.
Click to expand...
Click to collapse
I remember fixing this problem by flashing (Odin) a "dbdata.rfs.tar" file from one of these forums. It was long ago so I don't quite remember where it was and what exactly my steps were. As far as my memory goes, I flashed I997UCLB3 via odin and then flashed "dbdata.rfs.tar". That fixed this problem. I will attach the "dbdata.rfs.tar" file on this post, hope you find a solutions :S. Sorry if you have already tried it >.<

driverless said:
I remember fixing this problem by flashing (Odin) a "dbdata.rfs.tar" file from one of these forums. It was long ago so I don't quite remember where it was and what exactly my steps were. As far as my memory goes, I flashed I997UCLB3 via odin and then flashed "dbdata.rfs.tar". That fixed this problem. I will attach the "dbdata.rfs.tar" file on this post, hope you find a solutions :S. Sorry if you have already tried it >.<
Click to expand...
Click to collapse
i've tried it already by decided what the hell i'll give it one last try again.....still nothing i'm now convinced that this is a hardware problem and not software. thanks again for the comment!
Cheers

[FILE] PIT for GT-S7275R

Hello guys! Today I bring the extracted PIT for Galaxy Ace 3 GT-S7275R, but it should work on S7275B and S7275T due to they have same mounts points.
If you want to recover your phone from bootloop, soft brick, unroot or remove custom recovery, you should flash Stock ROM via Odin. If everything goes correctly, Odin flashing process should finish without any problem. However, in some cases the process finish before flashing and an error message appears at Odin. Some of those errors are "Invalid Ext4 Image" and "Get PIT for mapping".
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..​
Android uses the EXT4 storage structure, which defines the free available storage location for system partitions. PIT file (Partition Information Table) is a Samsung internal element that contains the location of different system partitions, I mean, it allocates phone partitions.
When you're installing a firmware, Odin starts to review partitions information. If it detect PIT file, everything will finish correctly, but if PIT file is not detected or is damaged, you'll get "Get PIT for mapping" issue.
To fix this problem, you must provide PIT file for Odin to flash firmware without problem.
Besides, this file is useful if your partitions are damaged or you want to restore their values due to some partition you've made or whatever.
You must put in "PIT" section of Odin, and be sure that "Auto-reboot", "Re-partition" and "F. Reset Time" boxes are ticked.
Download: CLICK HERE
That's all! Sorry for my bad english :silly:

dude my galaxy gt-7275R device is hard bricked! i must get the data back from internal storage,is there anyway to do that? or can u give me the debrick.img file for this device.. help me it's my favorite phone

N8000 insane bug

Well, where do I start...
This is insane. lol
First I created this thread: http://forum.xda-developers.com/galaxy-note-10-1/help/battery-crazy-t3443724
So, after flashing CM13 again my battery went normal and all was perfect. It was 11pm, I set my alarm to 9am and went to bed.
I wake up the next morning without my alarm wondering why didn't it go off so I check the time and it seemed my tablet went off sometime during my sleep. Ok, no problem. I turn it on and after 6 or 7 minutes I start fearing I might be on a bootloop. I have my breakfast and come back. Yep, bootloop. I reboot it and bootloop again.
Time for TWRP. I go to Wipe -> Advanced Wipe -> Dalvik Cache and Cache and swipe to wipe.
"eek:" = O
For some reason all my Os are replaced with "eek:" whenever I save changes on the thread.
Code:
[COLOR="Red"]E:Mount: Unable to find partition for path '/sdcard'
E:Unmount: Unable to find partition for path '/sdcard'
E:Mount: Unable to find partition for path '/sdcard'[/COLOR]
Updating partition details...
[COLOR="red"]E:Unable to stat 'data/media'[/COLOR]
...done
Full SELinux support is present
[COLOR="red"]E:TWFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E:DataManager::eek:utput_Version -- Unable to make /cache/recovery[/COLOR]
MTP Enabled
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs function.
[COLOR="red"]E:DataManager:eek:utput_Version -- Unable to make /cache/recovery[/COLOR]
Updating partition details...
[COLOR="red"]E:Unable to stat '/data/media'[/COLOR]
...done
I tried a whole bunch of different things, flashing a rom again, flahsing stock rom, flashing stock through Odin...
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1101)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/009> Removed!!
Nothing on the internet works, I tried ADB but they ALL get stuck into E:Unable to stat '/data/media'. I've been working on it for the whole day and NO progress has been made. There's nothing about specifically it on the internet, there are some similar errors with unapplicable solutions.
Anybody? I need this tablet sooo much, I don't have cell phone, laptop or anything, I just have this tablet.
I'd be so thankful if anybody could help.

In recovery format data system cache .
Download stock rom and install .
Same error message you need a new motherboard .

Dang... I´m ultra screwed then. Thanks for the support. All as I suspected unfortunately.

My phone won't boot up suddenly. Please help, thanks!

It is Samsung Galaxy Note 2 (GT-N7100), unrooted, stock ROM.
It always stuck at the Samsung Galaxy Note 2 logo screen.
I can boot to recovery mode and download mode.
What should I do to save my phone? Thanks a lot.
I tried to flash by using download mode but I got these errors.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1205)..
<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> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
When repartition is checked:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1205)..
<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> Can't open the specified file. (Line: 1831)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The following errors displayed when I booted to recovery mode:
Android system recovery < 3e >
KOT49H.N7100ZSUFNL1
E:failed to mount /efs (No such file or directory)
E:failed to mount /system ((No such file or directory))
# MANUAL MODE #
--Appling Multi-CSC
E:failed to mount /system (No such file or directory)
can't mount '/system' (No such file or directory)
E:failed to mount /cache (No such file or directory)
can't mount '/cache' (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:can't mount /cache/recovery/last_recovery
E:failed to mount /data (No such file or directory)
E:can't mount /data/log/recovery_log.txt
E:failed to mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:failed to mount cache (No such file or recovery)
E:Can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or recovery)
E:can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (No such file or recovery)
Click to expand...
Click to collapse

Masterton said:
It is Samsung Galaxy Note 2, unrooted.
It always stuck at the Samsung Galaxy Note 2 logo screen.
I can boot to recovery mode and download mode.
What should I do to save my phone? Thanks a lot.
I tried to flash by using download mode but I got these errors.
When repartition is checked:
The following errors displayed when I booted to recovery mode:
Click to expand...
Click to collapse
You seem to have wiped out EFS and system, yikes. Losing EFS typically doesn't go well unless you have an EFS backup to restore it.
Have you tried finding a OTA update or stock update.zip for your model number? If you find one you can flash it in stock recovery.
Sent from my SM-S903VL using Tapatalk

Have you tried finding a OTA update or stock update.zip for your model number? If you find one you can flash it in stock recovery.
Click to expand...
Click to collapse
It is GT-N7100.
I'm not good at it. What is OTA update?
Where could I find the proper OTA update or stock update?
Should I use flash it again using ODIN and download mode? Thank you.

Masterton said:
It is GT-N7100.
I'm not good at it. What is OTA update?
Where could I find the proper OTA update or stock update?
Should I use flash it again using ODIN and download mode? Thank you.
Click to expand...
Click to collapse
Google searching will answer all of your questoons, use your model number to search for a stock update that can be flashed by using your stock recovery(it must be a stock update.zip, it can't be a custom ROM .zip)
Do a Google search for:
"What is android OTA update"
"OTA update for (your model number)"
Or
"Stock update.zip for (your model number)"
Simple google searches will find what you need, all it requires is for you to use the right search terms, it not hard, it's just common sense.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Google searching will answer all of your questoons, use your model number to search for a stock update that can be flashed by using your stock recovery(it must be a stock update.zip, it can't be a custom ROM .zip)
Do a Google search for:
"What is android OTA update"
"OTA update for (your model number)"
Or
"Stock update.zip for (your model number)"
Simple google searches will find what you need, all it requires is for you to use the right search terms, it not hard, it's just common sense.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
It looks like it refers to over-the-air update, but it doesn't seem like to mean updating over Wi-Fi or wireless broadband, without plugging via USB to perform the update.
I tried but there are multiple options.
My phone won't boot up now. I couldn't even flash a stock ROM successfully. How could I perform an update?

Masterton said:
It looks like it refers to over-the-air uupdate, but it doesn't seem like to mean updating over Wi-Fi or wireless broadband, withou plugging via USB to perform the update.
I tried but there are multiple options.
My phone won't boot up now. I couldn't even flash a stock ROM successfully. How could I perform an update?
Click to expand...
Click to collapse
It's a .zip file that you flash using stock recovery if any exist for your device. Yes, it is over the air but most of the time they can be downloaded separately then flashed manually in stock recovery instead of using the normal OTA process, but it's the sane file and same update, just done a different way.
There is also a thread here in the galaxy s2 gt i9100 forum that has steps to troubleshoot a failed Odin flash, it might help you.
Sent from my SM-S903VL using Tapatalk