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
Related
ok so I was getting very short on available space so i went in and started deleting things (my fault I know). I have been on 4.2.2 so all my files were in "0". I figured since they were all in that file and I had everything doubled in that file, i started deleting everything in my other file and just kept everything that was in "0". Went to flash a new Rom and all my files were now gone. I deleted all my backups in that file also (I'm kicking myself right now).
So now I'm stuck in Recovery with nothing i can do. What can I do now??
Maybe try to odin
Sent from my SCH-I535 using xda premium
OK, so I flashed the unroot files through Odin. Went through successfully, but now I'm stuck on the stock splash screen. Any ideas? some reason when i try to get into recovery, it just vibrates.
Give me the link to the odin file you flashed. I'm curious why it was an unroot flash. When you boot into recovery, You can copy a new ROM file into your sdcard and flash a new ROM via ADB.
I'm starting to freak out a little bit here. I'm in odin trying to flash it back to stock and I'm not having any luck here. Someone got some time to help?
I can now flash into recovery but my up and down buttons dont work, so the only option I have at that point is to reboot, which then send me into the splash.
sjpritch25 said:
Give me the link to the odin file you flashed. I'm curious why it was an unroot flash. When you boot into recovery, You can copy a new ROM file into your sdcard and flash a new ROM via ADB.
Click to expand...
Click to collapse
This is what I'm trying to do right now. passed the first step, but the second isn't getting a pass.
this is what I'm getting on the second flash in odin:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I535VRALF2_618049_REV09_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
I dont geta pass above though. its just empty.
Does that just mean that I'm not giving it enough time to process?
SOB!!!! Anyone out there that can help me here??
Holy hell. It booted up. That could have been the most stressful 2 hours of my life.
Hi guys,
I have an S7 - SM-G930F. I tried rooting it, which caused this issue at first. I then tried various stock roms from samsung-firmware to sammobile (Vodafone the Netherlands)... in the end I found one from here, I tried it, only noticing I had the re-partition box checked.
Now my phone is stuck at this blue screen that says: "An error has occured..." - and I can't get into download mode anymore.
I'm scared I screwed this up. Is there still anything I can do?
Even tried with Smart switch and Kies, both give an error after filling in my model name... - "Unsupported device"
Please help..
Magetrip said:
Hi guys,
I have an S7 - SM-G930F. I tried rooting it, which caused this issue at first. I then tried various stock roms from samsung-firmware to sammobile (Vodafone the Netherlands)... in the end I found one from here, I tried it, only noticing I had the re-partition box checked.
Now my phone is stuck at this blue screen that says: "An error has occured..." - and I can't get into download mode anymore.
I'm scared I screwed this up. Is there still anything I can do?
Even tried with Smart switch and Kies, both give an error after filling in my model name... - "Unsupported device"
Please help..
Click to expand...
Click to collapse
Hi mate
First calm down , you will fix it
What firmware you had before rooting, Marsmellow , Nougat?
Why you had re partition on? when you had re partition you where using CSC file also?
how did you root?
In this cases the download issue may be caused by the bootloop itself , it becomes a timing issue....try several times and you will get into it eventually.
If you do re flash stock rom again
MAX 404 said:
Hi mate
First calm down , you will fix it
What firmware you had before rooting, Marsmellow , Nougat?
Why you had re partition on? when you had re partition you where using CSC file also?
how did you root?
In this cases the download issue may be caused by the bootloop itself , it becomes a timing issue....try several times and you will get into it eventually.
If you do re flash stock rom again
Click to expand...
Click to collapse
Thank you for your kindness.
I'm not sure to be honest. I updated it to the max, then I tried rooting it.
I think it got turned on, because this guide told me to add an PIT file.
However, I have managed to get back into download mode. I tried rooting by flashing.
What is the best thing u advice me to do from here?
Magetrip said:
Thank you for your kindness.
I'm not sure to be honest. I updated it to the max, then I tried rooting it.
I think it got turned on, because this guide told me to add an PIT file.
However, I have managed to get back into download mode. I tried rooting by flashing.
What is the best thing u advice me to do from here?
Click to expand...
Click to collapse
Hi
good you can get into download that is very good
When you say flashing root you mean by Odin or by recovery?
I would flash a stock rom again using CSC file and re- partition again...just to make sure the partition are the correct ones
Check here
Download the correct firmware and follow the instruction.......
MAX 404 said:
Hi
good you can get into download that is very good
When you say flashing root you mean by Odin or by recovery?
I would flash a stock rom again using CSC file and re- partition again...just to make sure the partition are the correct ones
Check here
Download the correct firmware and follow the instruction.......
Click to expand...
Click to collapse
Hi,
I'm happy I still have that possibility.
I rooted by Odin.
I have downloaded an firmware that belongs to the S7... - I will follow the guide.
When you say partition, you mean like this: http://prntscr.com/emplwv ?
Magetrip said:
Hi,
I'm happy I still have that possibility.
I rooted by Odin.
I have downloaded an firmware that belongs to the S7... - I will follow the guide.
When you say partition, you mean like this: http://prntscr.com/emplwv ?
Click to expand...
Click to collapse
Hi
To root in Nougat you have to flash it in custom recovery...by odin is not working
Regarding the picture yes like that BUT use CSC not home_csc , CSC contains the right PIT file
MAX 404 said:
Hi
To root in Nougat you have to flash it in custom recovery...by odin is not working
Regarding the picture yes like that BUT use CSC not home_csc , CSC contains the right PIT file
Click to expand...
Click to collapse
Yes, I downloaded the firmware Nougat.
Can u provide me a link that teaches me to flash it in custom recovery? Because all day I tried flashing Nougat with Odin. Maybe that's the problem.
Magetrip said:
Yes, I downloaded the firmware Nougat.
Can u provide me a link that teaches me to flash it in custom recovery? Because all day I tried flashing Nougat with Odin. Maybe that's the problem.
Click to expand...
Click to collapse
Hi
Here is the link for recovery and root all in one
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
But i would still recomend to try flashing a stock rom to make sure that everything is correct...then recovery , root or custom rom.......
Hi friend,
I have succesfully got TWRP on it. When I try the stockrom flash through odin like the picture, it fails me every time on 1/5 and says "FAIL!"
Is there anything I can do to solve this?
http://prntscr.com/en1zqo
everytime.
<ID:0/007> 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> cm.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Magetrip said:
http://prntscr.com/en1zqo
everytime.
Click to expand...
Click to collapse
Why have you ticked re-partition?
Leave ODIN at default settings and only use BL, AP, CP and CSC
If that still fails, try missing out BL and just use the other 3
*Detection* said:
Why have you ticked re-partition?
Leave ODIN at default settings and only use BL, AP, CP and CSC
If that still fails, try missing out BL and just use the other 3
Click to expand...
Click to collapse
Now I thought'd be a good idea, to delete the bad files of fail every time.
When I do the AP-CP and CSC it still gives me the "FAIL!" with everything checked on.
I have no image on the phone, so I can't even boot it up anymore.
I did check however "OEM unlocked"... when I do the TWRP, I can boot into recovery.
But no stock roms work. I tried it from samsung-mobile and one from sammobile.
Now I am downloading another stock rom to try...
Also I don't use pit file when doing this. Should I?
What can I do?
http://prntscr.com/en4jag
I have tried 3 different stock roms, and all fail on 1/5th. Even without the BL inserted in. Also tried only doing AP...
Tried doing AP/CP/CSC in Odin v3.10
Then it goes to 2/5 and fails.
http://prntscr.com/en51kg
Magetrip said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
Click to expand...
Click to collapse
*Detection* said:
Why have you ticked re-partition?
Leave ODIN at default settings and only use BL, AP, CP and CSC
If that still fails, try missing out BL and just use the other 3
Click to expand...
Click to collapse
Hi
Re partition is an option under some specific cases ( read here)
Try in a different PC / USB cable
Try a different Odin version
Go into recovery wipe dalvik/ cache and do a factory reset, flash again
Magetrip said:
Tried doing AP/CP/CSC in Odin v3.10
Then it goes to 2/5 and fails.
http://prntscr.com/en51kg
Click to expand...
Click to collapse
You need ODIN 3.12.3 minimum for this to work
Download
Code:
https://mega.nz/#!uBwC3KqR!17OPP5A1g9d7-GxAqCbjXFpmYfO7CgAHNcaZxqEkOao
Leave all settings as default, add all 4 sections of the ROM using CSC and try again
---------- Post added at 22:31 ---------- Previous post was at 22:30 ----------
MAX 404 said:
Hi
Re partition is an option under some specific cases ( read here)
Click to expand...
Click to collapse
Thanks for the info, was not aware of that
God bless you all.
This has resolved my issue:
- Tried it on my desktop (before on my laptop)
- Deleted Kies/Smart Switch
- Took another cable
- Tried the Odin 3.12.3
- Deleted dalvik/cache and factory reset
Works! Love you all. Tried over 8 hours. The solution is not always complicated...
Magetrip said:
God bless you all.
This has resolved my issue:
- Tried it on my desktop (before on my laptop)
- Deleted Kies/Smart Switch
- Took another cable
- Tried the Odin 3.12.3
- Deleted dalvik/cache and factory reset
Works! Love you all. Tried over 8 hours. The solution is not always complicated...
Click to expand...
Click to collapse
Great
Now you will love your S7 like never before lol
I Tried multiple times to flash with odin but never with success, allays with the same error:
<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/010> Odin engine v(ID:3.1203)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> SingleDownload.
<ID:0/010> sboot.bin
<ID:0/010> FAIL!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help would be appreciated.
Continue to try with diferent versions of sw. Also do try to instal twrp thru odin and see if that makes it boot
Have you tried to select nand erase all or bootloader update?
Until you have a successful flash do not try to select nand erase all or efs clear!
You could try bootloader update
lenovot said:
Continue to try with diferent versions of sw. Also do try to instal twrp thru odin and see if that makes it boot
Have you tried to select nand erase all or bootloader update?
Until you have a successful flash do not try to select nand erase all or efs clear!
You could try bootloader update
Click to expand...
Click to collapse
Thanks for helping me.
I tried flashing it with twrp it gave me a PASS, but after that it booted to the samsung logo kept showing that. So stuck in boot logo.
I tried to boot ones with the Samsung animation boot screen. but after that it showed the Samsung boot loop again.
I have not use nand erase or bootloader update. But I have use The BL option when selecting a firmware, that may screwed it up.
[UPDATE] It works again!, well kinda .... I have no touchscreen input anymore haha well atleast one step closer
Try to find your region using the serial number on the back of the phone or your imei. After that download and flash the sw from that region if it boots but you still dont have touch imput, flash twrp again and see if that has a touch imput if does do a full backup, boot, system efs etc and save it as is by otg on a stick or on your pc.
if you get touch in twrp you could also try to flash a custom rom and see if that helps. Something like samstock.
lenovot said:
Try to find your region using the serial number on the back of the phone or your imei. After that download and flash the sw from that region if it boots but you still dont have touch imput, flash twrp again and see if that has a touch imput if does do a full backup, boot, system efs etc and save it as is by otg on a stick or on your pc.
if you get touch in twrp you could also try to flash a custom rom and see if that helps. Something like samstock.
Click to expand...
Click to collapse
I have tried the factory reset option and now it just shows the boologo again, (invinite loop and the rtwp does not seem to fix it this time)
I have downloaded the https://updato.com/firmware-archive-select-model?record=6BE751A3C8BA11E69215FA163EE8F90B version
but my phone region was united emirates, and that does not seem to add up with the firmware...
I keep getting the same odin error and I am about to break the thing in 2
What should I do?
Have you tried smartswitch? At first if it doesn't connect try to install smartswitch on the phone. Install it on the phone and after that on your pc and see if it gives you an update
lenovot said:
Have you tried smartswitch? At first if it doesn't connect try to install smartswitch on the phone. Install it on the phone and after that on your pc and see if it gives you an update
Click to expand...
Click to collapse
Yeah tried that did not work the device is not showing in the list of recovery devices, can't install anything on the phone anymore, because it stuck in bootloop.
Use samfirmware to find your fw, nougat eventually and flash it. If you have made a backup of your efs do try to make a repit. Be careful to use the pit file for your sw. You can try to repit it even with a diferent fw as long as they all match. Get the fw from samfirmware and find the pit for it flash it with nand erase all bootloader update after that if it boots and it.s ok then ok if not flash twrp, restore efs and flash again the fw normal without pit bl update and nand erase. This is what i did with mine when i was trying to brand it to a network.
Have a Note Pro 12.2. Was wanting to install Lineage 16.0 OS on it.
Went into recovery and did a wipe/install.
Was able to root it using Odin.
Downloaded the Lineage files onto an SD card
Downloaded TWRP on the tablet with Google Play
Flashed the boot.img file to recovery
When I try to reboot into recovery, I get a Set Warranty Bit : Recovery on the startup screen and it just hangs there
I think I did originally backup the recovery file, but I cant seem to find it now. Its not on the SD card for the device where I thought it was.
Weirdly,
Booting regularly gets me the same screen
Booting into recovery gets me this screen (obviously)
Booting into bootloader gets me this screen too
I can't seem to power it down either, all key options just seem to loop back to the
bad recovery message.
It no longer 'connects' via USB to my computer either.
Can anyone please help me try to get this back? I can provide any additional info as well.
Im currently trying to find the original firmware for this device, but I haven't been very successful yet.
I would be very grateful for any information or links or help you could offer.
Thank you.
I opened the back just now to pull the battery.
When I replace it, and turn it back on, it goes to the same screen.
You're the second this year to post this problem, and nobody seems to have a fix.
Was thinking of putting a custom rom on mine, but this has put me off that idea.
Revert back to stock
To get your tablet back to a running state and revert everything back to stock, you'll want to use one of these two stock firmwares from the Sammobile site. I picked these two out based on the fact that you said you had a UK device. The firmware in the first link is from 2017, while the second link contains a firmware from 2016.
Personally, I have had no luck getting any of the recent firmware from any of the regions to install on my SM-P905 through ODIN; I get errors about partition sizes. However, installing older firmware from other regions works just fine. Try either of the two links and if the latest one for UK doesn't work, try the other one.
From 2017: https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P905/BTU/download/P905XXSABQC1/127655/
From 2016: https://www.sammobile.com/firmwares/galaxy-note-pro/SM-P905/BTU/download/P905XXUABPG4/89307/
A successful installation of the firmware will reset your bootloader, recovery, and rom back to stock Lollipop. You will be able to use your tablet at that point, although give it a good long time to boot the very first time. This will give you a clean slate to try and install Lineage 16, or any other rom of your choice.
Thanks for the info, Shardsx, I'm downloading them now.
OK, an update.
I let the device power down completely on the Set Warranty Bit : Recovery screen until it died.
I then plugged the tablet into the usb on my desktop, and I was able to press power and the vol down (Recovery screen? It says Odin mode) again, but I havent been able to do much with it through Odin or Kies programs for reflashing the firmware.
If I press power and vol up, I get the same Set Warranty Bit : Recovery screen.
ricosuave95 said:
OK, an update.
I let the device power down completely on the Set Warranty Bit : Recovery screen until it died.
I then plugged the tablet into the usb on my desktop, and I was able to press power and the vol down (Recovery screen? It says Odin mode) again, but I havent been able to do much with it through Odin or Kies programs for reflashing the firmware.
If I press power and vol up, I get the same Set Warranty Bit : Recovery screen.
Click to expand...
Click to collapse
Please elaborate a little on why you haven't been able to do much with it through Odin. In your first step, you said you let the device power down completely until it died, which makes it sound like you drained the battery. You'll want plenty of battery power for this process, so charge your device up. It sounds like you do know how to get into Download/Odin mode, so I won't ask about that. Instead, tell us a little bit more about what you're doing in Odin. Are you loading the firmware using the AP button? Which of the two files are you trying to load? Are you unzipping the firmware file first so that you're flashing the *.tar.md5 file? Are you waiting the appropriate amount of time for the firmware to unpack within Odin before attempting to flash anything? (This step takes a long time too) Are you able to successfully start the firmware upload? What results are you getting? Are you leaving the Odin options as stock when you do this?
I havent had much time to work on it.
Once I do, I'll post and update to it, and your questions.
Thanks
OK, so initially, I let the device die down so that there was nothing left on the battery - I was unable to shut it off. When it would reboot, it always gave me that same Set Warranty Bit : Recovery screen.
I charged it completely, and was able to boot into the download mode, but initially, I couldnt get it to register when I plugged into the USB.
Here is what the recovery/download mode said...
Product Name: Samsing SM-P905
Current Binary: Samsung Official
System Status: Custom
Knox Warranty: Void 0x1 (0)
Qualcomm Secureboot: Enable (CSB)
RP Swerv: S1, T1, R1, A1, P1
Secure Download: Enable
UDC Start
After a few reboots, it did though, and Odin was able to see it.
When I ran Odin, with both firmwares, they both gave me the Invalid EXT4 Image error... I then read online that I probably needed to reflash the PIT file for it.
I tried but was unsuccessful in reading mine off the device using a couple of tools., but I did find one in this thread that I tried... https://forum.xda-developers.com/showthread.php?t=2758925
It didnt seem to work.
I rebooted the device a couple of times, and with one of the firmwares above, it would fail almost immediately with the same EXT4 error, saying something about the volume size being different (40960 vs 204800 ish), the second one, however, seemed to carry on further, almost 3/4 the way through the process before it failed with the same (volume size too big). I think that the PIT I used was incorrect, which is why I was asking for my specific one in another thread. I cant seem to find hardly any PITs for this device.
I also tried using Kies, as after one reboot, it said on screen to use it to recover firmware, but while it did connect to PC via USB, Kies did not detect it, either before the PIT and after.
Heres the Odin error mesage for the second firmware that lasted a while...
<ID:0/003> 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/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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the first firmware that failed immediately:
<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/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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete (Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks to the help from nowheretohide and shardsx, I was able to get my tablet restored to factory... Used Odin and the file provided here:
https://forum.xda-developers.com/showthread.php?t=2758925&page=2
Now, because I obviously messed it up so bad the first time, and am now gun shy, can anyone help me install Lineage 16.0 with a step by step?
ricosuave95 said:
Thanks to the help from nowheretohide and shardsx, I was able to get my tablet restored to factory...
Now, because I obviously messed it up so bad the first time, and am now gun shy, can anyone help me install Lineage 16.0 with a step by step?
Click to expand...
Click to collapse
Don't be gun-shy. You now have almost all the tools to recover from similar issues in the future.
I'm using Odin 3.11 for these instructions. Assumptions I'm making is that you have already downloaded a working version of TWRP for this tablet (remember, the absolute latest versions on the official TWRP site are not compatible with our tablets. Go through the TWRP site and look at the compatibility page for our tablet, or use Valera's custom TWRP).
Step 1: Charge up that tablet.
Step 2: Get into Download mode.
Step 3: Open up Odin. Leave options as default. The one you should really double-check is to make sure that "Re-Partition" is not checked or enabled.
Step 4: Click the AP button and load the TWRP recovery image, and then upload it to your tablet through Odin. Your tablet will reboot automatically reboot. You might as well enter Recovery at this point.
Step 5: I usually store the the ROM images on an external SD card. Inside Recovery, I usually like to do an advanced wipe and wipe out /system /data /cache to . Then, I'll flash the ROM image from the external SD card. After the flash, just reboot the tablet and wait until Android starts up.
I apologize for not providing screenshots. I'm doing this off the top of my head but generally that's what I do to load new ROMs.
The above steps will get you a barebones Android. You'll still have to flash Google's stuff on top if you want to go that way, but basically repeat Step 5 but replace it with the recommended Google packages and that should get you set up pretty good.
I think it was the fact that I used a different version of TWRP. Oops.
Will try again using the correct tools now.
Also, I think Ill go with CRdroid - I'd just like to have a speedier tablet with no Samsung bloatware and maybe a little better battery life, since I replaced the batteries not long ago.
Thank you all!
Got it running with CRdroid, was a little laggier than I liked and some apps were crashing...
Tried lineage 16.0 and found it much better.
I need some troubleshoot tinkering
I have received a Note 10.1 (GT-N8020) from a friend who would appreciate if I could salvage pictures and documents that was on this tablet, and let us not debate his backup options.
Problem with the tablet is it wont boot properly.
It just hangs on the Samsung animation.
As first troubleshoot step my thought was to boot into Recovery and wipe cache and dalvik, just to get it booting. But I simply cannot boot into Recovery. I can only get to ODIN mode.
After several attempts giving up on Recovery, my plan was to flash a new Recovery onto tablet by using ODIN mode, however all attempts both with several different version of ODIN and different version of TWRP fails to be flashed.
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.1401)..
<ID:0/009> File analysis..
<ID:0/009> Total Binary size: 6 M
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> NAND Write Start!!
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So here I am, feeling stuck.
Either I am thinking there is a defect with the NAND chip, why the tablet must have failed in first place, however I can also find some articles claiming some of Samsung's tablets does not have a Recovery mode/partition, is this true for this model?
I have not reflashed entire tablet, since I need access to whatever data there must be on the tablet.
I also found description on sammobile explaining how to re-install ROM while preserving apps and data, but they keep mentioning ROMs based on 5 files (AP, BL, CP, CSC, HOME_CSC), while I can only find ROMs based on single files (AP)
Link to article (see step 2)
https://www.sammobile.com/samsung/galaxy-note-101/firmware/GT-N8020/CNX/download/N8020XXUDOH1/55623/
Anyone know where I can download such ROM based on 5 files (Samsung official ROM)
Suggestions for any other methods I can try to get the data out of tablet?
Try Philz Recovery instead of TWRP .
Not sure if ADB will work for you .
JJEgan said:
Try Philz Recovery instead of TWRP .
Not sure if ADB will work for you .
Click to expand...
Click to collapse
Philz Recovery tried to flash and fails too
Recover data try ADB .
JJEgan said:
Recover data try ADB .
Click to expand...
Click to collapse
IIRC would that not require USB debugging enabled (which I cannot since it will not boot) and the Android in a running state?
Thanks to the SamFirm tool I managed to find some ROMs configured with CSC_HOME. On first shot it failed to flash these ROMs too. But I will try some more tinkering
I guess your eMMC is locked.
So the only possible solution would be to desolder it and read the data directly out of it.
Whereas the OP gives a link to an "article" at sammobile, that page has since changed and no longer gives any useful instruction for re-flashing while preserving apps and data. However, I believe that the original "step 2" of that page referred to was : "2. Add each file to its respective field in Odin v3.14.4. Use CSC_*** if you want to do a clean flash or HOME_CSC_*** if you want to keep your apps and data."
Probably a bit late for the original poster from 2020 .
Could try flashing with No CSC .
JJEgan said:
Probably a bit late for the original poster from 2020 .
Could try flashing with No CSC .
Click to expand...
Click to collapse
Sure, there's a good chance that the original tablet has since become e-waste, however, there is also some chance that it's sitting in his friend's drawer in the slim hope of a resolution.
However, my clarification about "step 2" is for the benefit of other readers of this thread, since the OP will already know this information.
My own GT-N8020 tablet has the exact same problem. I was able to overcome the flashing difficulty by using the Prince Comsy patched version of Odin 3.12.3 (which disregards spurious USB communications errors that tend to occur).
However, re-flashing without the CSC portion of the firmware doesn't resolve the problem. I can't include the CSC portion as this will clear the data that I need to recover, and I haven't yet been able to find a HOME_CSC alternative.
Joe.