Related
heyy plz help me.
i can't update my s2 i-9100 from odin.
sometimes it gets stuck at setup connection and after 10 minutes it shows Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1).
i have changed ROM's also but still the same.
sometimes it gets to boot.bin then stucks for all eternity.
i don't know what to do.
please HELP me!
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 upgraded my sm-n915t T-Mobile Note Edge to Marshmallow 6.0.1 (N915TUVU2DPE3) a few days ago and a few things don't work on the newer firmware. I would like to go back to the Kit-Kat firmware 4.4.4 (N915TUVU1ANK3), but everything I have tried doesn't work to go back to 4.4.4.
First I tried wiping everything except the external sd card through TWRP and restroing a 4.4.4 nandroid backup, but this causes a bootloop.
Then I tried downloading N915TUVU1ANK3, going into download mode and flashing through odin but this always fails, giving the error
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I read about flashing the bootloader first so I put the aboot.mbn, MPM-HLOS.bin, rpm.mbn, sbl1.mbn, sdi.mbn, and tz.mbn files from the 4.4.4 firmware in a .tar file and tried to flash it using odin 3.09. This also failed.
Did the 6.0.1 firmware upgrade or lock the bootloader so I can't return to 4.4.4? And if it did, is there a way to downgrade the bootloader?
Or am I doing something wrong?
Thank you for your help!
See here on how to do it!
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.