Hello all, I have a rather large problem.
I erased the entire OS in my S6 and now it only powers up to the initial boot screen. I can get into download mode, but when I try to use Odin, it fails to flash the firmware. I do get the "COM4" indication, but no success with the flash. The phone is rooted, however, I cannot even access TWRP.
Has anyone on here experienced this issue or do you have any idea on how I can correct this issue?
Thank you in advance....
newman79 said:
I try to use Odin, it fails to flash the firmware. I do get the "COM4" indication, but no success with the flash.
Click to expand...
Click to collapse
please explain how Odin fails. what does it show?
try flashing the firmware twice in a row without rebooting between flashes. sometimes firmware doesn't stick after the first flash. or try Odin on a different computer.
HKSpeed said:
please explain how Odin fails. what does it show?
try flashing the firmware twice in a row without rebooting between flashes. sometimes firmware doesn't stick after the first flash. or try Odin on a different computer.
Click to expand...
Click to collapse
Have you tried using a different cable?
How about trying another USB port?
Are you sure your using the right system image?
What is your model number
Who is your provider..??
This has happened to me with my laptop. Thought I tanked my phone hardcore. Was able to flash stock tar with odin, from a different computer. Not sure why my laptop doesn't work, it just doesn't keep the connection. Can't even maintain a connection to do a data transfer when everything is working. Blah!
Thanks all for responding, I will attempt it this week sometime and give you an update.
I do not remember what Odin actually says, it has been a couple weeks now since I last attempted to fix it.
Try using both Odin 3.10.6 and 3.10.7
Related
I come to you with a very serious issue. I tried the newest cm 10.3 stable for my phone, after installing it a few times i decided it wasn't as stable as they thought it was. I wanted to switch back to my stock firmware, so i run odin, select the stock md5, hit run, it gets to the "BOOT" phase and then immediately fails. I go to check to see if i can still get into cwm, no dice. My phone is completely blank as of right now and it's not flashing correctly. Any ideas how to remedy this situation?
Can you still get into download mode? If you can try following this thread.
http://forum.xda-developers.com/showthread.php?p=40903040
baseballfanz said:
Can you still get into download mode? If you can try following this thread.
http://forum.xda-developers.com/showthread.php?p=40903040
Click to expand...
Click to collapse
unfortunately, it fails every time. Now, right as it says something about the pit and fails. I think the partition is messed up.
EDIT: Managed to find the issue. I guess it was the cable i was using to flash. Tried another really short cable and it worked fine first time no issues.
I have a Sprint Note 4 that supposedly had a custom ROM installed on but I believe the digitizer is broken. Nothing shows up on the display. I booted into DOWNLOAD MODE using Home Power and volume down and flashedN910PVPU1ANK2_N910PSPT1ANK2_SPR then N910PVPU1ANIE_N910PSPT1ANIE_SPR via ODIN It sounds like its stuck in a boot loop after both flashes, but ODIN says PASSED when it finishes. Since I can't access the screen, how can i get this flashed back to a stock rom? Any help would be greatly appreciated.
I'm confused; why flash two stock tars? Did you let the phone boot after flashing the first stock tar?
I'd suggest a factory reset in recovery, power down, Odin the factory tar of your choice and let it auto boot. You should see the phone boot into into recovery briefly on the auto boot when flashing stock tar in Odin, then fully boot. If not seeing the brief recovery, start over and try again.
I recall a YouTube video on a digitizer issue that may have been resolved. The guy had a dead spot on the digitizer. I think it only suggests a possible fix in a follow-up video the user posted. But maybe the stock tar will fix it.
why flash two stock tars?
After flashing the the first one, it just kept rebooting. That was last night. Today I flashed the older one. I'm trying install ADB on my Windows 7 desktop to enter recovery.
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
samep said:
So you can't do power down, volume up, home plus power to get to recovery?
The stock kernel won't allow adb access; permission denied when booted. Haven't tried adb on a boot loop; don't know if it lets you in or not.
Did you check the md5 for match prior to Odin? Maybe bad download?
Have you tried Odin without the sdcard installed. Bad user data or root directory data bad?
You could Odin the TWRP tar recovery and wipe everything but recovery and boot partition. Then Odin the stock tar after a power down.
Be careful not to select repartition during Odin. There was a PIT file posted but AFAIK, no one has shared a successful experience using the repartition with PIT file. Anyone correct me if I'm wrong and post a link to correct PIT file to use. Please.
Click to expand...
Click to collapse
I tried without SD card and I didn't check repartition in ODIN. The md5 matched on both.
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
samep said:
Did you try the suggestion of using TWRP to wipe partitions prior to stock tar? Look next to last paragraph of previous post.
Only other advice I can think of ATM is that the stock tars are so large, it takes a few moments to verify once selected. I leave my phone USB disconnected until Odin has verified the tar selected. Then I plug the USB and make sure I have the COM pop-up prior to start. If not, disconnect and reconnect the USB until COM is displayed. Not sure but I think there were some posters that didn't really flash the stock tar in Odin.
Click to expand...
Click to collapse
How can I use TWRP without the screen?
thanks
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
samep said:
Sorry but I got focused on the boot loop issue and lost focus on the screen issue.
No screen has me wondering how you know you're in download mode to flash Odin tar?
Starting over, I've never used kies but there was a similar problem in this thread I found with Google.
www.androidpit.com/forum/606685/phone-no-os-or-cwm-or-download-mode-please-help
Scroll down to post 10 for instructions.
Anyone else have experience or suggestion to share? Please jump in.
Click to expand...
Click to collapse
I went by feel....and the fact that Odin said COM connected. and PASSED
kevg77 said:
I went by feel....and the fact that Odin said COM connected. and PASSED
Click to expand...
Click to collapse
So you pulled the battery, pressed and held volume down, home and power buttons until it vibrated, waited to make sure it wasn't just booting, when satisfied, you pressed volume up; right?
I'd say that is a sufficient feel.
If the Odin or kies update won't take and screen is dead; with no adb access, who would know what's on the phone unless it's just not playing the right boot tone when it keeps rebooting? Problem?
I think that may be enough to take your phone back to point of sale and ask for replacement without worrying about root voiding warranty?
Did you try the Kies update?
I am familiar with the Note 3, thats how I was able to get it into Download mode by feel. I tried KIES and it said that my device is not supported. Im using the latest version of KIES. I know I'm running into an issue with the usb driver recognizing...Im on Windows 10 technical preview. thinking about trying it on an old Win7 laptop.. thanks for the advice
I got the new phone on the 10th of Jan. and while trying to root it Odin always stops at NAND Write start. I can leave it for 20 mins and never progresses past it.
I have dev mode on, OEM unlocking on, USB debugging on, Even turned off Verify apps via USB. My pc's antivirus and firewall has been disabled, and have used every usb port on my tower.
I have tried multiple files to flash, twrp 2.8.7.0 zeroftlespr. img.tar and the 2.8.6.0; Unikernel v6-920p and v6-0001; boot-of7root.tar
Im using latest Odin 3.07. The only discrepancy I've found is the Build number is LMY47x.G920PVPU3BOI1. That is a I not an L
Noone has any ideas?
Species5681 said:
Noone has any ideas?
Click to expand...
Click to collapse
If you had updated to a more current stock, then you can't use an older one. But I don't understand what you are trying to do.
Odin the latest stock. Reboot and return to download mode.
Odin a current version of unikernel, either 9 or use 8. Reboot. You are now rooted.
Odin the latest version or TWRP, 2.8.7.0.
Done. The other files you referenced are unnecessary.
The other things that usually fix Odin are to try different USB ports and cables.
No just trying to get the first root. Its a new phone.
Whenever i attempt to use Odin it always hangs at NAND write start.
Species5681 said:
Whenever i attempt to use Odin it always hangs at NAND write start.
Click to expand...
Click to collapse
As I said, try different ports and different cables.
All you need for root is to Odin Unikernel 8 or 9.
So my phone on day decided to randomly go into boot loop. Trying to use recovery to go to factory default resulted in the same bootloop.
Next, I Flashed twrp-2.6.3.1-hltetmo.tar successfully and then stock.
Here's the issue. While its connected into my PC, it gets all the way to the T-mobile sign at full brightness. But it only goes that far when it's plugged it in.
When I unplug it, it goes right back to a boot loop. And attempts to go to recovery results in it saying it's going to recovery, and then right back to boot-loop.
Now, I'm not sure which one I should be treating, the bootloop or my phone inablity to go to the flashed custom recovery.
Did you try flashing a stock ROM in Odin?
audit13 said:
Did you try flashing a stock ROM in Odin?
Click to expand...
Click to collapse
2 different stocks, same result.
Flashing was successful both time?
audit13 said:
Flashing was successful both time?
Click to expand...
Click to collapse
By successful, Odin said pass at the end and the phone restarted.
Try flashing the latest stock ROM with Odin and uncheck everyyhing except f reset time. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use the button combination to try and enter recovery.
If it still doesn't work, try flashing the latest version of TWRP and then use TWRP to perform a full wipe including the system, and try Odin again.
If it's still a no go, try flashing stock with a pit file.
audit13 said:
Try flashing the latest stock ROM with Odin and uncheck everyyhing except f reset time. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use the button combination to try and enter recovery.
If it still doesn't work, try flashing the latest version of TWRP and then use TWRP to perform a full wipe including the system, and try Odin again.
If it's still a no go, try flashing stock with a pit file.
Click to expand...
Click to collapse
I'm using the XDA pit file I found in the BootLoopRecovery Heimdal file. Since it appear you need something the
BL file, should be the stock rom or the recovery. And does the one box check ruled applies as well here?
This one to be exact.
https://forum.xda-developers.com/showthread.php?t=2545009
This has always been reliable for me when flashing Samsung phones with a stock ROM:
use the original Samsung USB cable that came with the phone;
use Odin 3.07;
use a USB 2.0 port, not USB 3.0;
use the latest stock ROM from sammobile.com.
To flash with a pit file, put the pit file in the pit box, flash the ROM in the PDA box, only things checked should be re-partition (this is selected automatically when adding a pit file), f reset time, and auto reboot.
I keep getting, "Secure Check Fail : Pit" when the re-partition button is checked and the same problem when it's not. (Odin says pass, but it gets stuck at the T-mobile sign while plugged in, and unplugged, it goes back to bootloop.)
At this point, I would conclude that the memory chip is damaged. Was the phone dropped or exposed to moisture?
Kind of feeling the same thing as it was one random reset and hasn't been the same since. Not the mention the thing has tendency to go all Gambit playing card on me, so it really might be terminal.
Ty for the help anyways, somebody probably will find their answer in this thread.
NotReallyBrain said:
So my phone on day decided to randomly go into boot loop. Trying to use recovery to go to factory default resulted in the same bootloop.
Next, I Flashed twrp-2.6.3.1-hltetmo.tar successfully and then stock.
Here's the issue. While its connected into my PC, it gets all the way to the T-mobile sign at full brightness. But it only goes that far when it's plugged it in.
When I unplug it, it goes right back to a boot loop. And attempts to go to recovery results in it saying it's going to recovery, and then right back to boot-loop.
Now, I'm not sure which one I should be treating, the bootloop or my phone inablity to go to the flashed custom recovery.
Click to expand...
Click to collapse
Flash TWRP 3.1 for hlte...that recovery is dope! It will flash the newest cm 14 and other nougat roms. It won't flash tw roms though. You'll need TWRP 2.8.7 for that.
Hi! I hope some one knows how to restore apk on a Galaxy S9 plus
I was trying to get rid of Bixby and erase some apks using adb app control, I have a backup of the apks in the computer, the problem right now it's that the phone has many photos and most of them are important , I would like to know if there is a way to avoid wipe data/ factory reset, via adb or Odin.
I'm stuck on loop after the operator logo.
It doesn't boot in safe mode.
I already have android 10 ROM but I'm afraid that if I flash it with Odin , it will wipe the user data, if there is way to Just update, or restore this files please let me know.
Thank you very much for you help.
dr.rokr said:
Hi! I hope some one knows how to restore apk on a Galaxy S9 plus
I was trying to get rid of Bixby and erase some apks using adb app control, I have a backup of the apks in the computer, the problem right now it's that the phone has many photos and most of them are important , I would like to know if there is a way to avoid wipe data/ factory reset, via adb or Odin.
I'm stuck on loop after the operator logo.
It doesn't boot in safe mode.
I already have android 10 ROM but I'm afraid that if I flash it with Odin , it will wipe the user data, if there is way to Just update, or restore this files please let me know.
Thank you
Click to expand...
Click to collapse
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.
TormentedHeart said:
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.
Click to expand...
Click to collapse
Hi! I have tried several times, and I get failure to start, the phone is detected but the flash doesn't initiate, sometimes I get this screen, sometimes it says fail .
I have installed Samsung USB drivers, from the
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
And Odin from here
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I used the original Samsung USB cable and tried the 3 USB ports in the laptop
What else can be happening?
Thank you very much!
dr.rokr said:
Hi! I have tried several times, and I get failure to start, the phone is detected but the flash doesn't initiate, sometimes I get this screen, sometimes it says fail .
I have installed Samsung USB drivers, from the
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
And Odin from here
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I used the original Samsung USB cable and tryed the 3 USB ports in the laptop
What else can be happening?
Thank you very much!
Click to expand...
Click to collapse
did you try booting into the download mode twice?
Once and then again and then start the odin.
I had to do that.
I had to flash the official firmware myself because my phone keeps crashing on the homescreen.
Didnt solve it but I did flash it properly.
bruno2030 said:
did you try booting into the download mode twice?
Once and then again and then start the odin.
I had to do that.
I had to flash the official firmware myself because my phone keeps crashing on the homescreen.
Didnt solve it but I did flash it properly.
Click to expand...
Click to collapse
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do
dr.rokr said:
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do
Click to expand...
Click to collapse
go to the recovery.
connect to the PC.
open odin.
click on "reboot to bootloader"
It should go to to download mode.
what does your download mode screen say?
When I was doing this process I tried reflashing the latest rom but that didn't solve my boot loop issue.
So I flashed an older version of the rom.
Make sure the version you download is compatible with your phone.
You have G9650ZHU9FUG2 so only roms with 9 will work.
I flashed that old version and it didn't work, phone still stuck.
Then I flashed the latest one again and then my phone worked.
I used odin from the link you posted.
Odin3 v3.13.1
actually what i would suggest is downloading/re-downloading samsung usb drivers. otherwise most phones won't respond to odin even in download mode without it
dr.rokr said:
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do
Click to expand...
Click to collapse
TormentedHeart said:
actually what i would suggest is downloading/re-downloading samsung usb drivers. otherwise most phones won't respond to odin even in download mode without it
Click to expand...
Click to collapse
Hi! I have uninstalled everything and then install the drivers again without luck
TormentedHeart said:
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.
Click to expand...
Click to collapse
Hi! Today I have successfully flashed the exact firmware that the phone had ( there is no newer) using a different laptop (it's true if the problem persist with Odin, use another laptop)
I got success message, at the very first time, and when the phone reboot, nothing , stuck as it was before, so I erased cache partition and no luck, still stuck on reboot, I have also tried repair apps , and reboot sistem now, what else should I do?
Thank you very much!
Hi! I want the community to know that using the APK adb app for Samsung it's a bad idea, after successfuly flashing the firmware and performing a factory reset several times the phone remain stucked, I downloaded about 10 different firmwares and flash them all times without an error, and the phone was bricked and stuck in boot. So I took it to the official service and nothing, still the same, then I found an external service that flash the device with a little box that they said they paid in advance for credits for using that box, it took them one full week to revive the phone, also they had to flash it several times. In conclusion, if you buy Samsung, stick with the garbage apps the throw, if you mess with the system in some way as the official technician said, the phone will be nearly unrecoverable for privacy benefits for the user. Thank you very much for the help to the community!