Related
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
I am so lost as to what to do next, i really need guidance.
I am offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work ASAP.
So i was attempting to root my phone [GALAXY S6 - SM-G920F]
Got the file from: https://autoroot.chainfire.eu/ which should've matched my Phone.
First attempt failed, got back into my phone everything is fine. Tried the same thing again, failed this time i get this message:
An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." The logs for the times it has failed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Tried connecting with Kies and Smart switch, none can find the device just keeps buffering and for smart switch it just say it's not supported. I am able to get into downloading mode, but that's it.
Got newest Kies, odin 3 v.10.7.exe however on my first go i noticed i had odin3 v.10.6 but now i got the latest i believe. After reading around i decided to try to fix it back to normal, so i downloaded my countries [sweden] firmware this one: http://www.sammobile.com/firmwares/confirm/57869/G920FXXU3COI9_G920FVDS3COI6_VDS/
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004>
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
And now i am here, i am truely nervous that i wont be able to get it to work.
Please Xda your my only hope. All i wanted was to free up space on my phone.. That's it.. :crying:
Ps. Worth mentioning, sometimes my usb is not recongnized and it flickers on and off (connectiong) but seems
to be fine most of the times and during the odin trials.
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
I just begain with youtubing easy way to root and i just said download odin, get the right firmware plug in an click odin.
That has failed and it's bricked, however i have tried to get my countries firmware, it didint work and produced my last log that i posted.
I am downloading another one there is two for Sweden however the other one says Sweden tre which is an operator over here and not one that i use so i doubt that will work?
i will attempt to download it but it takes 3h due to the limited speed at sammmobile.
So summarize, the sweden firmware from sammobile failed ;_;
What i do is, put phone in download mode, open odin, get the AP [Sweden from sammomobile] it finds it and press start, quickly after it says failed and i am back to square one.
I was reading the link you gave me about the pit files, it appears the error could be related to me having the wrong firmware?
I am seriously offering a bitcoin tip or a paypal tip to whomever helps me get my phone to work.
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
blud7 said:
There are firmwares here for VDS.
Uninstall Kies and reboot your PC before using Odin.
Click to expand...
Click to collapse
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
If you were on 5.1.1, then get 5.1.1
You can try the file you dl before. Just uninstall Kies before using Odin.
WaDoDem said:
Should i try all of those or just take the latest?
3H download, jesus my fiber is crying.
Click to expand...
Click to collapse
You dont need to download another rom dude...the problem is your usb dont get recognized and after a while it will disconnect...it happened to me aswell...searched on youtube did an easy fix and then i flashed stock rom with odin and joined marshmallow beta...
Tldr: search on youtube a fix for usb not recognized...i dont have a link sorry you have to search it by yourself its an easy fix..
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
anthonyrv03 said:
Is it OK to flash with the latest stock roms? G920FXXU3? or should I flash only G920FXXU2? they are both 5.1.1 anyway.. If i flash with G920FXXU3, can i downgrade it to G920FXXU2? thanks for any help
Click to expand...
Click to collapse
You're fine with either.
@WaDoDem
First of all, calm down. Believe me it's harder than you think to brick S6 in a not fixable way
If Odin doesn't flash official roms or you just cant suffer a slow a** download speed from SamMobile :
1. Press and hold all of 4 buttons on your device. (Volume up + Volume Down + Home + Power) your device will reboot.
2. As soon as device reboots release volume up and hold other 3 three. (Power + Home + Volume Down). Your device should boot into downloading mode.
3. Download this :
https://dl.twrp.me/zeroflte/twrp-2.8.7.2-zeroflte.img.tar.html
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes, hold Power+Home + Volume Up. Now your device will boot into TWRP recovery.
5. Wait for drivers to be installed. Your pc should show phone's internal storage as connected device. If not, go to TWRP Mount section and enable MTP mode. (Or if it's enabled, disable and re enable it )
6. Download this rom :
http://forum.xda-developers.com/gal...rom-2013266107-arrow-rom-v1-0-0-fast-t3212318
And this kernel:
http://forum.xda-developers.com/gal...nified-development/kernel-vindicator-t3156281
Then put them on your phone.
7. Wipe system,data,cache and dalvik cache from twrp.
8. Install Arrow Rom first and then flash Vindicator Kernel.
9.Reboot, first boot can take up to 15 minutes
10.Continue celebrating new year [emoji14]
Sent from my SM-G920I using Tapatalk
sometimes if odin not working i restart my computer and put my mobile in downloadmode again and than i try again,most of the time it worked.....
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
4. Connect your phone to your pc and flash above file with Odin. As soon as flashing process finishes said:
Odin cant find the tar file.
I got odin 3V3.10.7 in options auto reboot and f. reset time are all bocked in is that right?
On files to download i am able to do, ap,cp,csc,bl neither of those help to find the recovery image that i am supposed to start?
Click to expand...
Click to collapse
Damientju said:
If you think you can't find a wat at all, Samsung will help u. Download smartswitch to your PC and you can click in top corner emergency reinstall (or something like that) just put your serial number (as found on your backside of the phone)
Click to expand...
Click to collapse
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
WaDoDem said:
I cannot use recovery since none of the numbers i have on the back of my phone matches the one i need to enter.
i tried device initialization that led to FAILED TO UPDATE DUE TO AN ERROR.
and then smart switch recommends emergency software recovery the one you were talking about but i dont know how to get my code.
I assumed you meant to input my phones IMEI however that did not prove to be correct.
Click to expand...
Click to collapse
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Damientju said:
Relax, flip your phone and on the bottom you'll see (barely visible) text. The last line it says: 'S/N:'
The code after is your serial number. So not your IMEI
The same code is found on the stickers you'd got with your phone
Click to expand...
Click to collapse
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
WaDoDem said:
When i go to Smart switch Emergency Software recovery and input my S/N R58G52AMP1J
it says:
''Unable to find the recovery code. Check the recovery code in the PC's Emergency Software Recovery menu, or contact the samsung service center.''
When i did Device initialization used my model nr and S/N: R58G52AMP1J, halfway through completing the process, the first one did 100% then the next loading didint start got the error and that re-directed me to try Emergency Software Recovery.
Click to expand...
Click to collapse
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
[email protected] said:
HI
i know your problem , irecently f*cked my phone
I was bare worried however i was able to fix itnw
Download Both file and flash the pit first
and flash the Firmware
And make sure your using ODIN Odin v3.10.7
IF its fix let me know
Click to expand...
Click to collapse
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
yes
Nicolò98 said:
To root your phone, couldn't you simply flash twrp and then unikernel, like the guides say?
However, I'd try doing the following:
First of all, download the stock firmware for your version from samfirmware, then flash it via Odin (make sure the versione you download is the same you had before, or at least a more recent one).
From your logs, the problem seems to be pit file, so try reading here http://forum.xda-developers.com/showthread.php?t=1916936
If not, completely delete odin and download it again, maybe trying with a different firmware.
If everything goes well, let it boot into setup wizard, then you will able to root it again, this time following the standard procedure with odin:
- Make sure "Auto reboot" flag is NOT checked;
- Flash the twrp odin-flashable file (can't post links here, but you'll find them in General section);
- Manually reboot into recovery (Hold power+home+volume up).
- Once you're into twrp, flash unikernel and reboot.
Your phone will be rooted
Click to expand...
Click to collapse
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
WaDoDem said:
This is the log from when i failed to start/flash the PIT. seconds later my usb was un recognised.
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Click to expand...
Click to collapse
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
sd_N said:
If Odin says no PIT, he'll need to Odin the PIT file for his device first then Odin the factory firmware.
PS...I'm just browsing threads and stopped here, hopefully to help. I'll keep reading. lol
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
Did you get the appropriate PIT file for your devices Internal storage? It does matter whether its the 32 64 or 128GB version.
Click to expand...
Click to collapse
I just downloaded and tried the pit that above user posted.
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
It's a Galaxy s6 32GB.
I know people have struggled to track this ROM down so here you all go. Separate files all Odin-flashable. The AP is zipped because it halves the size. Just unzip and good to go.
Folder contains
AP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 *.zip
BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5
CP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5
CSC_TMK_G550T1TMK1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5
Happy modding!
Link - https://www.androidfilehost.com/?w=files&flid=147594
-Zealot
Somehow I can't flash these files through Odin?
Any suggestion?
evrycard said:
Somehow I can't flash these files through Odin?
Any suggestion?
Click to expand...
Click to collapse
I have been trying all day and hope these files work. but my hopes are slim. I almost feel as if I'm doing something wrong.
---------- Post added at 08:19 AM ---------- Previous post was at 08:14 AM ----------
Zealotz said:
I know people have struggled to track this ROM down so here you all go. Separate files all Odin-flashable. The AP is zipped because it halves the size. Just unzip and good to go.
Folder contains
AP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 *.zip
BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5
CP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5
CSC_TMK_G550T1TMK1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5
Happy modding!
-Zealot
Click to expand...
Click to collapse
Do I have to flash all the files at once or one by one or just the AP file. I have been trying all day to get the Firmwear flashed but it fails every time. I have never ran into this problem before.
Hey guys,
Check out this new Mod for Samsung galaxy on5
https://forum.xda-developers.com/android/development/mod-splash-screen-samsung-galaxy-on5-t3625967
Hi there, if i flash this rom may i be able to use with any network? right now i am sin locked
wowimjohnjohn said:
I have been trying all day and hope these files work. but my hopes are slim. I almost feel as if I'm doing something wrong.
---------- Post added at 08:19 AM ---------- Previous post was at 08:14 AM ----------
Do I have to flash all the files at once or one by one or just the AP file. I have been trying all day to get the Firmwear flashed but it fails every time. I have never ran into this problem before.
Click to expand...
Click to collapse
All at once, but apparently you cannot downgrade. I spent hours trying to flash PF1 from multiple sources and always failed on flashing boot but then I tried flashing PL1 for the heck of it and it worked like a charm the first time.
Dazed No More said:
All at once, but apparently you cannot downgrade. I spent hours trying to flash PF1 from multiple sources and always failed on flashing boot but then I tried flashing PL1 for the heck of it and it worked like a charm the first time.
Click to expand...
Click to collapse
How do you flash them all at once? Do you use Odin 3.12.3? Is there a certain order that the files should be in? Thank you.
EpicSaga said:
How do you flash them all at once? Do you use Odin 3.12.3? Is there a certain order that the files should be in? Thank you.
Click to expand...
Click to collapse
All at once. Just look at the filenames and load each in the appropriate slot.
Example:-
AP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_l ow_ship.tar.md5 *.zip goes in AP slot
BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_l ow_ship.tar.md5 goes go in BL slot
CP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_l ow_ship.tar.md5 goes in CP slot
CSC_TMK_G550T1TMK1APF1_CL8180604_QB9902404_REV00_u ser_low_ship.tar.md5 goes in CSC slot
Thank you, I did it and it worked!
"fail"
im trying to do this to my on5 smg550t1 but it doesnt work i keep getting fail after sboot.bin i put all the files in the right place im on the latest version of odin i put my phone in download mode before i plug into my laptop i dont know what i could be doing wrong
wke said:
im trying to do this to my on5 smg550t1 but it doesnt work i keep getting fail after sboot.bin i put all the files in the right place im on the latest version of odin i put my phone in download mode before i plug into my laptop i dont know what i could be doing wrong
Click to expand...
Click to collapse
The only thing you are doing wrong is skipping over the posts that explain you cannot downgrade to APF1, it will not physically let you. Other than that you are doing everything right.
Fail sboot.bin
I put files in order but when start, odin show me a fail in sboot.bin. I had downloaded 4 differen roms but always is the same fail. Please help me. Thanks
---------- Post added at 10:43 PM ---------- Previous post was at 10:34 PM ----------
Dazed No More said:
The only thing you are doing wrong is skipping over the posts that explain you cannot downgrade to APF1, it will not physically let you. Other than that you are doing everything right.
Click to expand...
Click to collapse
He my friend, could you help me please? I dont understand what do you want to tell us with downgrade? I have G550T1 sn APF1, i have this fail, so what version could i use? I didnt find the posts that explain that.
Stock rom Installed But Stuck On metro pc logo
Hi bro this rom is installed but stuck on metro pc logo.....
Dazed No More said:
All at once, but apparently you cannot downgrade. I spent hours trying to flash PF1 from multiple sources and always failed on flashing boot but then I tried flashing PL1 for the heck of it and it worked like a charm the first time.
Click to expand...
Click to collapse
Wow!!! Many many many Thanks to you to brother!! This messege save my life and me ON5!! I wasted a lot of time reading and serching even downloading files! But your post was like GOLD for me. Thank you once again
On5
Dazed No More said:
All at once, but apparently you cannot downgrade. I spent hours trying to flash PF1 from multiple sources and always failed on flashing boot but then I tried flashing PL1 for the heck of it and it worked like a charm the first time.
Click to expand...
Click to collapse
Hey im having the same exact problem, tried flashing and BOOM sboot.bin fail. I understand that I, can't downgrade however, I dont specifically understand what you mean by PL1 and PF1. Thanks in advance
<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> MD5 hash value is invalid
<OSM> CP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar (1).md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar (1).md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CP_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar (1).md5 is invalid.
<OSM> End...
<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.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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)
Look at the firmware you are trying to flash. It ends with PF1....the firmware that succeeds it is PL1 and after that in not sure. Once you update from PF1 to another firmware you can never downgrade back to PF1, but you can downgrade from other more recent firmwares to PL1, why I am not sure.
can anyone help me plz i need an imei certificate for the smg550t1 / on5 metro pcs or a back up of any on5 efs
On 5
Dazed No More said:
Look at the firmware you are trying to flash. It ends with PF1....the firmware that succeeds it is PL1 and after that in not sure. Once you update from PF1 to another firmware you can never downgrade back to PF1, but you can downgrade from other more recent firmwares to PL1, why I am not sure.
Click to expand...
Click to collapse
Ah, ok seems simple enough. Would you still happen to have your PL1 files that you can upload?
JustAnotherWolf said:
Ah, ok seems simple enough. Would you still happen to have your PL1 files that you can upload?
Click to expand...
Click to collapse
No that was a long time ago....may I ask why you want to flash old firmware? It will prompt you to update to the newest anyways as soon as you boot up the phone so it seems counter productive...
My SM-G550T1 current build : MMB29K.G550T1UVU2AQC4
Dazed No More said:
Look at the firmware you are trying to flash. It ends with PF1....the firmware that succeeds it is PL1 and after that in not sure. Once you update from PF1 to another firmware you can never downgrade back to PF1, but you can downgrade from other more recent firmwares to PL1, why I am not sure.
Click to expand...
Click to collapse
As above (and FYI), my SM-G550T1 current build is MMB29K.G550T1UVU2AQC4. I'm just a novice and rooting/unlocking/flashing my first android. Do I need a copy of the stock ROM or will my Nandroid backup suffice? If so, I understand that the PL1 version is ok for my to use if need be. I guess the PL1 version is here on this site somewhere or I can Google it?
Thanks for all your attentiveness and insight....I would have been right among those flashing myself into a veritable slap-happy dither had I not benefited from the prior posts.
jb
I rooted my Samsung S6 SM-G920F via Odin.
I tried installing Xpose. But once i did, My phone cut off, And now its flashing Blue led? I can access Download mode, and Recovery, As well as the Samsung logo screen. But sometimes it goes past the Samsung logo to a black screen.
I have tried using Odin to do a recovery and it just isn't letting me?
Anyone know how i can fix this?
Flash stock rom
Ragazzza said:
Flash stock rom
Click to expand...
Click to collapse
I'v tried. Doesn't work unless i'm doing something wrong
can you write the log of odin that showed you when flash firmware ,also what is your latest bootloader you have ?
shiko2007 said:
can you write the log of odin that showed you when flash firmware ,also what is your latest bootloader you have ?
Click to expand...
Click to collapse
I can't using Odin since this problem, I get "Setup Connection..."
And i'm new to this stuff, What's a bootloader sorry!
DarkMaGiicS_ said:
I can't using Odin since this problem, I get "Setup Connection..."
And i'm new to this stuff, What's a bootloader sorry!
Click to expand...
Click to collapse
bro , if you get Setup Connection you can try unplug and after that re plug again or try another usb cable
or another usb hub of computer and do after that odin can recognize your device .
what is exactly full name firmware you try to flash it will be like that " G920FXXS5DQA3"
shiko2007 said:
bro , if you get Setup Connection you can try unplug and after that re plug again or try another usb cable
or another usb hub of computer and do after that odin can recognize your device .
what is exactly full name firmware you try to flash it will be like that " G920FXXS5DQA3"
Click to expand...
Click to collapse
That's new. I never knew them suggestions!
Yeah, My problem is, I have no clue.
My only guessing searching through fimware that it could possible be G920FVIR5DQA2 that's a guess.
ok bro if you have that firmware "G920FVIR5DQA2" this mean you have latest bootloader that you know by "5DQA2" now try flash again your firmware and after that you can to enter stock recovery but you will lose your root after flashing stock rom so you must must to re -root again to pass the samsung logo or you will stuck on logo after flash
shiko2007 said:
ok bro if you have that firmware "G920FVIR5DQA2" this mean you have latest bootloader that you know by "5DQA2" now try flash again your firmware and after that you can to enter stock recovery but you will lose your root after flashing stock rom so you must must to re -root again to pass the samsung logo or you will stuck on logo after flash
Click to expand...
Click to collapse
Flash as in using Odin AP? If so, I done what you said, Once i add the file to Odin, It says "Please wait" and then doesn't respond?
can you post log of odin , also don't move your cable when is connected to the usb and make sure your connector is plug well
can you post log of odin , also don't move your cable when is connected to the usb and make sure your connector is plug well
Click to expand...
Click to collapse
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
Doing this now
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1100)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
is it flashing well now or it is stuck on system.img
is it flashing well now or it is stuck on system.img
Click to expand...
Click to collapse
My phone doing process in Download mode. But now its done, My phone is stuck in the "Samsung" Logo with the blue light still flashing?
you can try make soft reboot by (hold vol down+ power ) it will restart and should pass samsung logo but when you have root and knox trip i think it will not allow you to pass samsung logo so you should install twrp recovery and make backup your efs folder for safety reason and make install cf-root of your device and flash it in recovery
shiko2007 said:
you can try make soft reboot by (hold vol down+ power ) it will restart and should pass samsung logo but when you have root and knox trip i think it will not allow you to pass samsung logo so you should install twrp recovery and make backup your efs folder for safety reason and make install cf-root of your device and flash it in recovery
Click to expand...
Click to collapse
Tried. Giving it the blue light. i tried twrp at first, and that didn't solve the issue :/
you should wipe cash and delvic cash , do you flashed cf-root of your device or not ?
you should wipe cash and delvic cash , do you flashed cf-root of your device or not ?
Click to expand...
Click to collapse
Thank you dude! I have messaged you!
Solved
always relax and be patient with Samsung device
uninstall xposed
go to recovery n flash uninstall xposed zip or else flash stock firmware
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.