Related
my samsung gt-19300 is stuck on the boot screen(not the blue splash screen). cant open recovery mode. can only get into download mode.
i tried flashing the stock firmware usin odin and also tried flashing .pit file but this is what odin says
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
i have tried many methods found on this thread : "(SOLVED) PIT/Bricked/Dead problem on GT-I9300 international"
but nothing seems to work. i keep get the same error from odin.
also tried flashing cwm recovery via odin but that encountered the same problem. (cant open serial COM port)
i have all the proper drivers and samsung kies installed. i even tried uninstalling kies and then flashing the firmware but it had the same problem.
any sort of help is valued. thank you
XDA Visitor said:
my samsung gt-19300 is stuck on the boot screen(not the blue splash screen). cant open recovery mode. can only get into download mode.
i tried flashing the stock firmware usin odin and also tried flashing .pit file but this is what odin says
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
i have tried many methods found on this thread : "(SOLVED) PIT/Bricked/Dead problem on GT-I9300 international"
but nothing seems to work. i keep get the same error from odin.
also tried flashing cwm recovery via odin but that encountered the same problem. (cant open serial COM port)
i have all the proper drivers and samsung kies installed. i even tried uninstalling kies and then flashing the firmware but it had the same problem.
any sort of help is valued. thank you
Click to expand...
Click to collapse
Hello there! Welcome to XDA!
First register an XDA account (so you can ask in the proper forum)
then, please visit the following forum... (see below)
try asking here: (You will have a much better chance of getting help there)
Galaxy S3 Q&A, Help & Troubleshooting
or
Galaxy S3 Main Section
Good Luck!
I'VE TRIED EVERYTHING I CAN THINK OF..TRIED 6 DIFFERENT CORDS THINKING MAYBE IT WAS IT..DOWNLOADED 5 DIFFERENT ODIN THINKING MAYBE THEY WERE CORRUPT AND STILL THE SAME RESULT.<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/010> Added!!
CAN SOMEONE PLEASE HELP
Hello,
Welcome to XDA.
I'm not finding anything specific for your device. Try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
The experts there may be able to help.
I'll add my 2 cents and try to help you. Have you tried using different USB ports on PC? Was USB debugging turned on in the device settings before you flashed? Do you have the USB drivers installed properly? If you have Samsung Kies installed you have to make sure it is not running in background because it interferes with Odin. Check your anti virus and Firewall settings and turn them off while flashing then turn them back on after you are done. These are just a few things for you to check.
Remember to register an XDA account so you can post and reply in the forums. Good luck.
Previously my device was in a state where I couldn't get into any mode other than download mode after unsuccessfully trying to root my device (it would tell me to launch kies, even though kies could not detect my device, and my device does not support initialisation). For some extra info, after rooting my device almost every app would stop responding instantly.
After about 50 tries (of the same .pit file) I managed to flash a pit file successfully (if flash is the correct term) and now I can launch my phone again, it brings me to the initial set up page but I constantly get that google services has stopped responding, stopping me from finishing the set up process. When I do the volume up + home + power now it comes up with a red android for 'chainfire auto root' and does some random stuff then reboots my phone (but has no actual visual effect). Now I am trying to flash the stock firmware for my device but i get the following issue:
<ID:0/005> Added!!
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Surely this shouldn't be happening as I literally just flashed a .pit file in order to get my device working again? Anyway, any advice is appreciated and sorry if any information I gave was hard to follow because this is my first time rooting
XDA Visitor said:
Previously my device was in a state where I couldn't get into any mode other than download mode after unsuccessfully trying to root my device (it would tell me to launch kies, even though kies could not detect my device, and my device does not support initialisation). For some extra info, after rooting my device almost every app would stop responding instantly.
After about 50 tries (of the same .pit file) I managed to flash a pit file successfully (if flash is the correct term) and now I can launch my phone again, it brings me to the initial set up page but I constantly get that google services has stopped responding, stopping me from finishing the set up process. When I do the volume up + home + power now it comes up with a red android for 'chainfire auto root' and does some random stuff then reboots my phone (but has no actual visual effect). Now I am trying to flash the stock firmware for my device but i get the following issue:
<ID:0/005> Added!!
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Surely this shouldn't be happening as I literally just flashed a .pit file in order to get my device working again? Anyway, any advice is appreciated and sorry if any information I gave was hard to follow because this is my first time rooting
Click to expand...
Click to collapse
Hello, and welcome to XDA!
Not sure how to target this one; you should find your help in this thread:
> Samsung Galaxy S 4 i9500, i9505, i9505G, i9506 > Galaxy S 4 Q&A, Help & Troubleshooting > [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly.
Please note you will need an XDA account in order to post there.
Hope this helps, and good luck!
OfficerJimLahey said:
Hello, and welcome to XDA!
Not sure how to target this one; you should find your help in this thread:
> Samsung Galaxy S 4 i9500, i9505, i9505G, i9506 > Galaxy S 4 Q&A, Help & Troubleshooting > [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly.
Please note you will need an XDA account in order to post there.
Hope this helps, and good luck!
Click to expand...
Click to collapse
OP here, thanks for the help. I went through it and managed to restore my phone to stock.
For anyone else with the same issue as me this is how I fixed it:
Restart computer, disable antivirus, flash pit on its own, flash pit with firmware, it gets to 99% finished and then fails, and then flash pit on its own again (untick PDA).
Well, now to attempt to root it again Thanks again.
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Parteeajp said:
I rooted my phone with odin and i decided later that i wanted to unroot it. So i went into SuperSu and went to settings and tried the full unroot thing. My phone restarted and everything and i went to the root checker and it said i was unrooted. Then, i was still getting the Security notification that always pops up saying " Security Notice: Unauthorized actions have been detected ". So i went to that and i decided to try to factory reset my phone from that screen. So I cleared all the data on the phone and everything and it came back completely reset. The only problem was that I am still getting the notification. I have no idea what to do to get rid of it and i want to completely unroot my phone. I have looked all over the internet for the Galaxy S7 Verizon stock firmware. I can't find the firmware anywhere and its really bugging me having that notification there still. If there is no unroot available for the S7 right now, i was wondering if there is someway i can hide that notification for now to give me peace of mind. Thank you so much in advance.
Click to expand...
Click to collapse
Hi mate
Just flash a stock rom with odin on top of it
http://www.sammobile.com/firmwares/database/SM-G930V/
back up everything important before you do it ..just in case
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Hi
Yes you need to flash it with Odin
did you downloaded from sammobile?
if not try i from there , follow their instructions :
Extract (unzip) the firmware file
Download Odin v3.11.1
Extract Odin ZIP file
Open Odin v3.11.1
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
Usually sammobile has only one tar file ( unzip it just once) , back up you photos and files before just in case
Check this thread is not for your phone but the basics apply to all samsung phones
http://forum.xda-developers.com/galaxy-s7/how-to/official-stock-firmware-update-odin-t3369431
Parteeajp said:
Hey, i have a whole new problem now. When i was trying to unroot my phone, i accidentally installed the wrong firmware on to the phone. I turned my verizon phone into a t-mobile phone.
Im not exactly sure what flashing is, but is it where you put the BL, AP, CP, and CSC things into Odin and start it?
I might have already done that because i found the verizon firmware somewhere and when i try to do it in odin. It gives me an error and says fail.
Click to expand...
Click to collapse
Can you post a pic of the back of the phone showing the model number as SM-G930V and FCC ID. Then take a pic of the bootloader screen and show what what model number it has, if flash successfully it should be showing as SM-G930T. If proven true then it may seem that as the S7 is a Universal Hardware phone (QCOMM that is).
Please Help
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Benaiah1287 said:
I'm not sure if this is the right place to post, but I have a similar problem.
I tried flashing SM-G930U to my SM-G930V.
Odin failed, and I rebooted my phone. It will only reboot to download mode or recovery mode.
- I have tried redownloading files to check for corruption.
- Using different versions of Odin.
- Flashing to the stock files, which also fails.
- Using stock USB cable.
- Using different ports.
It doesn't seem like Odin will flash anything
Click to expand...
Click to collapse
nitropowrd said:
Benaiah1287: I am in the exact same predicament...
I got the G930U firmware from sammobile and have tried flashing it with Odin versions 3.10, 3.11, and 3.12, all with failure.
My next steps are to try the stock G930V firmware or to see if the Samsung Software Upgrade Assistant can repair.
Click to expand...
Click to collapse
You need to use the prince comsey's modified odin that bypasses SHA verification.
Saga's End
aromerblz said:
You need to use the prince comsey's modified odin that bypasses SHA verification.
Click to expand...
Click to collapse
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
nitropowrd said:
I hunted down the Comsy version of Odin 3.12 Odin3_v3.12_PrinceComsy.zip (MD5 hash 136E707B39C2E4CDC47820C68065CD5C)
but I still received a failure with the following output:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone (Download-mode) display:
DVIF!!
S REV CHECK FAIL : [aboot]Fused 4 > Binary 2
[1] eMMC write fail : aboot
I also tried it without copying the BL file only, as I have also read that this could work, but no dice.
I then tried the stock G930V firmware (for my G930V) with the following result:
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
on reboot it gave me the 'Software Update Failed' screen
I then used the Samsung Repair Utility and after half an hour it was able to restore the original OS. It did give me a new warning about it not being able to make calls until it was set up with a Verizon account, but after reboot it still just has the message "SIM card is not from Verizon Wireless," so I'm assuming it is still in its original "factory unlocked" state.
So, about 8 hours of tinkering later, I cannot recommend trying to flash the SM-G930V at all.
My sole purpose for all this was in trying to get compatibility with Republic Wireless (which claims it supports the unlocked S7 but really means the North American 930U only).
Click to expand...
Click to collapse
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
nitropowrd said:
For anyone keeping up, the source of the 930U with bootloader version 4 is here
...which I found through Fix For Those Who Tried Flashing The g930u Firmware
Too bad I just ordered a G930U instead thinking there was no current release
It appears it was also uploaded to sammobile just yesterday...but I am only assuming because the naming convention does not agree to the guide I found here, and I don't understand the 'PL#' part
Click to expand...
Click to collapse
thanks a lot. I had 2 S7s. One I was able to flash with G930UUEU2APEH, but the other one couldn't...but I could with the one you posted ( SM-G930U_1_20160921124641_vvcrzx3ej5_fac)
Help please <ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> persist.img.ext4
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> xbl.elf
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
aromerblz said:
You are trying to flash a downgraded bootloader version/firmware. Your phone has bootloader v4 and you are trying to flash a v2 firmware. Flashing a v4 or above will work.
Click to expand...
Click to collapse
I am having the same problem. How do I know the version before trying and failing until I get one that works?
Couldn't the boot loader 'version' be changed/hacked within the (down graded) boot loader so the version check would pass?
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.