G925F does not start anymore - Galaxy S6 Edge Q&A, Help & Troubleshooting

During sending an SMS my phone hangs, and does not start anymore.
The phone is rooted. I tried to start recovery but nothing happens (Vol UP + Home + Power Key).
Odin is working by VOL Down + Home + Power Key, so i tried to flashTWRP recovery (https://dl.twrp.me/zerolte/twrp-3.0.2-0-zerolte.img.tar.html)
Which has worked:
<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> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But I can still not start into Recovery(?)
I think the next steps is to try a full flash of complete image, right?
But can i download/backup some files from the phone without recovery, I don't want to loos all my data (if possible)
Are there any other procedures to try?
Best regards,
Tom

Now, I tried Smart Switch with recover option -> no success ;( Stuck on Samsung boot logo.
I think I need a new phone (any help?)

You can't backup anything without the phone on or recovery.
Try hold only POWER + VOL DOWN ONLY nothing else. This should force safe mode. If this doesn't boot up hold power and vol down again until it goes off then quickly switch to recovery mode combination. If this won't boot to recovery next thing is to flash stock firmware. But you will lose all data and it will flash a new recovery image.
What model is it and what region?

Thanks for your tips, unfortunatly it does not work -> Save mode also stuck on boot screen.
I also tried to flash stock firmware (G925FXXS4DPIF_G925FVFG4DPHB_G925FXXS4DPIF_HOME.tar) -> Same issue
Model: International Version: SM-G925F
Should I try to flash a new bootloader? Which one? What's about my EFS Backup?

offtopicfication said:
Thanks for your tips, unfortunatly it does not work -> Save mode also stuck on boot screen.
I also tried to flash stock firmware (G925FXXS4DPIF_G925FVFG4DPHB_G925FXXS4DPIF_HOME.tar) -> Same issue
Model: International Version: SM-G925F
Should I try to flash a new bootloader? Which one? What's about my EFS Backup?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/106963/G925FXXS4DPJ2_G925FBTU4DPH1_BTU/
Try to download and flash this.
I don't think you will be able to get any data off the phone now. But if you flash the firmware i just posed it should work.
Try twrp again and make backup of efs

callumbr1 said:
http://www.sammobile.com/firmwares/download/106963/G925FXXS4DPJ2_G925FBTU4DPH1_BTU/
Try to download and flash this.
I dont think you will be able to get any data off the phone now. But if you flash the firmware i just posed it should work
Click to expand...
Click to collapse
I fear the worst... still no look to boot into recovery, after flashing the provided firmeware and installing twrp again.
I think its a hardware fault (ram/memory issue)

offtopicfication said:
I fear the worst... still no look to boot into recovery, after flashing the provided firmeware and installing twrp again.
I think its a hardware fault (ram/memory issue)
Click to expand...
Click to collapse
Did you flash the UK BTU firmware i just posted above? Does odin show any error messages? What happens after odin passes and phone boots?

callumbr1 said:
Did you flash the UK BTU firmware i just posted above? Does odin show any error messages? What happens after odin passes and phone boots?
Click to expand...
Click to collapse
Of course, flashed G925FXXS4DPJ2_G925FBTU4DPH1_G925FXXS4DPI9_HOME.tar with Odin3_v3.12.3 in "AP Mode" and default settings.
No errors in log - the phone reboots automatically after flashing, stops at
PHP:
Samsung
Galaxy
S6 edge
POWERED BY
android
boot logo
Phone is since to ours in this state, I can't even shut down the phone. Only reboot with "Vol Down + Power" or "Vol Down + Home + Power" works (till to the next reboot halting at boot logo)

offtopicfication said:
Of course, flashed G925FXXS4DPJ2_G925FBTU4DPH1_G925FXXS4DPI9_HOME.tar with Odin3_v3.12.3 in "AP Mode" and default settings.
No errors in log - the phone reboots automatically after flashing, stops at
PHP:
Samsung
Galaxy
S6 edge
POWERED BY
android
boot logo
Phone is since to ours in this state, I can't even shut down the phone. Only reboot with "Vol Down + Power" or "Vol Down + Home + Power" works (till to the next reboot halting at boot logo)
Click to expand...
Click to collapse
Try the same firmware again with this PIT file
https://drive.google.com/file/d/0BzyeAt2hy6XeaXhVSUlGYTNobE0/view
In odin insert the PIT into pit and check repartition. Try that

here is a photo of the halted boot screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

wow, fast response

callumbr1 said:
Try the same firmware again with this PIT file
https://drive.google.com/file/d/0BzyeAt2hy6XeaXhVSUlGYTNobE0/view
In odin insert the PIT into pit and check repartition. Try that
Click to expand...
Click to collapse
What is this PIT file?
I'm in a state I try everything (I have even ordered a new phone - S7) - but i would really happy if i can cancel that order :fingers-crossed:
Here is the log:
Code:
<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> 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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<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)

Stuck at boot logo :crying:
should I restart the phone or flash twrp?

offtopicfication said:
What is this PIT file?
I'm in a state I try everything (I have even ordered a new phone - S7) - but i would really happy if i can cancel that order :fingers-crossed:
Here is the log:
Click to expand...
Click to collapse
It just rebuilds the partitions. Try it to see if it works. Just put the firmware into AP and put the PIT into pit. Check f reset time, auto reboot and repartition.

callumbr1 said:
It just rebuilds the partitions. Try it to see if it works. Just put the firmware into AP and put the PIT into pit. Check f reset time, auto reboot and repartition.
Click to expand...
Click to collapse
I followed exactly your described steps, but still no behavior change...

offtopicfication said:
I followed exactly your described steps, but still no behavior change...
Click to expand...
Click to collapse
Hmmmm strange. Is your phone network locked?

callumbr1 said:
Hmmmm strange. Is your phone network locked?
Click to expand...
Click to collapse
no

offtopicfication said:
no
Click to expand...
Click to collapse
Whst region are you in?

Phone feels slightly warmish

callumbr1 said:
Whst region are you in?
Click to expand...
Click to collapse
Austria

Related

[Q] pls help me... brick

i have a galaxy s3..
The android version was 4.0.3
I wanted to renew the version to 4.1.2 so i downloaded the stock british ROM4.1.2
I opened ODIN and put the md5 file in PDA and conected the PHONE into the computer (DoWNLOAD)
afet clicking START it was kind of stuck on BOOT.img and FAILED. I disconnected the phone and he worked...
i tried another version and a blue line started to apper in the DOWNLOAD MOD but it STUCKED again.. so i disconnected the phone and now i have the messege: "FIRMWARE UPGRADE ENCOUNTERED AN ISSUE.PLEASE SELECT RECOVERY MODE IN KIES AND TRY AGAIN"
what should i DO ?? i can only gen into download mode
What guide were you following? Did it say to put the firmware into "pit"?
Considering you have no idea what you're doing, it's unlikely you'll manage to fix this by yourself.
Short answer: flash the correct pit file
Glebun said:
What guide were you following? Did it say to put the firmware into "pit"?
Considering you have no idea what you're doing, it's unlikely you'll manage to fix this by yourself.
Short answer: flash the correct pit file
Click to expand...
Click to collapse
oh sorry i meant PDA ...
So you only flashed the pit file without the actual Firmware?
You really need a guide to not screw things up here now.
If download mode is working, good.
What files do you have in your firmware zip file. I mean there can`t be only a Pit file.
List all files here detailed.
Edit:
So there was only one File? and you put it in pda?
If yes that should be correct.
What Galaxy S3 do you have? The international one? I9300 ?
Also provide a link from where did you download the Firmware?
http://forum.xda-developers.com/showthread.php?t=1978840
Then try reading the basics before flashing anything .
Ignorance = a brick .
jje
1. tell us where exactly you got the firmware
2. read the product name under the battery. is it I9300?
Scarface1991 said:
So you only flashed the pit file without the actual Firmware?
You really need a guide to not screw things up here now.
If download mode is working, good.
What files do you have in your firmware zip file. I mean there can`t be only a Pit file.
List all files here detailed.
Edit:
So there was only one File? and you put it in pda?
If yes that should be correct.
What Galaxy S3 do you have? The international one? I9300 ?
Also provide a link from where did you download the Firmware?
Click to expand...
Click to collapse
YES i have I9300.
I have downloaded this:
write this on google: hotfile I9300XXELLA_I9300OXAELLA_BTU.zip
the first link
sorry for the split... XDA don't allow me to post "outside links"
take the battery out and confirm you have an i9300.
provide an Odin screenshot of the error
How many files are in the zip file?
taltalm3 said:
YES i have I9300.
I have downloaded this:
write this on google: hotfile I9300XXELLA_I9300OXAELLA_BTU.zip
the first link
Who on earth knows what file that is from roomyshare.com . It could be good bad full of malware wrong file anything .
Download from a genuine source only .
jje
Click to expand...
Click to collapse
Glebun said:
take the battery out and confirm you have an i9300.
provide an Odin screenshot of the error
Click to expand...
Click to collapse
YES i have an I9300
I can't screenshot because it isn't happens it's just stuck
and this is what is wrote:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXELLA_I9300OXAELLA_742798_REV00_user_low_ship.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> boot.img
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Scarface1991 said:
How many files are in the zip file?
Click to expand...
Click to collapse
2:
the MD5 file and
SS_DL.dll
Ok first download a firmware that is absolutely safe to use. You can use this site to do so or search here at XDA for a Firmware:
http://www.sammobile.com/firmwares/1/
XDA I9300 Firrmwares (Check the second post of that thread and search for your country):
http://forum.xda-developers.com/showthread.php?t=1646610
afterwards check how many files there are in the firmware zip and then use this guide to flash the firmware:
Intratech said:
1. Just download the firmware version you want from the second or third posts and extract the .tar or .tar.md5 file in the archive and save it somewhere
2. Reboot your phone to download mode.
To get download mode shut down the device. After it shuts off completely simultaneously press the Down volume key+ Home button + press the power button .
You should see a warning asking you to press volume up if you want to continue or volume down to cancel, press volume up. You are now in download mode!
3. Start Odin
4. Click on the PDA button and browse to the .tar or .tar.md5 file that you extracted in step 1
If the package has more than one .tar archive then they will be labelled with PDA, Phone/Modem and CSC. Just put them in the corresponding section of Odin
5. DO NOT PUT .PIT FILE AND DO NOT, I REPEAT, DO NOT TICK REPARTITION.
Anyone ask about .pit file is a moron
Should look like this screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If the package has 3 files it should look like this:
Regardless of firmware version it's still the same methodology
6. Connect the USB cable and wait for the ID:COM section to turn yellow
7. Click start to flash
8. Do not disconnect the cable or turn off the device, it will reboot when it finishes.
Click to expand...
Click to collapse
My suspicion is that kies interrupted the flash.....Did you disable kies before the flash?
asked rruplow
Scarface1991 said:
Ok first download a firmware that is absolutely safe to use. You can use this site to do so or search here at XDA for a Firmware:
http://www.sammobile.com/firmwares/1/
XDA I9300 Firrmwares (Check the second post of that thread and search for your country):
http://forum.xda-developers.com/showthread.php?t=1646610
afterwards check how many files there are in the firmware zip and then use this guide to flash the firmware:
Click to expand...
Click to collapse
I did it and it stuck on SYSTEAM.img
what now? :crying:
slaphead20 said:
My suspicion is that kies interrupted the flash.....Did you disable kies before the flash?
Click to expand...
Click to collapse
yes
taltalm3 said:
I did it and it stuck on SYSTEAM.img
what now? :crying:
yes
Click to expand...
Click to collapse
Ok this is weird. What's the situation right now? Are you in download mode or is your phone still hooked up to the computer and it's stuck at system.img?
Sent from my GT-I9300 using xda app-developers app
Scarface1991 said:
Ok this is weird. What's the situation right now? Are you in download mode or is your phone still hooked up to the computer and it's stuck at system.img?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
FAIL
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXELL4_I9300OJKELK9_I9300JKELK4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> system.img
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The same error is what I got. It was the service centre for my phone.
Sent from my GT-I9300 using xda app-developers app
Help someome please

Phone is bricked - pit file issue

Hi All,
My phone is GT I9300 International Version,
ROM Installed before incident: one of the latest (past month) CM 10.1 nightly builds.
Woke up this morning and my phone was in download mode and my screen was like this and it kept rebooting:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried taking out the battery / reboot / connecting to usb problem persists the rom is not loading and bring you back to download mode with the white screen.
Tried to enter the following modes:
Recovery Mode: NO RECOVERY MODE, it enters back to the download mode.
Download Mode: when entering download mode the phone screen is black as it should be
Conclusion: DOWNLOAD MODE IS THE ONLY AVAILABLE MODE I HAVE !
So, i figured something probably have gone bad in the phone but it's fixable since i can still go into the download mode.
So i downloaded one of the stock roms from samsmobile and tried with odin
Odin 1.85/3.04/3.07 - Getting error messages:
every time i tried reflashing it has lost the driver connection and even though it showed "Added" in the ODIN sometimes it wouldn't pass the setup connection step, so everytime i had to reboot the phone in order for the connection to be properly initialized.
PDA file to flash -
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUFME3_I9300OJKFME1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
No Pit ? So i downloaded a PIT:
SGS3\GT-I9300_mx_20120220.pit - this one fits the i9300 with 16gb according to what i searched and off course the model i own.
here is the odin output
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
and that's it it was just stuck like this forever...
I should mention that i tried different USB ports or even computers (all win7 64 bit) also tried runnning it(odin) with windows xp sp3 compatibility
usually when you start download mode and odin has started already you would see some kind of a progress bar on the actual phone,
that was missing as well...meaning the phone didnt seem to respond so far to the odin although it did shows sign of connectivity.
does anyone have a solution for this issue ???
Flashing Pit can kill your phone ..
But looks like your PIT was damaged anyway .
Solution is a service centre repair or buy a new motherboard .
jje
JJEgan said:
Flashing Pit can kill your phone ..
But looks like your PIT was damaged anyway .
Solution is a service centre repair or buy a new motherboard .
jje
Click to expand...
Click to collapse
Is this the famous MotherBoard Bug ? My version was 1.1
Anyhow, the download mode works its just you can't do anything with it because the its missing a pit file and can't upload one apparently ...
Anyone has a better suggestion about how to forcibly re-partition the drive ? and set the pit file ?
to me it sounds like a SD CARD issue and not a motherboard issue...
Does it show product name while in download mode? Or is it blank?
No its not SDS.
If you think its sd card then you are confused as NAND is part of the motherboard .
As you have no warranty then its certainly worth trying to repartition .
Sorry i don't know where the relevant post is .
jje
dxppxd said:
Does it show product name while in download mode? Or is it blank?
Click to expand...
Click to collapse
Hi,
Nope it doesn't say the product name in that field, what does it mean ?
here is the out of that...
ODIN MODE
PRODUCT NAME:
CUSTOME BINARY DOWNLOAD: No
CUSTOME BINARY: Samsung Official
SYSTEM STATUS: Custom
JJEgan said:
No its not SDS.
If you think its sd card then you are confused as NAND is part of the motherboard .
As you have no warranty then its certainly worth trying to repartition .
Sorry i don't know where the relevant post is .
jje
Click to expand...
Click to collapse
its ok, thanks for the patience,
i thought the re-partitioning is related to the space allocation between the partitions.
but you right since its just a few kb file it can sit on the nand, and be flashed.
Just got the exact same problem, used cyanogenmod 10.1 for a long time. Last days it has been freezing all the time so i put MIUI on it and after an hour it died.
If your product name is blank in download then you have SDS, return to Samsung for warranty repair.
Try flashing any kernel in odin and than check result
Sent from my GT-I9300 using xda app-developers app
Does anybody has a explaination for the white stripes on the screen? Normally the download mode screen is just clear but when it turns on it get's stuck at the white stripes.
Factionwars said:
Does anybody has a explaination for the white stripes on the screen? Normally the download mode screen is just clear but when it turns on it get's stuck at the white stripes.
Click to expand...
Click to collapse
The motherboard is blown, memory control chip is toast which probably explains the white lines.
boomboomer said:
The motherboard is blown, memory control chip is toast which probably explains the white lines.
Click to expand...
Click to collapse
Great, thanks. Hopefully they will repair my phone under warranty. It has been a very long time modding and running cm10.1.
idanohh said:
Hi All,
My phone is GT I9300 International Version,
ROM Installed before incident: one of the latest (past month) CM 10.1 nightly builds.
Woke up this morning and my phone was in download mode and my screen was like this and it kept rebooting:
Tried taking out the battery / reboot / connecting to usb problem persists the rom is not loading and bring you back to download mode with the white screen.
Tried to enter the following modes:
Recovery Mode: NO RECOVERY MODE, it enters back to the download mode.
Download Mode: when entering download mode the phone screen is black as it should be
Conclusion: DOWNLOAD MODE IS THE ONLY AVAILABLE MODE I HAVE !
So, i figured something probably have gone bad in the phone but it's fixable since i can still go into the download mode.
So i downloaded one of the stock roms from samsmobile and tried with odin
Odin 1.85/3.04/3.07 - Getting error messages:
every time i tried reflashing it has lost the driver connection and even though it showed "Added" in the ODIN sometimes it wouldn't pass the setup connection step, so everytime i had to reboot the phone in order for the connection to be properly initialized.
PDA file to flash -
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUFME3_I9300OJKFME1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
No Pit ? So i downloaded a PIT:
SGS3\GT-I9300_mx_20120220.pit - this one fits the i9300 with 16gb according to what i searched and off course the model i own.
here is the odin output
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
and that's it it was just stuck like this forever...
I should mention that i tried different USB ports or even computers (all win7 64 bit) also tried runnning it(odin) with windows xp sp3 compatibility
usually when you start download mode and odin has started already you would see some kind of a progress bar on the actual phone,
that was missing as well...meaning the phone didnt seem to respond so far to the odin although it did shows sign of connectivity.
does anyone have a solution for this issue ???
Click to expand...
Click to collapse
i have the same problem please can u help me. im missing a pit file can u send me a link for pit file
Please can some help me my sgs3 i9300 international. is stuck on boot logo but will go into download mode. Ive flashed a stock rom but it says failed missing pit file. Com6 can some one send me a link please
Sent from my GT-I9505 using XDA Premium 4 mobile app
You can try this solution:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Read and follow the instructions exactly. If it doesn't work then you'll need a new motherboard, there is no other software solution.
It's NAND problem and it's solved
Hi,
this happens when you tick by mistake NAND ERASE ALL in ODIN software (ver.3 and newer), and then is partition damaged or couldn't be restored as the device need. Or when the some apps has access to EFS folder or DEV folder. Could be damaged partition.
Problem is solved here: Boot logo not boot animations disappeared! - solution is here! :highfive:
Regards, Peter
P.S. In thread above I explain all and btw. I had white stripes before starting my tablet! Everything will great after rebooting but white strips stayed.

boot loader files seems to be corrupted‏

Hi guys:
I have a problem with my GT-I9305. Last week it showed me some messages about a Policy Update and an app trying to access files. I clicked on Upgrade and it said that I have the latest one. (words more than less). Friday morning it restarts itself and never passes the 1rst screen, the one saying Galaxy S III GT-I9305, not even the one saying Samsung.
So I went to Samsung Support in Melbourne and been told that main PCB is faulty and need to be replaced. But.... there is the reason of my post ... I found that I can enter download mode and even I tried to do a factory reset. But apparently NAND files are corrupted as the boot files are missing. (Images attached) I have errors like :
E:failed to mount / cache (no such file or directory)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now , a faulty PCB won’t allow me accessing download mode or android factory reset / wipe options , I believe. (or want to believe)
So, is there a way to flash the whole thing and resuscitate my phone?
I tried to use Odin V1.85, V3.09, V3.10 with firmaware taken from sammobile for Australia Optus (as I bought the phone from them) I9305XXUENC2_I9305OPSENC3_I9305XXUENA2_HOME.tar.md5
It failed all times.
Some forums suggest me to flash the .pit file, but I can’t find the one corresponding to my phone.
So the thing is : can my phone be hard bricked and still give me the down load options ?
if No, How can I flash the NAND files
This is a Galaxy S III LTE for Australia, service provider Optus. I did not root it and it was using stock firmware with officials updates. and yes , of course it's out of warranty. (otherwise the guys in Samsung would put more effort in fixing it)
Model: GT-I9305
FCC ID : A3LGTI9305
SSN: -I9305GSMH
Any help is much appreciated.
Do anyone knows how to restore / flash the bootloader ?
That could take me in the right direction
jonathan.alvarez.castillo said:
Do anyone knows how to restore / flash the bootloader ?
That could take me in the right direction
Click to expand...
Click to collapse
Hey Jonathan, I haven't used a Samsung Device for a while as I moved on to use Sony devices, but I'm gonna try to help you out as you asked me on http://forum.xda-developers.com/showpost.php?p=61923100&postcount=149
Just give this a go.
Download this Vodafone firmware from here http://www.sammobile.com/firmwares/download/50575/I9305XXUFOD3_I9305VNZFOD1_VNZ/
Follow the instructions you see on the bottom of the page that includes downloading Odin v.3.10.6. After that if it's failed again then re flash the firmware with Re-Partition ticked and pit file included. Find the attached pit file for I9305
kamalmawa said:
Hey Jonathan, I haven't used a Samsung Device for a while as I moved on to use Sony devices, but I'm gonna try to help you out as you asked me on http://forum.xda-developers.com/showpost.php?p=61923100&postcount=149
Just give this a go.
Download this Vodafone firmware from here http://www.sammobile.com/firmwares/download/50575/I9305XXUFOD3_I9305VNZFOD1_VNZ/
Follow the instructions you see on the bottom of the page that includes downloading Odin v.3.10.6. After that if it's failed again then re flash the firmware with Re-Partition ticked and pit file included. Find the attached pit file for I9305
Click to expand...
Click to collapse
Thanks for replying , I definitely will give it a go. :good:
By the way I notice you give me a link to New Zealand - Vodaphone Firmaware, but mine is an Australian - Optus. Would it work in the same way using the following firmware, given the same PIT file you mentioned ?
http://www.sammobile.com/firmwares/download/28984/I9305XXUENC2_I9305OPSENC3_OPS/
jonathan.alvarez.castillo said:
Thanks for replying , I definitely will give it a go. :good:
By the way I notice you give me a link to New Zealand - Vodaphone Firmaware, but mine is an Australian - Optus. Would it work in the same way using the following firmware, given the same PIT file you mentioned ?
http://www.sammobile.com/firmwares/download/28984/I9305XXUENC2_I9305OPSENC3_OPS/
Click to expand...
Click to collapse
Yeah it doesn't matter, Except New Zealand firmware is newer and Android 4.4.4 Kit Kat while Optus firmware is Android 4.3 Jelly Bean. If you already downloaded the Optus firmware then don't waste your time downloading the NZ firmware. See if you can boot your phone after re-partitioning with .pit file
kamalmawa said:
Yeah it doesn't matter, Except New Zealand firmware is newer and Android 4.4.4 Kit Kat while Optus firmware is Android 4.3 Jelly Bean. If you already downloaded the Optus firmware then don't waste your time downloading the NZ firmware. See if you can boot your phone after re-partitioning with .pit file
Click to expand...
Click to collapse
I tried with the .pit file and Optus Firmware I9305XXUENC2_I9305OPSENC3_OPS, also
I9305TDVUENC1_I9305TXSAEND2_XSA , ticked Re-partition and even Nand Erase all (3 combination), and the result was :
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305TDVUENC1_I9305TXSAEND2_I9305TDVUENC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin engine v(ID:3.1005)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Set PIT file..
<ID:0/016> DO NOT TURN OFF TARGET!!
<ID:0/016> FAIL!
<ID:0/016>
<ID:0/016> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Not too much luck
And without selecting the pit file , I got:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305TDVUEMK4_I9305TXSAENB1_I9305TDVUEMK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin engine v(ID:3.1005)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> SingleDownload.
<ID:0/016> sboot.bin
<ID:0/016> NAND Write Start!!
<ID:0/016> FAIL!
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Give it a another go with old version of Odin 3.07 attached below, which is the last version I used with my S3. Try it with and without .pit . I'm afraid I can't think of anything other than hardware fault if it still fails after that. Also make sure Kies not running on background and Samsung USB drivers are installed. Good luck
kamalmawa said:
. I'm afraid I can't think of anything other than hardware fault if it still fails after that.
Click to expand...
Click to collapse
It's not taking it...
:crying: RIP my good old GT-I9305.
Ohhh just remember, is there a way to do the same with an SD card?, I mean not using Oding?
Perhaps I could bypass the issue and install from the inside.
jonathan.alvarez.castillo said:
It's not taking it...
:crying: RIP my good old GT-I9305.
Ohhh just remember, is there a way to do the same with an SD card?, I mean not using Oding?
Perhaps I could bypass the issue and install from the inside.
Click to expand...
Click to collapse
You could try.. But You need a custom recovery first such as CWM or TWRP.. Good luck
Well, all efforts were made to save the good old S3, RIP GT-i9305.
We had good times but you departed too early.
Kamalmawa thanks for your efforts.
AAAAND now I have a shiny new S5 $40 plan, 1 GB data. not too bad

Am I dumb or is Odin just garbage?

I've been trying to flash the unlocked firmware and debrand and get rid of the bloat. But either gets stuck on Setupconnection or Initializing..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6787 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> FAIL! (DeviceInfo)
I've also tried downgrading the version so i can sideload pie BUUUUT of course it does the same thing. I don't get it. I've ALWAYS had issues with Odin with ANY samsung device. I have windows 10. What's the deal here? I'm using the ATT variant of the S9+ I've read people saying OMG IT WORKS THANKS but I can't get odin to do anything but FAIL and get stuck on bloated firmware. And these threads tend to get ignored so I really hope someone has an idea.
I've ran it as admin. I've turned it on as admin THEN plugged the phone in. I've tried literally everything possible and it just fights me.
Are you putting the phone in download mode?
Odin has been around since the dinosaurs, and has been roc solid since then. You're doing something wrong, or have an issue somwhere on your end.
Are you enabling usb debugging on the phone and using the patched Odin?
the_scotsman said:
Are you putting the phone in download mode?
Odin has been around since the dinosaurs, and has been roc solid since then. You're doing something wrong, or have an issue somwhere on your end.
Click to expand...
Click to collapse
I've been modifying android devices since the captivate. yes its in download mode. It wouldn't read on odin if it wasn't.
YrrchSebor said:
Are you enabling usb debugging on the phone and using the patched Odin?
Click to expand...
Click to collapse
what will usb debugging do in download mode? Isn't that only useful in the system?
Konner920 said:
I've been modifying android devices since the captivate. yes its in download mode. It wouldn't read on odin if it wasn't.
Click to expand...
Click to collapse
EDIT: Put it BACK in download mode, put debugging on. Same issue. I'm not doing anything different than I always have using Odin. Ever since KNOX samsung phones have been a pain. I even installed a XP VM and it did the same thing, aswell as a windows 7 VM.
Konner920 said:
I've been modifying android devices since the captivate. yes its in download mode. It wouldn't read on odin if it wasn't.
Click to expand...
Click to collapse
So you're obviously using the correct version of Odin then I assume?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the_scotsman said:
So you're obviously using the correct version of Odin then I assume?
Click to expand...
Click to collapse
Yes the patched Odin. I've tried so many different firmwares and NONE will flash.
and everytime.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6787 M
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6787 M
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6787 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
then it'll give a DeviceInfo error and fail.
Konner920 said:
what will usb debugging do in download mode? Isn't that only useful in the system?
Click to expand...
Click to collapse
That's what I thought but I was advised to enable it in the developer options. I flashed a Verizon s9 plus to the unlocked firmware with no issues at all, using that same Odin. I was also advised to choose a firmware that has the same bootloader version that the phone was currently on.
YrrchSebor said:
That's what I thought but I was advised to enable it in the developer options. I flashed a Verizon s9 plus to the unlocked firmware with no issues at all, using that same Odin. I was also advised to choose a firmware that has the same bootloader version that the phone was currently on.
Click to expand...
Click to collapse
How can I tell what bootloader version I have? It's just the firmware version for it in recovery
Konner920 said:
How can I tell what bootloader version I have? It's just the firmware version for it in recovery
Click to expand...
Click to collapse
The 5th number from the end is either 1,2, or 3. So I checked in the phone info app and currently I had 1, so I chose an unlocked firmware that also had a 1 there. It flashed fine, and then it got all the OTA updates to get up to the latest unlocked build. Hope you figure it out!
Oh, I was also advised to choose an XAA firmware, but I have no idea why or what that even really means. I think it just means it's completely carrier free. Also I used CSC rather than Home CSC
YrrchSebor said:
The 5th number from the end is either 1,2, or 3. So I checked in the phone info app and currently I had 1, so I chose an unlocked firmware that also had a 1 there. It flashed fine, and then it got all the OTA updates to get up to the latest unlocked build. Hope you figure it out!
Oh, I was also advised to choose an XAA firmware, but I have no idea why or what that even really means. I think it just means it's completely carrier free. Also I used CSC rather than Home CSC
Click to expand...
Click to collapse
My bootloader has a 3, and I don't see any XAA firmware with a 3 on the bootloader.
YrrchSebor said:
The 5th number from the end is either 1,2, or 3. So I checked in the phone info app and currently I had 1, so I chose an unlocked firmware that also had a 1 there. It flashed fine, and then it got all the OTA updates to get up to the latest unlocked build. Hope you figure it out!
Oh, I was also advised to choose an XAA firmware, but I have no idea why or what that even really means. I think it just means it's completely carrier free. Also I used CSC rather than Home CSC
Click to expand...
Click to collapse
I literally can't get it to do anything
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> apdp.mbn
<ID:0/004> msadp.mbn
<ID:0/004> persist.img.ext4
<ID:0/004> userdata.img.ext4
<ID:0/004> dqmdbg.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> Total Binary size: 4655 M
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
if I try without the home CSC it just says Setupconnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I spam start til it says initializalize, and it FAILS with (Deviceinfo)
And I can't return this piece of **** cause best buy wants a 45 dollar restocking fee.
Konner920 said:
My bootloader has a 3, and I don't see any XAA firmware with a 3 on the bootloader.
Click to expand...
Click to collapse
The XAA is probably not crucial, but the bootloader number is I believe. Any luck yet?
Try to delete all android and samsung drivers on your PC. If you have Kies or smart switch uninstall it. Then start your phone in download mode and open odin. At least plug it into your PC and wait a few minutes, that Windows can find the drivers.
Are you launching ODIN as admimistrator? As in right click on it and selecting "runa as administrator "
Sent from my SM-G965U1 using Tapatalk
I ended up just taking it back for a refund, the razer phone 2 is under AT&T with no bloat so I'm waiting for my refund from best buy. I liked the phone, too much bloat and bixby is the most worthless assistant. It wasnt even worth trying to disable it, samsung lost their touch. I miss the old galaxy phones without KNOX and this bixby crap. so this can be closed.
had the same issue. Changed USB cable and all was good.
Konner920 said:
I've been trying to flash the unlocked firmware and debrand and get rid of the bloat. But either gets stuck on Setupconnection or Initializing..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6787 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006>
<ID:0/006> FAIL! (DeviceInfo)
I've also tried downgrading the version so i can sideload pie BUUUUT of course it does the same thing. I don't get it. I've ALWAYS had issues with Odin with ANY samsung device. I have windows 10. What's the deal here? I'm using the ATT variant of the S9+ I've read people saying OMG IT WORKS THANKS but I can't get odin to do anything but FAIL and get stuck on bloated firmware. And these threads tend to get ignored so I really hope someone has an idea.
I've ran it as admin. I've turned it on as admin THEN plugged the phone in. I've tried literally everything possible and it just fights me.
Click to expand...
Click to collapse
i have the same problem, how to fix it? am i downloading the wrong firmware or i just did it wrong?
Same exact problem and history with Odin. Was a solution found for this?
Same exact problem.
All threads completed. (succeed 0 / failed 1)
Any knows solutions?

It seemes I totally bricked my S6

Hi,
I did a lot of trying to get twrp installed.
After a while I followed a hint and it worked but I lost Magisk.
After installing Magisk I got a bootloop. Magiskuninstaller didn't work and all other methods I know also didn't help.
Now I have only twrp working and maybe that's the only possibility to install anything, because in ODIN I always get failures
e.g.
Trying to install bootloader:
<ID:0/007> abl.elf
<ID:0/007> xbl.elf
<ID:0/007> xbl_config.elf
<ID:0/007> FAIL! (Auth)
and
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
or, when I tick Re-Partition in options
<ID:0/007> Can't open the specified file. (Line: 2006)
any help would be appreciated
Firstly, and please forgive me for nitpicking in your time of dread, if your device can power on it is not bricked, despite what so many uninformed folks say; "bricked" means there is no way to get it to even power on. And since I'm in 'education mode' there is no such thing as "soft brick"; it's like saying something is "kinda dead", and there is no such things as zombies irl.
Anyways, have you tried resetting the tab in recovery mode? Good instructions here:
https://www.hardreset.info/devices/samsung/samsung-galaxy-tab-s6/recovery-mode/
TiTiB said:
Anyways, have you tried resetting the tab in recovery mode? Good instructions here:
https://www.hardreset.info/devices/samsung/samsung-galaxy-tab-s6/recovery-mode/
Click to expand...
Click to collapse
First: Thanks for your support
But: I'm in twrp recovery not in stock
and I cannot enter safe mode
any solution for this?
Tronje said:
First: Thanks for your support
But: I'm in twrp recovery not in stock
and I cannot enter safe mode
any solution for this?
Click to expand...
Click to collapse
I don't think I've had to use button combos while in TWRP, but their purpose is to *force* your device in to a certain state (in this case Recovery), no matter what state they are currently in. Usually in such cases where it looks like critical files or operations are messed up, common, and sound, advice is to get back to stock and then do, whatever.
Other than that, I'll have to defer to what others have to say. Good Luck!
or is there a way to do it via sideload?
it's totally crazy, nothing seemes to work
I was able to install stock boot image and stock recovery that I extracted from firmware that I downloaded from samfrew hopefully I could solve the problems with odin - but failed
I'm even not able to shut down the tablet when connected to powercable - there is a permanent bootloop
I was able to take some photos. Maybe someone will realize what else I could try to do. The large photo shows, what happened when I tried to sideload several versions of the downloaded firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tronje said:
or is there a way to do it via sideload?
it's totally crazy, nothing seemes to work
I was able to install stock boot image and stock recovery that I extracted from firmware that I downloaded from samfrew hopefully I could solve the problems with odin - but failed
I'm even not able to shut down the tablet when connected to powercable - there is a permanent bootloop
I was able to take some photos. Maybe someone will realize what else I could try to do. The large photo shows, what happened when I tried to sideload several versions of the downloaded firmware
View attachment 4988349
View attachment 4988351
View attachment 4988353
View attachment 4988355
Click to expand...
Click to collapse
I'm not an expert here by any means, but I think if you can get to fastboot/bootloader you can use ODIN to do a full restore. I would think you can also use fastboot to just restore the recovery partition as well.
ChrisDos said:
I'm not an expert here by any means, but I think if you can get to fastboot/bootloader you can use ODIN to do a full restore. I would think you can also use fastboot to just restore the recovery partition as well.
Click to expand...
Click to collapse
Dear,
did you really read my post?
I need real, detailled help because I'm always getting errors in Odin.
I think Odin is no longer an option.
Mostly it ends with an FAIL! (Auth)
or Re-Partition operation failed
or, when I tick Re-Partition in options: <ID:0/007> Can't open the specified file. (Line: 2006)
I was so desperate that I was looking for a PIT-file, who knows wherefore, but no success.
I ticked and unticked I think every possible options in Odin, tried several releases of firmware with several releases of Odin-Software and also different twrp releases.
My last hope was my old notebook, as I read, that sometimes there are differences in behaviour between some PC, but failed again.
Maybe a detailed instruction how and what to sideload or another PIT-File (I found only this one: GTS6L_EUR_OPEN.pit)
Maybe that's the problem: I'm using German firmware with European PIT? But I couldn't find European firmware oder German PIT
Tronje said:
Dear,
did you really read my post?
I need real, detailled help because I'm always getting errors in Odin.
I think Odin is no longer an option.
Mostly it ends with an FAIL! (Auth)
or Re-Partition operation failed
or, when I tick Re-Partition in options: <ID:0/007> Can't open the specified file. (Line: 2006)
Click to expand...
Click to collapse
Might want to use Frija to download the firmware. If ODIN is no longer an option, then all is lost. I highly doubt that is though. I've had issues with specific USB cables not working or a bad USB port. I wouldn't panic yet as TiTiB said. As long as you can get it to turn on and get to the bootloader, there should be a way to recover it.
Looks at the Tab 5Se, S10, note 10, etc threads on recoveries. The Tab S6 forums don't seem to be nearly as prolific as other forums.
I know you are at your wits end, but hang end there. Try using Frija to get the proper firmware. You might even try going back to the original or second release in August of last year. You key is going to be getting ODIN to do the work though. I also fine it ludicrous that the Samsung devices have so many different boot options using the keys. Evening the timing of pressing the buttons in a certain order is critical.
ChrisDos said:
Might want to use Frija to download the firmware.
Click to expand...
Click to collapse
ok, I did, downloaded, flashed with the same disappointing result
ChrisDos said:
If ODIN is no longer an option, then all is lost. I highly doubt that is though. I've had issues with specific USB cables not working or a bad USB port. I wouldn't panic yet as TiTiB said. As long as you can get it to turn on
Click to expand...
Click to collapse
I even cannot shut it down. That's what make me think, it's lost.
ChrisDos said:
and get to the bootloader, there should be a way to recover it.
Click to expand...
Click to collapse
I didn't find any. In bootloader there should be a warning message first before entering, but there is none. And later some characters (a status message or something like that) on the top of the screen, but there is none.
ChrisDos said:
Looks at the Tab 5Se, S10, note 10, etc threads on recoveries. The Tab S6 forums don't seem to be nearly as prolific as other forums.
Click to expand...
Click to collapse
that's my very last hope
Tronje said:
I even cannot shut it down. That's what make me think, it's lost.
Click to expand...
Click to collapse
All is not lost - If it powers on, it isn't bricked - Simply software malfunctioning. Would assume you've corrupted the system with Magisk, which means just flashing stock should fix it. No idea why Odin isn't working though, since you've already flashed back to stock recovery - Are you sure you have the correct Firmware? Your bootloader is probably locked again, so you won't be able to flash anything but stock.
bartleby999 said:
All is not lost - If it powers on, it isn't bricked - Simply software malfunctioning. Would assume you've corrupted the system with Magisk, which means just flashing stock should fix it. No idea why Odin isn't working though, since you've already flashed back to stock recovery - Are you sure you have the correct Firmware? Your bootloader is probably locked again, so you won't be able to flash anything but stock.
Click to expand...
Click to collapse
I tried all available firmware versions with different odin releases. It's always the same:
<ID:0/010> Initialzation..
<ID:0/010>Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Re-Partition operation failed.
Trying to flash twrp recovery:
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> vbmeta.img
<ID:0/007> FAIL! (Auth)
<ID:0/007>
I really really would like to know where this FAIL! (Auth) comes from. But all google search brought solutions not fitting to my situation.
Few minutes ago it just let me flash TWRP_T865_3.3.1-9.tar without grumbling - but there is no twrp recovery, only stock
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
with TWRP_T865_3.3.1-10L.tar I'm getting error message again
Tronje said:
I tried all available firmware versions with different odin releases. It's always the same:
...
Click to expand...
Click to collapse
I just posted a solution here: https://forum.xda-developers.com/showpost.php?p=82229527&postcount=7
Moe5508 said:
I just posted a solution here: https://forum.xda-developers.com/showpost.php?p=82229527&postcount=7
Click to expand...
Click to collapse
That's great news. Now I got one step further.
For the first time there are some characters on the screen. (see attached file)
... but FAIL! (Auth)
persists
when I tried flashing BL-File
That's great indeed.
Now we get down to the firmware issues...it appears you might have upgraded to a higher BL one which may not allow you to downgrade BL)...might I suggest you try a different firmware?
And you are also already OEM Unlocked, right?
Was this round one of flashing BL, or round two, as per my guide? Please PM me and lets troubleshoot that way rather...
Moe5508 said:
That's great indeed.
Now we get down to the firmware issues...it appears you might have upgraded to a higher BL one which may not allow you to downgrade BL)...might I suggest you try a different firmware?
And you are also already OEM Unlocked, right?
Was this round one of flashing BL, or round two, as per my guide? Please PM me and lets troubleshoot that way rather...
Click to expand...
Click to collapse
display shows
FRP LOCK : OFF
OEM LOCK : OFF (U)
so I think I'm unlocked
I tried all German 4 firmware releases and I always failed in step 1
I got my device in november with october release and upgraded to december release
Here's the full log of Odin, it always shows the same result:
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 152 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> NAND Write Start!!
<ID:0/010> SingleDownload.
<ID:0/010> abl.elf
<ID:0/010> xbl.elf
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I could try to lock the device, but probably no good idea?
what is strange:
when I try to install twrp recovery I'm getting message
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
but when I boot, there is no twrp recovery , only stock, nothing changed
Tronje said:
what is strange:
...
but when I boot, there is no twrp recovery , only stock, nothing changed
Click to expand...
Click to collapse
I think this is a TWRP issue then, and you can ask in the thread there...as far as I can recall with flashing TWRP, you must be quick again at first boot to NOT let the device boot fully...you need to boot directly into TWRP else the custom recovery won't stick...
Moe5508 said:
I think this is a TWRP issue then, and you can ask in the thread there...as far as I can recall with flashing TWRP, you must be quick again at first boot to NOT let the device boot fully...you need to boot directly into TWRP else the custom recovery won't stick...
Click to expand...
Click to collapse
Yes, I know. But I don't know what to do with twrp?
There seemes to be no operating system on the tab and there is no possibility to flash one from twrp. I flashed it just to see what would happen. It couldn't get worse.
What I need is a methode flashing by odin or something else with available firmware.
I only know odin. Is there something similar?
Tronje said:
I tried all available firmware versions with different odin releases. It's always the same:
<ID:0/010> Initialzation..
<ID:0/010>Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> FAIL! (Auth)
<ID:0/010>
<ID:0/010> Re-Partition operation failed.
Trying to flash twrp recovery:
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> vbmeta.img
<ID:0/007> FAIL! (Auth)
<ID:0/007>
I really really would like to know where this FAIL! (Auth) comes from. But all google search brought solutions not fitting to my situation.
Few minutes ago it just let me flash TWRP_T865_3.3.1-9.tar without grumbling - but there is no twrp recovery, only stock
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 0 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
with TWRP_T865_3.3.1-10L.tar I'm getting error message again
Click to expand...
Click to collapse
Sorry but I have to ask, why are you repartitioning anything? The only option you should touch in Odin from the options available on the left side of the screen is automatic reboot as far as I'm aware.
I would slow down and reread from the beginning.
1. Get all the correct firmware, double checking model and version numbers (is it SM-T860 or SM-T860N for example).
2. Prioritize your tasks and do them 1 at a time (get recovery working correctly, then install stock firmware, then if desired install TWRP OR root, one or the other, don't attempt to speed things up and try flashing 2 operations at once).
3. Reread what you are about to attempt before you start the process.
4. Don't try and improve on the instructions you are following, follow them exactly.
If you do the above I really can't see how you can go wrong.
Feel free to PM me any questions and if I can help I will.
Good luck brother
Sent from my [device_name] using XDA-Developers Legacy app

Categories

Resources