Related
i've read through some of the threads but i can't find anything that would help...i was installing a viperrom and now my phone wont go passed the samsung boot screen i can't access the recovery my computer wont even detect my phone how can i fix this
reboot into cwm3 and wipe data,cache ,dalvik x3 then flash rom
my guess iss that you didn't odin before you installed the rom ?
This might sound like a dumb question, but...did you turn off the phone before trying to get to recovery? As in, did you pull the battery so you could actually get the phone off?
If you can't get to recovery, did you try going in download mode and then plugging it in?
The point here is that since you can at least get the samsung logo you're not bricked...because you're still getting a response
Sent from my baked and emotionless SPH-D700
i tried to put my phone in download mode and plugged it in but the computer can't detect my phone when i open odin
just redownload the drivers
Download the 32-bit even if you're on a 64-bit computer
the 32-bit drivers seem to work better install them then restart your computer and phone then retry ODIN
You can get the Drivers in this thread....
http://forum.xda-developers.com/showthread.php?t=770388
You's go a soft brick =3
From My Samsung Epic Using TapaTalk.
ive redownloaded the software and still can't detect my phone
all im able to do right now is get my phone into download mode but odin still can't detect it...or do i only need the .tar file in the pda slot and my phone will receive once its connected ?
do you have another computer you can try?
did you try using diffrent ports to plug your phone in?
lol one of my epics still does it. Does it do this?
http://s42.photobucket.com/albums/e...on=view¤t=video-2011-02-05-07-52-00.mp4
yup trying to sell it as is since i can't fix it. Hello epic #2/ second line, and yes it stays there. No computer detect it, yes it gets into recovery no it wont load up roms lol.
odin finally detects the port but i used the tar.md5 file from the link and says hash value is invalid?
robertobmwm3 said:
odin finally detects the port but i used the tar.md5 file from the link and says hash value is invalid?
Click to expand...
Click to collapse
Is it the dk28 tar or the di18 tar?
and yes i did try all ports and like i said it says theSPH-D700-DK28-8Gb-REL.tar.md5 is invalid
correct it is the dk28
robertobmwm3 said:
and yes i did try all ports and like i said it says theSPH-D700-DK28-8Gb-REL.tar.md5 is invalid
Click to expand...
Click to collapse
You need to rename the file to-
SPH-D700-DK28-8G-REL.tar.md5
Just delete the b and everything will be fine.
hell yeah thanks alot now it says set up connection what should i do now?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-DK28-8G-REL.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..
robertobmwm3 said:
hell yeah thanks alot now it says set up connection what should i do now?
Click to expand...
Click to collapse
What says "set up connection"?
Edit: Oh, I see.
Select PDA place the .tar file in PDA Section
uncheck F.Reset time
select victory_8G_100528.pit in the pit section
connect your phone
then hit start
iSaint said:
Select PDA place the .tar file in PDA Section
uncheck F.Reset time
select victory_8G_100528.pit in the pit section
connect your phone
then hit start
Click to expand...
Click to collapse
Did you put you phone into download mode before you connected it?
Hi,
I have a Galaxy s4 I9505 on which I try to flash a new bootloader with Odin, so a tar file containg only aboot.mbn, sbl1,sbl2, sbl3,mpn,tz.
I'm pretty sur that the current one is a 4.2.2 and I want to upgrade to a 5.0.1.
So I put my phone on USB debugging mode, boot in download mode, select the bootloader.tar (which is compatible with my phone) in the BL field of ODIN which I launched as admin, , connect my phone which is correctly detected by Odin and then start to flash. The problem is that it always fails with this message:
Code:
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have the correct samsung drivers, I tried on different PC (windows 7/10), different USB ports and USB data cables, but I have always the same error message. The only thing that I did not try is to flash with the original samsung USB cable which I read in other forums that could be the cause.
I also say that ODIN works with no problem on the same phone when I flash any stock ROM (downgrade, upgrade) or any recovery file, so that's why I don't think that the cable could be the reason.
I'm not really sure if my bootloader is unlocked but I guess it is otherwise flash would not be possible, but I have no way to see of it is unlocked or not.
I don't see what else could be the reason, write access persmission?
Thx.
try older Odin version....
mbaier said:
try older Odin version....
Click to expand...
Click to collapse
Hi, thx but I should have added also that in my first post, I think I tried every possible version of Odin from 1.83 to 3.12, no luck...
I know you said you have tried it on different PCs and USB ports, but does this mean you also tried the rear ports?
I know most PCs nowadays have front ports for convenience so maybe you haven't tried that option. Rear vs front does seem to make a difference.
Pwnycorn said:
I know you said you have tried it on different PCs and USB ports, but does this mean you also tried the rear ports?
I know most PCs nowadays have front ports for convenience so maybe you haven't tried that option. Rear vs front does seem to make a difference.
Click to expand...
Click to collapse
Yes I did
Try to flash the entire stock Rom from Sammobile.com rather than just the bootloader.
You confirmed the model # in download mode?
audit13 said:
Try to flash the entire stock Rom from Sammobile.com rather than just the bootloader.
Click to expand...
Click to collapse
already done also..it starts by flashing aboot.mbn and so fails exactly the same way..
You confirmed the model # in download mode?
Click to expand...
Click to collapse
Sorry, what do you mean by that? I don't see anything to confirm.
Boot into download mode. Is the model # gt-i9505?
Since the aboot.mbn is not flashing because the ROM is not for the phone, the bootloader in the phone is newer than the bootloader in the ROM, or you need to use the original USB cables.
hi all, please help me my note 3 sm n900 stuck at note 3 logo, only download mode works, recovery mode not working. when i try to flash stock rom via odin its showing following log
leaves cs..
odin v.3 engine
file analysis
setup connection
initializing....
the its taking ages not going further:crying:
please help
it went into this state automatically i have not done anything, suddenly it was powered off then this problem occurred, btw its charging & showing battery % as well....
What are you flashing ??
JJEgan said:
What are you flashing ??
Click to expand...
Click to collapse
i was flashing nothing suddenly my fone get switched off then i tried to switched on so its not booting, odin is recognizing fone but fail to flash anything its giving error in the end something like " (pass 0/ failed 1)
<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..
Try different USB cables and USB ports.
nickomy said:
<ID:0/003> Initialzation..
Click to expand...
Click to collapse
Alots reason if stuck like this and some solution is weird but works
Wrong firmware, download the right one.
Not pull out battery and reinsert before flash with odin(better takeout sim and SD card, yeah this weird)
Cable problem
PC port problem(changing to others port)
Using wrong version, odin(better using latest)
Odin problem/bug in PC(because old version alots problem, solution is to close odin and open again then flash ROM
Another way, just flash TWRP, backup important file using TWRP then flash custom ROM
Try it & Goodluck.
audit13 said:
Try different USB cables and USB ports.
Click to expand...
Click to collapse
Tried with different usb cables & different usb ports but still no luck, read somewhere on xda that. The problem is with your device's hard drive which you may define as system storage . This is a very common issue with Samsung devices . Don't worry it's easy to fix . If you have warranty then go to Service center and if you don't have warranty then go to a service professional and ask him to replace your device's hard drive which contains ram and emcc in a single chip. If you face no base band issue then simply flash efs via odin that will resolve the imei issue
download menu status is
ODIN MODE
Product Name : SM-N900
Current Binary: Samsung Official
System Status: Official
Reactivation Lock (KK): OFF
Secure Download : Enabled
KNOX WARRENTY VOID : 1
RP SWREV : A4
Odin readings are
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900XXUEBOC4_N900ODDEBOB2_N900DDUEBOB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Does a com port get assigned to the phone in Odin?
audit13 said:
Does a com port get assigned to the phone in Odin?
Click to expand...
Click to collapse
some times yes some times no, then I'd to take out the battery n reinsert to recognize by odin. Kies is not recognizing at all. Thanks for your prompt replies really appreciate it:fingers-crossed:
It's definitely a problem if the phone losses USB connectivity.
It's possible the usb port on the phone is defective?
audit13 said:
It's definitely a problem if the phone losses USB connectivity.
It's possible the usb port on the phone is defective?
Click to expand...
Click to collapse
but its charging both from wall socket n laptop as well
There are 4 wires in a usb cable: 2 for data, 2 for power.
It's possible for a phone to charge and not transfer data.
audit13 said:
There are 4 wires in a usb cable: 2 for data, 2 for power.
It's possible for a phone to charge and not transfer data.
Click to expand...
Click to collapse
Ok i'll recheck n confirm, btw alot of thanks for youe help:fingers-crossed::good:
how much is the possibility that my fone hard drive got corrupted as its not going into recovery. I'm in doubt bcz my fone had required factory reset for no reason about once in a month
Your phone does not have a hard drive .
But its possible that the memory has a corrupt section .
But your symptoms are more likely an app causing the problem .
Thanks to all for their help, problem solved as it was connectivity issue i have tried on another pc it worked like a charm. Cheers to all
Looking for some direction if possible. I have a SM-T580, with no ROM, and am currently unable to flash a ROM via ODIN. I have re-installled TWRP and the verity patch but the device will not boot into TWRP/ recovery to install Lineage OS, or any other ROM for that matter. I attempted to re-pack Lineage as a .tar so that I could try to flash it but ODIN crashed when I tried it. Since my device had already updated to Oreo prior to it failing, I am not been able to reinstall a previous version, (I tried).
Currently am stuck at a flickering Logo screen., but only if USB is plugged in. If not plugged in, no boot...
{
"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 message in the top right corner says "Recovery is not SEANDROID Enforcing JTAG lock is not set". I can boot into download mode, just not sure what to flash at this point.
I have been able to restore my t580 back to nougat. Try autoroot here https://forum.xda-developers.com/galaxy-tab-a/how-to/root-t3674409
It will force you to facotry reset your device. The official twrp recovery isn't compatible with the Oreo 8.1 Update. Try flashing followmsi's newest twrp recovery from here https://drive.google.com/drive/mobi...-mGf0b_oQ69wirVcgd-okF-ps?sort=13&direction=a
In Odin (use 3.13.x) untick autoreboot or you will not be able to boot into recovery. After you flash twrp, press vol- and Power. When the screen turns black, immediately switch to home button and vol + and power. When you are succeed at booting twerp, you must format the data partition to remove encryption and reboot again to twerp to be able to use the data partition. Wipe all and install your favourite Rom. Try also to Flash newest followmsi Kernel. You can find it on the link above. I hope you find this post helpful.
In a similar situation. How do you just put it back to stock? I used the twrp, but I then tried to flash the latest stock in odin, and it failed.
another try.
Well my husband managed totally kill my T580 so I gave it a break yesterday. I am going to try @AndroidJail's suggestion below. I will let you know how it turns out. Wish me luck!:fingers-crossed:
Flutterfly said:
Well my husband managed totally kill my T580 so I gave it a break yesterday. I am going to try @AndroidJail's suggestion below. I will let you know how it turns out. Wish me luck!:fingers-crossed:
Click to expand...
Click to collapse
Good luck!
Wish me luck too, I have the same problem as above. Will only show battery icon and download mode if USB is plugged in.
When trying to flash in Odin it just hangs on "Inilitilzation" and nothing ever happens.
redheelerdog said:
Good luck!
Wish me luck too, I have the same problem as above. Will only show battery icon and download mode if USB is plugged in.
When trying to flash in Odin it just hangs on "Inilitilzation" and nothing ever happens.
Click to expand...
Click to collapse
That's exactly what mine was doing. I was able to flash the newest TWRP file that androidjail points to but cannot get it to boot into TWRP. I don't know where to go from there.....
Flutterfly said:
Well my husband managed totally kill my T580 so I gave it a break yesterday. I am going to try @AndroidJail's suggestion below. I will let you know how it turns out. Wish me luck!:fingers-crossed:
Click to expand...
Click to collapse
Start from scratch and download a Nougat version of Android from Sammobile and Odin version 3.13.1. Boot into download mode and plug into PC after starting Odin. In this version of Odin you must unzip the tar file and select ONLY the AP and BL files. If you didn't see "Added" appear in the Odin log box when you plugged in the tablet, then you need to check the Samsung-Usb-Driver-v1.5.61.0 is installed on the PC. This install will replace TWRP with the stock recovery and the tablet should boot the stock ROM. If this works, it means your tablet is OK and we can proceed with installing TWRP and any custom ROM.
edit: There is nothing wrong with AndroidJail's advice. I just advise taking it one step at a time. IOW, get a stock ROM working first to make sure there isn't a hardware problem.
Edit: BTW, you don't have to bother setting up the stock ROM. Just want to make sure it boots OK before proceeding with TWRP and custom ROM.
follow-up question regarding T-580
lewmur said:
Start from scratch and download a Nougat version of Android from Sammobile and Odin version 3.13.1. Boot into download mode and plug into PC after starting Odin. In this version of Odin you must unzip the tar file and select ONLY the AP and BL files. If you didn't see "Added" appear in the Odin log box when you plugged in the tablet, then you need to check the Samsung-Usb-Driver-v1.5.61.0 is installed on the PC. This install will replace TWRP with the stock recovery and the tablet should boot the stock ROM. If this works, it means your tablet is OK and we can proceed with installing TWRP and any custom ROM.
edit: There is nothing wrong with AndroidJail's advice. I just advise taking it one step at a time. IOW, get a stock ROM working first to make sure there isn't a hardware problem.
Edit: BTW, you don't have to bother setting up the stock ROM. Just want to make sure it boots OK before proceeding with TWRP and custom ROM.
Click to expand...
Click to collapse
So I have new information! I was able to Flash the AP and CSC file of the 8.1.0 firmware but when I attempt to flash the BL file, it fails.
This is he error I get:
<ID:0/006> 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/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 5 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> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestions? I feel like I'm so close!!
In the same situation
In the same situation.
Upgraded to 8.1, installed Ashyx's version of TWRP.
Was attempting to remove encryption so i could access internal storage and SD card (and install LineageOS 15.1) when I messed up something with the partitions probably wiped out something important, TWRP gave a warning that there's no OS.
Now can't seem to flash anything through Odin (Using 3.13.1).
Tried the stock 8.1, doesn't work, stock BL, AP, CSC, nothing.
"can't open specified line", sometimes just freezes and fails.
Cannot get to recovery, cannot reflash TWRP.
Would love some help.
This is what I get when I try to flash CSC of 8.1:
<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.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 75 M
<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> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Any luck?
MajorBoobage said:
In the same situation.
Upgraded to 8.1, installed Ashyx's version of TWRP.
Was attempting to remove encryption so i could access internal storage and SD card (and install LineageOS 15.1) when I messed up something with the partitions probably wiped out something important, TWRP gave a warning that there's no OS.
Now can't seem to flash anything through Odin (Using 3.13.1).
Tried the stock 8.1, doesn't work, stock BL, AP, CSC, nothing.
"can't open specified line", sometimes just freezes and fails.
Cannot get to recovery, cannot reflash TWRP.
Would love some help.
This is what I get when I try to flash CSC of 8.1:
<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.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 75 M
<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> Can't open the specified file. (Line: 1892)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Were you ever able to get your device working? I
was not, but just recently it was suggested that the wrong Bootloader REV could be causing my issue. Thought I would share with you.
has anyone made any progress regarding this issue. TWRP reboot fails every time I try and I have to flash to OREO 8.1 to restore device. All attempts to downgrade to Android 7 or 6 fail as well.
SM-T580N (canada)
BMcDoh said:
has anyone made any progress regarding this issue. TWRP reboot fails every time I try and I have to flash to OREO 8.1 to restore device. All attempts to downgrade to Android 7 or 6 fail as well.
SM-T580N (canada)
Click to expand...
Click to collapse
Yes, finally. Your issue seems to be the Bootloader
Casper Young said:
Yes, finally. Your issue seems to be the Bootloader
Click to expand...
Click to collapse
How did you get yours working? Which files and bootloader?
Thanks
There are 3 FRP Recovery Locks
redheelerdog said:
How did you get yours working? Which files and bootloader?
Thanks
Click to expand...
Click to collapse
This may be difficult to explain. I've been scouring all through XDA searching for an answer to a second issue and this apparently is a third. So here I need to back up. My first issue was after I rooted my T580. I was Beta testing and on a search and destroy mission with a root method that worked well, yet had a few bugs which I was correcting at the time. I had already provided a fix for the Samsung Security Agent for people to take care of the issue where the device ask users to reboot. And I have noticed it often doesn't charge while in use. In the Developer Settings the USB Configuration does not move from MTP to Charge, this one seemed a Settings issue that I noticed on my tab that no-one else mentioned. I also ran into a difficulty with going to Download Mode and this was yielding different issues. No Recovery was one of them. Others were mentioning a redirection to a locked FRP. I tried to replicate the issue only to be locked into Download Mode and couldn't flash nor leave.
I got out of that by holding the power, home and both volumes down until the device shut off and reset (about 20 seconds). After this I booted up again and the Device Manager was giving me a notification of some security threat asking for a restart. This was the Security Agent again. I turned it off and tried to reboot to recovery. I got redirected to a blue page with red letters at the top left saying, "Custom Binaries Blocked by FRP Lock". The symtoms are: Bootlooping, won't load past Logo screen and often flickers. Download mode is accessable but Odin3 is not flashing official firmware. Worst of all? Absolutely no Recovery. I flashed this in: SM-T580 Binary 4 FRP Unlock.
https://drive.google.com/drive/folders/1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5?usp=sharing
Incorrect or invalid files are the reason for this happening which overload the Binaries so they're blocked! Now this got me out of FRP Lock which ended my personal issue. Here's some things I picked up along the way that are useful,
This one clears Knox:
https://drive.google.com/file/d/1EolYe9auY9jslYSpSgHoon_YB00D2noV/view?usp=sharing
Here's an updated TWRP: (For the T580)
https://drive.google.com/file/d/125ucHgjdNYqs54k2EmiwJZY_KxTdsTMi/view?usp=sharing
And here's a patched Odin3.13B because the normal one has some difficulties:
https://drive.google.com/file/d/13c0uDH99PcUzO0cnHuyBKy2e-b_I1W53/view?usp=sharing
The second issue is with another tablet but very similar. having all the same symptoms but the recovery redirect doesn't say Custom Binaries blocked ect. It said:
Odin Mode
Download Speed
Fast
PRODUCT NAME: SM-T580
CURRENT BINARY: Custom
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 1 (0x0500)
Frp is enabled.
Ignore pit partition
So far I can do nothing to correct the difficulty of the second FRP Lock. And here appears to be a third FRP Lock. This is unusual! It is not advisable to downgrade to 7.1 because of the differences in partitioning. And it's a serious consideration that whomever had the device before may have tried because it referrs to the pit files. I've tried many different methods, OEM Unlock, flashed the bootloader in, the BL, the BL and the AP, the 3 file (BL, AP & CSC) and the 4 file (BL, AP & Home CSC) and got nothing! But fixing the partition or pit files wasn't one of the methods.
Try holding Power+ Vol up AND vol down + home button (touch the screen with entire thumb over the charging port) all at once. When you see the writing popup let go of power but keep the other buttons pressed. Hope it helps. Worked for me
S.S
So Casper, just to confirm, you are able to load this TWRP on your T580 with 8.1? I have a rooted P580 with Samsung 8.1 and have never managed to get TWRP to load - I get a black screen/can't boot and have to install vanilla all over again to get past that. To my knowledge after searching everywhere there has not been a fix as of this date (9/30/19), and lots of people want that fix so they can load the adoptable storage patch zip and get past the 16GB storage limitation - that is my impetus as well - bought a quality high speed microSD for that purpose. Put many hours into already this so am reluctant to try again unless someone has verified that this TWRP will load under 8.1 on a 580. I assume that the T580 and P580 are TWRP identical. My FRP is unlocked so I don't share that part of your problem.
Having similar issue with my t580. Can boot to download mode but nothing else. Can get to splash screen if I leave download mode, but tablet sits there. If I plug it into wall charger I have grey battery icon with lightning bolt. I have tried flashing many combination files and BL/AP/CSC files with no luck. Odin(v3.13 and modded) hang at either setup connection or initialization. Trying to install TWRP does the same. I'm about ready to use this thing as a small boogie board. I have some images I'll post
See attached images. Also, screen will "flicker" aometimes. Not sure if that has to do with low battery or what. But when it is flickering, Odin seems to get to sboot. Well it did once. At that point FRP lock was showing off in Odin. But device would not boot back to download mode til I charged it for about 10min. Once I booted back to download mode, FRP was back on.
Well, I had a major problem with my T-580, no OS, unable to boot, tried 3 PCs and 2 laptops with no luck. Odin would just hang and that just sucked ass. (device battery had gone completely dead, that was the only thing that put me in the boot loop)
Posted questions in this thread and started another with no luck. https://forum.xda-developers.com/ga...italzation-t3870557/post78234744#post78234744
Damn near took a hammer to the MF several times but I didn't. :laugh:
I got an email last week about some responses to this thread and started reading, in the past I had taken out the 64MB micro SD and tried to load some files on it that way but that never worked.
I picked up the T-580 a couple of days ago, plugged it in (totally dead), let it charge for maybe 10mins.
I held the power, vol +-, and home buttons... and low and behold, the SOB booted up into the normal home screen!
I really could not believe it started right up without doing anything.
The 64MB micro SD was out of the slot when all this went on, so I think maybe all the BS with Odin and OS locks had something to do with the micro SD? Not sure, but I am glad I did not smash the MF.
Probably won't help anyone with this post but I wanted to share my latest experience with a rooted T-580. I would probably not root these devices again based on this **** ass experience, but I am glad I got the thing back.
redheelerdog said:
Well, I had a major problem with my T-580, no OS, unable to boot, tried 3 PCs and 2 laptops with no luck. Odin would just hang and that just sucked ass. (device battery had gone completely dead, that was the only thing that put me in the boot loop)
Posted questions in this thread and started another with no luck. https://forum.xda-developers.com/ga...italzation-t3870557/post78234744#post78234744
Damn near took a hammer to the MF several times but I didn't. :laugh:
I got an email last week about some responses to this thread and started reading, in the past I had taken out the 64MB micro SD and tried to load some files on it that way but that never worked.
I picked up the T-580 a couple of days ago, plugged it in (totally dead), let it charge for maybe 10mins.
I held the power, vol +-, and home buttons... and low and behold, the SOB booted up into the normal home screen!
I really could not believe it started right up without doing anything.
The 64MB micro SD was out of the slot when all this went on, so I think maybe all the BS with Odin and OS locks had something to do with the micro SD? Not sure, but I am glad I did not smash the MF.
Probably won't help anyone with this post but I wanted to share my latest experience with a rooted T-580. I would probably not root these devices again based on this **** ass experience, but I am glad I got the thing back.
Click to expand...
Click to collapse
You should name it Lazarus....?
Hi guys,
so my mobile is now going into download mode
if you want to see the full story of how my mobile bricked you can check my previous question.
https://forum.xda-developers.com/s7-edge/help/s7-edge-sm-g935fd-completely-dead-hard-t4077485
as of now i can go into the download mode but when i try to flash the 7.0 Nougat version rom with it (the version which it had installed when it got bricked)
it starts the process but then it fails below is the log details :
<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.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4143 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if i just turn on the mobile its says something like "an error occcured while updating the software please connect to smart switch"
if anyone has any idea please advice , as i didnt get any response on my previous question as well
and yes i searched online already and but the methods i found didnt help
Thanks in advance.
abdullah61129 said:
Hi guys,
so my mobile is now going into download mode
if you want to see the full story of how my mobile bricked you can check my previous question.
https://forum.xda-developers.com/s7-edge/help/s7-edge-sm-g935fd-completely-dead-hard-t4077485
as of now i can go into the download mode but when i try to flash the 7.0 Nougat version rom with it (the version which it had installed when it got bricked)
it starts the process but then it fails below is the log details :
<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.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4143 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if i just turn on the mobile its says something like "an error occcured while updating the software please connect to smart switch"
if anyone has any idea please advice , as i didnt get any response on my previous question as well
and yes i searched online already and but the methods i found didnt help
Thanks in advance.
Click to expand...
Click to collapse
Did you try connecting the phone to smart switch and try recovering from there?
Sent from my SM-G985F using Tapatalk
abdullah61129 said:
Hi guys,
so my mobile is now going into download mode
if you want to see the full story of how my mobile bricked you can check my previous question.
https://forum.xda-developers.com/s7-edge/help/s7-edge-sm-g935fd-completely-dead-hard-t4077485
as of now i can go into the download mode but when i try to flash the 7.0 Nougat version rom with it (the version which it had installed when it got bricked)
it starts the process but then it fails below is the log details :
<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.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4143 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
if i just turn on the mobile its says something like "an error occcured while updating the software please connect to smart switch"
if anyone has any idea please advice , as i didnt get any response on my previous question as well
and yes i searched online already and but the methods i found didnt help
Thanks in advance.
Click to expand...
Click to collapse
This looks more like emmc chip (your phone's storage chip) error, you already lost all your data and if its a hardware issue then i doubt software reflash could fix it, but do tell me what was your current firmware number which was in your phone before all this , also send a pic of download mode..
Also what screen stripes you were talking about in your earlier thread? Send a screenshot of them too (looks more like a hardware problem too)
If you can't post images here on xda, just upload to an external site like imgur and send your pic link here ..
Per my best knowledge, smart switch doesnot support emergency recovery anymore (but if it still supports in some old versions or it works - then please do try that too) .. Good luck
Sent from my S7 Edge using XDA Labs
vash_h said:
Did you try connecting the phone to smart switch and try recovering from there?
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
havent tried that since i am afraid if i do that i might lose the data , maybe it might format and put the latest firmware in it
shah22 said:
This looks more like emmc chip (your phone's storage chip) error, you already lost all your data and if its a hardware issue then i doubt software reflash could fix it, but do tell me what was your current firmware number which was in your phone before all this , also send a pic of download mode..
Also what screen stripes you were talking about in your earlier thread? Send a screenshot of them too (looks more like a hardware problem too)
If you can't post images here on xda, just upload to an external site like imgur and send your pic link here ..
Per my best knowledge, smart switch doesnot support emergency recovery anymore (but if it still supports in some old versions or it works - then please do try that too) .. Good luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
My firmware was Nougat 7.0 . S7 EDGE SM-G935FD
I will try to put the images on the site you mentioned and give the link here
i didnt try the smart switch as i was afraid it might automatically format it and put the latest firmware , i hope the emmc ship is still recoverable as thats my only hope if firmware flashing doesnt help
shah22 said:
This looks more like emmc chip (your phone's storage chip) error, you already lost all your data and if its a hardware issue then i doubt software reflash could fix it, but do tell me what was your current firmware number which was in your phone before all this , also send a pic of download mode..
Also what screen stripes you were talking about in your earlier thread? Send a screenshot of them too (looks more like a hardware problem too)
If you can't post images here on xda, just upload to an external site like imgur and send your pic link here ..
Per my best knowledge, smart switch doesnot support emergency recovery anymore (but if it still supports in some old versions or it works - then please do try that too) .. Good luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
https://www.dropbox.com/sh/w1d8bdoiyaw2air/AAAZSWRYgXDAqRqWJRIz1ETEa?dl=0
this is the link to both the download mode pic and the screen pic
although the screen doesnt scramble now it can go to download mode
if i try to flash in odin i get the error at recovery.img
abdullah61129 said:
https://www.dropbox.com/sh/w1d8bdoiyaw2air/AAAZSWRYgXDAqRqWJRIz1ETEa?dl=0
this is the link to both the download mode pic and the screen pic
although the screen doesnt scramble now it can go to download mode
if i try to flash in odin i get the error at recovery.img
Click to expand...
Click to collapse
Sorry your problem looks like a hardware error.. and i don't think you can recover your data any more
Sent from my S7 Edge using XDA Labs
shah22 said:
Sorry your problem looks like a hardware error.. and i don't think you can recover your data any more
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
that sucks man
what about the emmc chip , would it be possible to do a chip off recovery?
what i dont understand is that if its a hardware issue then why does it even turn on and allow me to go to the recovery mode
abdullah61129 said:
that sucks man
what about the emmc chip , would it be possible to do a chip off recovery?
what i dont understand is that if its a hardware issue then why does it even turn on and allow me to go to the recovery mode
Click to expand...
Click to collapse
What was the last firmware present on your phone. Hardware damage is always tricky.. sometimes it allows phone to boot with weird things going on before completely failing..
I can see that your bootloader number is 2 , i will give you the combination rom, try flashing that in odin
Be warned that all your data in your phone is already lost, at this point your only goal is to make your phone working again, thats where i am helping..
Combination u2 rom : https://drive.google.com/file/d/1JKDiV3LmqUt8GLlOLnmZ6Xsqxn-Hpv9d/view?usp=drivesdk
Flash it in odin 3.14.4 and untick auto reboot in odin options, if flashing is successful .. ur phone will still be in download mode.. hold vol down + home + pwr button to force reboot and when phone starts rebooting( screen goes black ) immediately change holding from vol down to vol up+ home + pwr buttons , trick here is to force reboot to recovery directly from download mode without booting combination rom, do a factory data wipe in combination recovery.. then clear cache and then try reboot to combination rom..
If you could boot into combination rom, run some hardware tests.. and report back, if everything goes good, we can try flashing the last stock firmware that was present on your device, Good luck
Sent from my S7 Edge using XDA Labs
shah22 said:
What was the last firmware present on your phone. Hardware damage is always tricky.. sometimes it allows phone to boot with weird things going on before completely failing..
I can see that your bootloader number is 2 , i will give you the combination rom, try flashing that in odin
Be warned that all your data in your phone is already lost, at this point your only goal is to make your phone working again, thats where i am helping..
Combination u2 rom : https://drive.google.com/file/d/1JKDiV3LmqUt8GLlOLnmZ6Xsqxn-Hpv9d/view?usp=drivesdk
Flash it in odin 3.14.4 and untick auto reboot in odin options, if flashing is successful .. ur phone will still be in download mode.. hold vol down + home + pwr button to force reboot and when phone starts rebooting( screen goes black ) immediately change holding from vol down to vol up+ home + pwr buttons , trick here is to force reboot to recovery directly from download mode without booting combination rom, do a factory data wipe in combination recovery.. then clear cache and then try reboot to combination rom..
If you could boot into combination rom, run some hardware tests.. and report back, if everything goes good, we can try flashing the last stock firmware that was present on your device, Good luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I honestly dont remember the exact firmware details, all i know is that it was Nougat 7.0 and an update was available for a long time but i didnt update as i had no space (like only 800 or 900mb was left)
I see, so the data is lost.
Soo this combination U2 rom , it will replace the rom which was previously installed?
Sorry i am just trying to learn more about this combination U2 rom as i have never read about it
Thanks
shah22 said:
What was the last firmware present on your phone. Hardware damage is always tricky.. sometimes it allows phone to boot with weird things going on before completely failing..
I can see that your bootloader number is 2 , i will give you the combination rom, try flashing that in odin
Be warned that all your data in your phone is already lost, at this point your only goal is to make your phone working again, thats where i am helping..
Combination u2 rom : https://drive.google.com/file/d/1JKDiV3LmqUt8GLlOLnmZ6Xsqxn-Hpv9d/view?usp=drivesdk
Flash it in odin 3.14.4 and untick auto reboot in odin options, if flashing is successful .. ur phone will still be in download mode.. hold vol down + home + pwr button to force reboot and when phone starts rebooting( screen goes black ) immediately change holding from vol down to vol up+ home + pwr buttons , trick here is to force reboot to recovery directly from download mode without booting combination rom, do a factory data wipe in combination recovery.. then clear cache and then try reboot to combination rom..
If you could boot into combination rom, run some hardware tests.. and report back, if everything goes good, we can try flashing the last stock firmware that was present on your device, Good luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
does flashing a combinatiom rom usually make a mobile lose its data?
what if theres still a chance to recover the data
abdullah61129 said:
I honestly dont remember the exact firmware details, all i know is that it was Nougat 7.0 and an update was available for a long time but i didnt update as i had no space (like only 800 or 900mb was left)
I see, so the data is lost.
Soo this combination U2 rom , it will replace the rom which was previously installed?
Sorry i am just trying to learn more about this combination U2 rom as i have never read about it
Thanks
Click to expand...
Click to collapse
It will just help to unbrick your device (provided that it gets flashed successfully in odin first)
Just follow my steps in above post after (if) odin could flash successfully.
Sent from my S7 Edge using XDA Labs
---------- Post added at 06:28 PM ---------- Previous post was at 06:19 PM ----------
abdullah61129 said:
does flashing a combinatiom rom usually make a mobile lose its data?
what if theres still a chance to recover the data
Click to expand...
Click to collapse
You tried flashing already..
Flashing anything has the risk to lose all your data if you have no backup before ..
And flashing with HOME CSC doesn't erases data..
But as you said you tried flashing various stock firmwares, but odin failed in the middle..
So yeah, i think your data is already lost
But if it was that important , i seen some android programs which can recover deleted files from phone but they are mostly paid and also phone should be in working condition..
Also there are professional data recovery companies who would take in your phone and pull its memory chip apart and use their special hardware on that chip to extract anything they could.. but there is no guarantee that you will get back any important data from it and their cost is huge for this process..
Thats why its recommended to always keep a back up of all your data
Sent from my S7 Edge using XDA Labs
shah22 said:
It will just help to unbrick your device (provided that it gets flashed successfully in odin first)
Just follow my steps in above post after (if) odin could flash successfully.
Sent from my S7 Edge using XDA Labs
---------- Post added at 06:28 PM ---------- Previous post was at 06:19 PM ----------
You tried flashing already..
Flashing anything has the risk to lose all your data if you have no backup before ..
And flashing with HOME CSC doesn't erases data..
But as you said you tried flashing various stock firmwares, but odin failed in the middle..
So yeah, i think your data is already lost
But if it was that important , i seen some android programs which can recover deleted files from phone but they are mostly paid and also phone should be in working condition..
Also there are professional data recovery companies who would take in your phone and pull its memory chip apart and use their special hardware on that chip to extract anything they could.. but there is no guarantee that you will get back any important data from it and their cost is huge for this process..
Thats why its recommended to always keep a back up of all your data
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
yes i tried flashing the stock but that recovery.img error occurs.
i have always read people say that you lose data after flashing a stock rom which isnt true as i recently flashed Note 3 Neo SM N7502 and Note 3 SM-N9005
both with stock rom and all the data, apps and contacts were intact.
i only used the AP files on both and nothing else
but i have never flashed a combination rom so was curious if the data is erased if that is flashed.
Yes, i have seen several apps like wondershare/dr fone which can recover the data but the problem is they either require root or say if unrooted the USB debugging has to be on , in my case i never rooted nor turned on the USB debugging mode as i never needed it.
i live in dubai , currently i am searching for someone who can professional pull out all the data from the chip but due to the coronavirus lockdown all shops are shut and even online technician arent active.
Yes its better to always backup the data, it happened so suddenly as i mentioned in my first post it automatically went blank when i plugged in my usb
anyhow i will try to flash the combination rom and let you know
Thanks
abdullah61129 said:
yes i tried flashing the stock but that recovery.img error occurs.
i have always read people say that you lose data after flashing a stock rom which isnt true as i recently flashed Note 3 Neo SM N7502 and Note 3 SM-N9005
both with stock rom and all the data, apps and contacts were intact.
i only used the AP files on both and nothing else
but i have never flashed a combination rom so was curious if the data is erased if that is flashed.
Yes, i have seen several apps like wondershare/dr fone which can recover the data but the problem is they either require root or say if unrooted the USB debugging has to be on , in my case i never rooted nor turned on the USB debugging mode as i never needed it.
i live in dubai , currently i am searching for someone who can professional pull out all the data from the chip but due to the coronavirus lockdown all shops are shut and even online technician arent active.
Yes its better to always backup the data, it happened so suddenly as i mentioned in my first post it automatically went blank when i plugged in my usb
anyhow i will try to flash the combination rom and let you know
Thanks
Click to expand...
Click to collapse
You cannot compare a note 3 with s7 series generation lol
And yes , flashing a stock rom wipes all data if you DON'T choose HOME _ CSC in csc box..
Flashing with home_csc won't cause data loss but its akin to a dirty flash .. causes problems and is there for upgrading android os without data loss, and its not generally a good thing to NOT wipe data and factory reset after flashing as it causes problems..
IF YOU INTEND TO DO A PROFESSIONAL RECOVERY OF YOUR DATA DON'T FLASH ANYTHING ANYMORE AS IT WILL FURTHER MAKE IT DIFFICULT TO RETRIEVE !
WARNING : combination rom would wipe all your data, so be warned if you flash it, it would be even more difficult to recover data ..
Sent from my S7 Edge using XDA Labs
shah22 said:
You cannot compare a note 3 with s7 series generation lol
And yes , flashing a stock rom wipes all data if you DON'T choose HOME _ CSC in csc box..
Flashing with home_csc won't cause data loss but its akin to a dirty flash .. causes problems and is there for upgrading android os without data loss, and its not generally a good thing to NOT wipe data and factory reset after flashing as it causes problems..
IF YOU INTEND TO DO A PROFESSIONAL RECOVERY OF YOUR DATA DON'T FLASH ANYTHING ANYMORE AS IT WILL FURTHER MAKE IT DIFFICULT TO RETRIEVE !
WARNING : combination rom would wipe all your data, so be warned if you flash it, it would be even more difficult to recover data ..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
hmm i see,
well i guess i will just wait for a professional recovery service then, if they cant recover then i will just use this combination rom and try and fix the mobile so its usable again