Related
HELLO!
I recently had issues with my Galaxy S6 after "unrooting it".
In short way as possible:
1. I have Rooted my S6
2. I have decided to unroot it
3. I have downloaded stock rom from Sammobile (correct one yes)
4. The flash failed leaving me with some errors.
5. I have flashed twrp recovery and it fixed the problem.
6. Today I have turned my phone off and it got stock in boot loop
7. I tried clearing cache. Didn't help.
8. I cleared internal storage (Factory reset) and my phone didn't turn on at all... I went into twrp again to find out that there is literally nothing on my phone apart from the TWRP recovery...
9. I have access to Download Mode/Recovery mode .
I have tried flashing stock firmware on the phone and it didn't work becuase Odin is giving me errors all the time. Please don't bother providing me solutions with Odin as I have tried literally everything, different usb ports, versions of Odin etc etc. didn't work.
Is there any way to fix this? Maybe Custom Rom CM13 ?
CM13 is not stable. Try to copy a custom rom that is stable and specific to your device via adb.
Else try Odin.
Maybe try from somebody else's pc with the latest version of ODIN. If required download the stock rom file from sammobile again; mayb some errors have crept in while downloading.
Trust me; ODIN is the best option.
Check whether your computer is up to date and whether usb drivers are properly installed. Try with ODIN with newly downloaded rom file
Don't use usb 3.0 ports on Your computer. They either won't work or mess up the data that odin sends to Your phone. And flash stock rom again.
anaveragehuman said:
What is the error you're getting IN ODIN?
Click to expand...
Click to collapse
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Just flash a pit file..nothing else. Power off.. Go to recovery..wipe data.. factory reset and you are OK
if you want to do a clean install you have 2 solutions first with smart switch second you download wrong firmware and with wrong i mean no for wrong model of s6 but wrong number!!!your csc must have 3 not 2!!!for example i had this firmware on my phone G920FEUR3COI6 and i tried to flash this G920FEUR2COH2 and i got a bootloop because of this section EUR2!!!for sure download this http://www.sammobile.com/firmwares/download/57680/G920FXXU3COI9_G920FBTU3COJ1_BTU/ and you are good to go!!!
Its more easy a fast just to flash pit and to factory reset or otherwise bootloop
Download and open Smart Switch on your PC
Then, connect phone at download mode to your PC
And, rescue the firmware via Smart Switch.
If you decide to flash a Pit file, you should be able to find the right one here.
http://www.theandroidsoul.com/download-samsung-galaxy-s6-pit-file-g920fiklstw8-84262/
fiesatros9979 said:
if you want to do a clean install you have 2 solutions first with smart switch second you download wrong firmware and with wrong i mean no for wrong model of s6 but wrong number!!!your csc must have 3 not 2!!!for example i had this firmware on my phone G920FEUR3COI6 and i tried to flash this G920FEUR2COH2 and i got a bootloop because of this section EUR2!!!for sure download this (URL) and you are good to go!!!
Click to expand...
Click to collapse
Sorry, for not replying. I seemed to get it working after flashing my firmware, but I still got the error, so I went the same way as before and flashed twrp and it seemed to work, however when I turn my phone off and try to turn it back on then the bootloop happens and I have to go through the same process all the time which is kinda time consuming. I am just downloading this firmware that you have linked me and try to flash it hopefully with no errors :angel: and it will bring my knox back
forumber2 said:
Download and open Smart Switch on your PC
Then, connect phone at download mode to your PC
And, rescue the firmware via Smart Switch.
Click to expand...
Click to collapse
SmartSwitch doesn't recognise my device :l
I remember messing up my Galaxy S5 after tweeking things in custom ROM and I have fixed it though KIES but this doesn't seem to work anymore.
lummujaj said:
Just flash a pit file..nothing else. Power off.. Go to recovery..wipe data.. factory reset and you are OK
Click to expand...
Click to collapse
I've never used/know what pit file does or is? Any guides
fiesatros9979 said:
if you want to do a clean install you have 2 solutions first with smart switch second you download wrong firmware and with wrong i mean no for wrong model of s6 but wrong number!!!your csc must have 3 not 2!!!for example i had this firmware on my phone G920FEUR3COI6 and i tried to flash this G920FEUR2COH2 and i got a bootloop because of this section EUR2!!!for sure download this http://www.sammobile.com/firmwares/download/57680/G920FXXU3COI9_G920FBTU3COJ1_BTU/ and you are good to go!!!
Click to expand...
Click to collapse
Update: Thanks for the link! I'm so mad... the firmware I was downloading didn't work and I kept on telling people it's the right one, but I downloaded yours and it worked with no issues! Odin flashed with no issues and I'm back to stock. ++++ :good:
MrDarkness96 said:
Update: Thanks for the link! I'm so mad... the firmware I was downloading didn't work and I kept on telling people it's the right one, but I downloaded yours and it worked with no issues! Odin flashed with no issues and I'm back to stock. ++++ :good:
Click to expand...
Click to collapse
I m happy for helping you.....☺
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
MrDarkness96 said:
Update: Thanks for the link! I'm so mad... the firmware I was downloading didn't work and I kept on telling people it's the right one, but I downloaded yours and it worked with no issues! Odin flashed with no issues and I'm back to stock. ++++ :good:
Click to expand...
Click to collapse
You re welcome......
Hi,
I am trying to install TWRP onto my S6, however everytime in Odin it fails.
I've done a fresh wipe of my phone, got Odin v3.10.7 installed on my pc with twrp-2.8.7.2-zeroflte.img.tar and twrp-3.0.2-0-zeroflte.img.tar (tried both incase the newest one didnt work.)
I put my phone into Download Mode and the plugged it into my laptop, and then chose the correct file under the AP section of Odin.
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I notice in the top left it says in green letters: Custom Binary(RECOVERY) Blocked By R/L
Tried restarting my phone etc but nothing seems to change it.
Can someone help?
Cheers
Okay so I managed to get Odin to work for the TWRP file - however it hasn't changed anything in my recovery menu...
I read on https://twrp.me/devices/samsunggalaxys6.html that I need to disable Fastboot as it wipes over the TWRP when booting... so after googling how to do that, people say to go into power settings and turn it off. But there are no settings for it.
How can I disable fastboot so that the TWRP will stay installed?
craigsup said:
Okay so I managed to get Odin to work for the TWRP file - however it hasn't changed anything in my recovery menu...
I read on https://twrp.me/devices/samsunggalaxys6.html that I need to disable Fastboot as it wipes over the TWRP when booting... so after googling how to do that, people say to go into power settings and turn it off. But there are no settings for it.
How can I disable fastboot so that the TWRP will stay installed?
Click to expand...
Click to collapse
No official TWRP is compatible with the MM bootloader on the S6 yet. I imagine this is your issue?
2ZE said:
No official TWRP is compatible with the MM bootloader on the S6 yet. I imagine this is your issue?
Click to expand...
Click to collapse
So how can anyone root their S6 with 6.0.1?
craigsup said:
So how can anyone root their S6 with 6.0.1?
Click to expand...
Click to collapse
I used CF-AutoRoot to get the initial root, then flashed a custom 3.0.2.2 TWRP (available from the official TWRP thread... Look for the idlekernel link). Works great
Bigbiff seems to have an official MM version in the pipeline, so just flash that when it's released in the next month or two
Oh, and you can just flash a custom kernel that comes with a root
2ZE said:
I used CF-AutoRoot to get the initial root, then flashed a custom 3.0.2.2 TWRP (available from the official TWRP thread... Look for the idlekernel link). Works great
Bigbiff seems to have an official MM version in the pipeline, so just flash that when it's released in the next month or two
Oh, and you can just flash a custom kernel that comes with a root
Click to expand...
Click to collapse
So if I use CF-AutoRoot that will modify the recovery menu so that I can use any ROM I want?
I want to use http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423
So I'd use CF-AutoRoot and then in the new recovery menu select the zip files from the above link?
craigsup said:
So if I use CF-AutoRoot that will modify the recovery menu so that I can use any ROM I want?
I want to use http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423
So I'd use CF-AutoRoot and then in the new recovery menu select the zip files from the above link?
Click to expand...
Click to collapse
CF-AutoRoot only installs a temp recovery to flash SuperSU. It then reinstates the stock recovery, so no.
Root it with CF-AutoRoot, flash the custom TWRP that currently works with MM, make a back up, then go mad
Device: SM-G920F
ROM: NanoROM-5.6.0~beta2-20160916-920.5FD-PDP
Android-Version: 6.0.1
Based On TouchWiz
I dont know which information i should give to my device
Problem:
Hello im not so new i read a lot here and at this problem its the same.
I have the same problem as this guy but there is since a few months no updates and not so detailed device info
Last evening my phone crashed i used Chromecast-app/webcasterapp and chrome at this moment.
Ive got 2 new apps Chromecast-App and FireTV app.
So sinced it crashed i thought it just reboots but it was stuck since half an hour.
iv tried a Hard reboot and tried to reboot into Recovery but it just stucks on the "Samsung Galaxy S6 Powerd by Android" screen
i just can boot into Download / odin mode
What ive tried:
Flash over Odin3_v3.12.3:
TWRP 3.0.2.0 (No Errors)
G920FXXU2BOFJ_G920FOXA2BOFJ_XEF(4File)_ChoiMobile.VN (Not Matching Version Error)
BL-6.0.1-G920FXXU4DPHB (No Errors)
2016-09-19-6.0.1-PHN-G920FXXU4DPIL-4teilig (*4 Files; No errors )
Flashing Over Odin_v3.10.0 just stucks on Writing Nand
Flashing Orginal Over Smart Switch ends With no Errors
I don´t know which version is the right ;( i just know its an G920FXX but is there so much diffrent ?
If you need any more information please tell me
Update
I just noticed that i dont have a charging screen at all
Nobody got a clue or an Idea what i could try else ?
I would say this:
1. Reflash TWRP with ODIN.
2. Download stock rom from sammobile for your particular device.
3. Enter recovery, wipe and install the stock rom.
Had same issue as you, trial and error got me the solution
Do not try to flash rom in ODIN
I tried to flash twrp-3.0.2-1-zeroflte.img.tar so many times odin -> pass
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
but then when i try to enter twrp there is no just this stupid screen
i hate it when developers give no usable error messages :crying:
tr1g4d0n said:
I tried to flash twrp-3.0.2-1-zeroflte.img.tar so many times odin -> pass
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
but then when i try to enter twrp there is no just this stupid screen
i hate it when developers give no usable error messages :crying:
Click to expand...
Click to collapse
Are you holding down the button combination long enough to get into recovery?
Usually if a phone is stuck at logo, in 90% of cases DRK is messed up, but it will only show in stock recovery.
If knox is triped, try flashing custom kernel e.g. CF autoroot, which will bypass the problem, or it can be fixed with a box.
If it is not, I don`t know how to fix it.
You can try emergency initialization via Smart Switch with sn of the phone and see what happens on stock fw. (you can check my threads, I made a guide for SS initialization)
MossadPhil said:
Are you holding down the button combination long enough to get into recovery?
Click to expand...
Click to collapse
I holde it up to 2 Minutes so i think yes i do
and i often use recovery so i think i push it right
brenner650 said:
Usually if a phone is stuck at logo, in 90% of cases DRK is messed up, but it will only show in stock recovery.
If knox is triped, try flashing custom kernel e.g. CF autoroot, which will bypass the problem, or it can be fixed with a box.
If it is not, I don`t know how to fix it.
You can try emergency initialization via Smart Switch with sn of the phone and see what happens on stock fw. (you can check my threads, I made a guide for SS initialization)
Click to expand...
Click to collapse
as you can see at my first post i tried the initialization via smart switch and stock rom flashing
but i will try the custom kernel and CF autoroot when i find it on xda
could you explain me what DRK is and what you mean with "or it can be fixed with a box." what is a box?
Thanks anyway :good:
tr1g4d0n said:
as you can see at my first post i tried the initialization via smart switch and stock rom flashing
but i will try the custom kernel and CF autoroot when i find it on xda
Click to expand...
Click to collapse
CF auto root: https://autoroot.chainfire.eu/
tr1g4d0n said:
could you explain me what DRK is and what you mean with "or it can be fixed with a box." what is a box?
Thanks anyway :good:
Click to expand...
Click to collapse
I think some people here with more technical expertise than me, can answer that question more precisely, or you can try google it, and box is a professional repair tool, like Octopus/Octoplus, Z3X, etc. mostly used by 3rd party repair shops.
so the last days i tried to flash many different versions of samsung stock: rom, kernel, bootloader; and i have tried to flash auto root and twrp custom rom
nothing helped =(
now i try octopus/plus samsung
Download kies - samsung firmware updater ( google for it ) and install the latest firmware, this in most of the cases rezolves any software related problem.
After that you can root again and install witch custom rom you want.
The last day´s i tried almost everything. Nothing helped =(
Now my last hope is the warrenty. If the bill is smaller as 100€ i will pay it otherwise i will buy the Nexus 5x
Thank you very much for each advice !
MossadPhil said:
I would say this:
1. Reflash TWRP with ODIN.
2. Download stock rom from sammobile for your particular device.
3. Enter recovery, wipe and install the stock rom.
Had same issue as you, trial and error got me the solution
Do not try to flash rom in ODIN
Click to expand...
Click to collapse
OK, so how do I flash the firmware from sammobile since it's a tar/md5 and wont flash in twrp?
ivyhole said:
OK, so how do I flash the firmware from sammobile since it's a tar/md5 and wont flash in twrp?
Click to expand...
Click to collapse
You only flash TWRP with ODIN.
Last line of my message said do not try to flash rom with ODIN. ????
Hello there guys,
I write in this new thread because i have a huge problem with my samsung galaxy s7 sm-g930f. Actually I had rooted it with twrp and magisk (and it worked) but when i restarted the twrp recovery i always had the 0mb internal storage issue. So i tried many things to fix this but didn't work, until i followed a tutorial that ruined everything. Well .. the mistake is all mine because the tutorial stated to reformat cache and data and i did it with system too. Now my galaxy s7 doesn't boot anymore, it is stuck on the booting screen where it is written "Samsung Galaxy S7". In TWRP it is said my S7 doesn't have any operating system anymore and i can't flash anything with odin, it gets stuck at "Setting Partition". The only thing i can flash with Odin is TWRP and it doesn't help ... When i try to flash the stock rom with twrp installed, it says "Pass", the flash lasts 3 seconds and it doesn't change anything so i can bearly believe this works. I didn't find anything on the web so i hope you will help me.
Punch it.
PS : TWRP version is 3.2.3.0
Download the latest firmware files from updato or sammobile, install drivers then try again once more. Still of it is unsuccessful, boot into twrp and flash a custom rom.
amalantony said:
Download the latest firmware files from updato or sammobile, install drivers then try again once more. Still of it is unsuccessful, boot into twrp and flash a custom rom.
Click to expand...
Click to collapse
TWRP doesn't work anymore and this doesn't work (either methods) !
put your phone into Download mode and Boot OEM rom via odin.
Odin gets stuck
When i try to install the latest version i get stuck at "Set Partition"
<ID:0/004> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/004> sboot.bin.lz4
I had similar problem when was goin back from Oreo to Nougat.
By using TWRP i accidentally wiped full partition so I had to boot oem rom using odin.
But even odin couldnt do it.
Had FAIL message just before the end of the loading rom into the phone.
Then accidentally I plugget out the phone from laptop and got blue screen with big triangle on it saying to use windows smart switch to emergency recovery the partition.
I turned the phone off using power +vol- buttons and just after screen went off and before the vibra I pressed pwr+vol up+home to go into "odin download mode"
Try it, I dont think it will do more damage but it might help.
Hey there,
my Note 10.1 GT-n8010 bought in 2012 has been soft bricked for years but here I am giving it another try. Because of that, I have no memory of what software version was on the device, but I know it was rooted. The recovery mode is not working as the android logo with red triangle shows up, but I am able to go into download mode which says that: current binary and system status are both custom. I've tried flashing different stock ROMs from SAMMOBILE, starting with XEO (as it is my region) for 4.4.2 and 4.1.2 , but it didn't work. Every time I get sboot.bin FAIL in odin. I've also tried to install TWRP recovery and to root the device in order to unlock bootloader but then I get recovery.img fail in odin. So my main question is: what is causing sboot.bin to fail? I've read that flashing the most recent ROM usually makes this problem go away, but not in my case. Any advice would be greatly appreciated, thanks.
sboot wrong firmware for model or and older bootloader.
You need a rom firmware with the same bootloader.
Bootloader has never been locked.
JJEgan said:
sboot wrong firmware for model or and older bootloader.
You need a rom firmware with the same bootloader.
Bootloader has never been locked.
Click to expand...
Click to collapse
Could you point me in a direction of how to look for a correct ROM? On sammobile there are only two versions of ROMS for my region - 4.4.2 and 4.1.2 and none of them worked. Should I go through every possible region and hope for the best? How do I know that a ROM has the same bootloader? Since I can't turn on the device and find out the specifications of my system, is this just a guessing game? Thanks for taking the time to help me, by the way.
Was the Note purchased in your region ??
I would start with the oldest firmware any region a nd work through them.
Just make sure 16 or 32 gb is as your model.
Sammobile.
Updato.com.
Samsung-updates.
Are firmware sources.
I am also unable to revive my N8000, I can only go in download mode to flash.
Could you tell me when flashing a recovery with odin if the bootloader version matter ? I don't get that ? for me recovery are self loading no ?
No and no.
Suggest flash stock rom via Odin .
Fails post fail points in Odin
Galaxy note 10.1 (GT-N8000) cant get into recovery mode
JJEgan said:
No and no.
Suggest flash stock rom via Odin .
Fails post fail points in Odin
Click to expand...
Click to collapse
Sauces, my name is Caterina and I too have a problem with my Galaxy note 10.1 and looking for solutions on the internet I came to your forum. I hope you can help me. Let me explain: my tablet, while I was using it, froze without a reason and a few seconds later it restarted, remaining stuck on the word "samsung". You can't turn it off because if I press "power" it restarts. The only way to turn it off is to attach it to the charger. It does not go into recovery mode but only in odin mode. I tried to install a firmware download with SamFirm but it doesn't work. I tried with "dr. Phone" and nothing; with "reiboot for android" and nothing; I tried to install adb but if I type adb devices on the promt it doesn't find me the tablet despite the drivers are correctly installed (in fact odin if I connect in tablet via usb I recognize it). Usb debug is not active nor can I activate it since I cannot log in. The tablet is connected as an MTP. The twrp doesn't let me install it (I downloaded it from here https://forum.xda-developers.com/galaxy-note-10-1/orig-development/recovery-twrp-3-2-3-t3895276/ page4) but I didn't even understand what to do exactly. I downloaded the * .tar.md5 file and changed the extension to * .tar but nothing; I inserted the * .tar file in "AP"; I downloaded the img iso file but I don't know where to put it. I'm desperate. Help me to solve. One last thing, it's not possible to download the firmware from sammobile because you need a premium account and it's not the I. If any of you can download it could you alleviate it? Thanks in advance.
Install TWRP 2.8 * from TWRP thread or twrp.me .
Or try Philz recovery from this forum .
<I tried to install a firmware download with SamFirm but it doesn't work.>
What does not work mean what errors in Odin ??
What firmware .
Firmwares samsung-updates or updato .com .
JJEgan said:
Install TWRP 2.8 * from TWRP thread or twrp.me .
Or try Philz recovery from this forum .
<I tried to install a firmware download with SamFirm but it doesn't work.>
What does not work mean what errors in Odin ??
What firmware .
Firmwares samsung-updates or updato .com .
Click to expand...
Click to collapse
Hi and thanks for checking with me. I tried twrp 2.8.6.0 downloaded from twrp.me. I also tried previous versions for the GT-N8000 but to no avail. Clearly, since the models gt-n8010 and n8013 are not compatible with mine, is it possible to try the twrp for the p4notewifi or would I send the tablet in brik? Could you please send me the link to the recovery philiz please? However I also tried CF-auto-root and nothing. I state that I have never developed the root before and not so without root permissions I can share a non samsung firmware. Maybe that's why the recovery has been modified, not so. In any case, if there was a way to root now I would do it. I only care about saving the tablet and making it work.
This is after used twrp-2.8.6.0-gt-n8000.tar
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1303)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 8 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------- Post added at 04:47 AM ---------- Previous post was at 04:44 AM ----------
JJEgan said:
Install TWRP 2.8 * from TWRP thread or twrp.me .
Or try Philz recovery from this forum .
<I tried to install a firmware download with SamFirm but it doesn't work.>
What does not work mean what errors in Odin ??
What firmware .
Firmwares samsung-updates or updato .com .
Click to expand...
Click to collapse
However with the original firmware downloaded with both Samfirm and Samobile the error is sboot.ini fail. The versions of odin I tried are 3.13; 3.09 and 1.85.
JJEgan said:
Install TWRP 2.8 * from TWRP thread or twrp.me .
Or try Philz recovery from this forum .
<I tried to install a firmware download with SamFirm but it doesn't work.>
What does not work mean what errors in Odin ??
What firmware .
Firmwares samsung-updates or updato .com .
Click to expand...
Click to collapse
With Phliz touch 6.48.4 n8000.tar.md5 I have this
<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/006> Added!!
<ID:0/006> Odin engine v(ID:3.1303)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 7 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help me!!!!
Sboot fail is due to flashing a firmware that has older bootloader than the one on the tablet.
Flash later firmware.
Try latest firmware.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Usual rule of thumb with Odin is try another USB cable and ports on your computer. Normally the ones off the back side of a laptop/computer are the best to use since they are right off the motherboard. Odin is 100% connection sensitive. Always has been.
JJEgan said:
Sboot fail is due to flashing a firmware that has older bootloader than the one on the tablet.
Flash later firmware.
Try latest firmware.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Usual rule of thumb with Odin is try another USB cable and ports on your computer. Normally the ones off the back side of a laptop/computer are the best to use since they are right off the motherboard. Odin is 100% connection sensitive. Always has been.
Click to expand...
Click to collapse
Hi JJEgan, I tried them all but I just can't bypass the boot problem that prevents me from flashing firmware with odin. I wanted to try with the pit but since I know it could damage my tablet I wanted to know from you a site where to download a functional pit, suitable for my galaxy note gt-n8000. On the internet I found several but we know several versions: 4.04, 4.12 etc. and I don't know if it should match the pit version with the version of the rom I'm going to download. If I download the Italian Rom (since I am Italian) will I have to use an Italian pit or if the pit is of a given nationality, will the Rom also be of the same nationality? In odin, if I put the pit and pda, do I have to tick only the auto reboot and F. reset time boxes or even the re-partition box? Generally I know that the re-partition should never be selected but I read (but I'm not sure) that the inclusion of the pit involves selecting the distribution. Waiting for you to reply cordially.
No idea sorry PITs are model and 16 or 32 gb not countries .
I dont know about flashing PIT ,
But all questions have beeen answered already in the forum .
PIT is part of the firmware .
JJEgan said:
No idea sorry PITs are model and 16 or 32 gb not countries .
I dont know about flashing PIT ,
But all questions have beeen answered already in the forum .
PIT is part of the firmware .
Click to expand...
Click to collapse
Mine is a 16GB model. I found several pits but I didn't understand how to use them and, since the procedure is risky, I wanted to be sure to flash the right one and to operate correctly. Don't you know how to address me to some page where they talk about it? But do you think my tablet is recoverable? Believe me, it seems to me that whatever I do is not successful. Yet I thought that in the case of soft bricks something could still be done but I'm starting to lose hope. In any case, thank you for your time and wish you a good day.
Don't you know how to address me to some page where they talk about it
No sorry apart from the forums SEARCH .
and see
https://forum.xda-developers.com/galaxy-note-10-1/help
Looks like Odin cannot write the recovery, this leads me to assume that this is a faulty MMC which seems to be a rather common issue. I don't think that this is a recoverable issue unless you solder a new MMC.
For the recovery part, try this:
1) turn on the tablet
2) wait for a reboot
3) immediately after the screen goes black, press and hold power only, you will see the logo come up and then vanish quicker than before
5) as soon as it vanishes, release power and immediately press and hold it again and also press and hold volume up at the same time
6) after the Samsung logo appears again, release the power key but not the volume up
I found this to sometimes help with a boot loop. If this does not work, you are probably out of luck. The Samsung logo disappearing basically tells you that the partition (either boot or recovery) could not be loaded into RAM for the kernel to be started. The BL2 then panics and restarts the device.