hi a friend of mine gave me a s6 edge stuck in boot loop as soon as i plug the usb cable.
qithout the usb cable it seems that the phone doesn't have charge in the battery.
however i tried flashing with odin different revisions of firmware and pitt files.
even if odin flashed successfully the firmware the phone keeps on having the boot loop problem
i tried to enter in the recovery mode but i have no access.
i don't know if it's a pitt file problem or what.
ps i don't know the size of the internal storage it must be 32 gb i think
There is no solution for this problem . Seems to be a hardware problem and/or totally corrupted boot partition or defective storage . Odin and Smart Switch don't help .
Related
Hi guys,
Here's what I've done.
Galaxy S2, rooted several days ago using CF-Root no problem.
Flashed Cyanogen 7.1 been using it for a couple of days, no problem.
I had the yellow triangle on boot and I bought a USB Jig thinking that would remove it.
It put the phone into Odin mode, but didn't remove the triangle.
So then, still with Cyanogen 7.1 on the phone, I powered off the phone, connected it up on Odin and used the PDA button to flash an official Samsung Kernel (Kernel_I9100XWKI4) - I remember XKWI4 was on my phone originally before I did anything. I guess this had changed with Cyanogen being installed.
Now the situation is I cannot power the phone on at all, just black screen.
Plugging in the USB jig does absolutely nothing.
If I have Odin open and connect the phone to the PC, Odin does recognise the phone.
Can anyone help me please - only had the phone a week!
Remove battery wait 10s, put battery back and either use the jig or boot while holding home vol-down and power.
i remember when i was fixing my brother galaxy s captivate after i flashed cyanogenmod i had to install google aosp drivers as opposed to samsung drivers to get odin to recognize his phone. So...try that.
Thanks for the replies guys.
Basically ODIN can see the phone.
I had managed to get the phone to boot to the Samsung screen (triangle gone as now on Stock Kernel) however it would stay on this screen forever.
I have used ODIN and flashed CWM recovery 4.0.1.5 to the phone which I can access using the 3 key combo. Obviously after doing this, the phone now boots with the triangle however it stays on the Samsung screen permentantly.
I figured I would try to re-flash Cyanogen.
Problem I now have is that Cyanogen is on the removable SD card - the phones internal 16Gb "card" is empty.
I can't get CWM to see anything on the removable SD card.
If I simply power on the phone currently, I get the Samsung flash screen with the triangle (no longer bothered about removing this, I just want the phone to work!) and it stays like this permentantly.
I can access CWM Recovery Mode, however it cannot see the removable SD card.
I can also access ODIN download mode and the phone is detected with ODIN.
I am unsure as to what Kernel is currently on the phone.
Either connect your phone to the pc while in recovery, go to mounts and storage and mount sd (or internal memory, no idea what the actual name is) and copy the rom to the internal sd card. Or use odin to start fresh again.
My device had wifi problems(not turning on), so instead of me taking a risk, i had it sent to a repair shop, and they made it much worse
This is the device as is:
when booting normally, gets stuck on "Samsung GALAXY SII GT-I9100"
when booting to recovery, boots to recovery but can't do anything because it fails to mount a ton of partitions(I can't tell whether all don't mount),
there's a lot of red text that comes up, stating the partitions failing to mount and can't find them etc.(doesn't detect ext. sd card as well)
when booting into Odin mode, boots properly into Odin mode, but all the pcs I've tried it on, with all the cables I've tried it still doesn't recognize the device :"Unknown USB Device(Device Descriptor Request Failed)", doesn't pick up in odin
(the phone also charges the battery) thought it might be useful
Please help me(tell me how i can fix it) as its been like this for the past few months, i am using this(This thread) as a last resort
Thanks in advance
My phone is MDK and used to have TWRP recovery. I was flashing a rom (EMPTY GALAXY) via TWRP and on the reboot it got in the bootloop. The symptoms are:
Can't boot into recovery, simply goes into BOOTING RECOVERY loop
Won;t even start without a cable, I put a charged battery and didn't want to start with just battery.
I reflashed the emergency MDK image via Odin with success, but still can't make the past BOOTING RECOVERY loop. I tried with PIT and without PIT file.
The only thing I can get into is the download mode
Kies 3 says says unsupported phone, while Kies2 keeps trying to connect
Kinda running out of options
I was recently given an S6 from a friend who won it but already had one. I was excited to try and root it, foolish of me to think about maybe getting more information, and I attempted a CF-Autoroot. The root claimed, in Odin 10, to have succeeded. However, it fails to boot entirely. The grey android screen that flashes the word "erasing" as the loading bar progresses during firmware reboot makes it half way before restarting. Now I can boot into Odin mode, and I can boot into recovery. USB debugging was off at the time the phone started to act up so that's a no go. I have tried multiple times in restoring it to no avail. The phone recovery says "failed to mount /efs."
Odin mode said custom and then, after using kies to attempt a restore, would fail to complete and once again get stuck on SAMSUNG screen. If I Return to Odin mode I would notice that the system went back from custom to Samsung again, though the knox counter was still at 1.
I am able to load TWRP and occasionally manage to format and tweat partitions to mount the phone in recovery but can't transfer any files.
I have access to a USB OTG device that loads via mini usb port in the device. This phone has caused me a lot of grief and I Can't think of any way to recover it. Essentially I am left with a brand new device that is worthless. Is there anyone out there with experience recovering this error.
Also I am unable to obtain the lost emergency firmware recovery number.
Thank you in advance for all the time and efforts that I hope will be provided. I have spent many days on this device trying to simply make it work.
Regards, Desmond
Hello, I am a laymen who is new to this forum,
I have a water damaged Samsung galaxy A51, it worked until my Dad tried to charge it and now it is not able to boot.
I have replaced the part of the phone on the inside with the charging port. I still can't boot it. It is stuck on the booting screen.
I am trying to flash boot it with ADB and twrp, but It is stalling out and saying "sending 'recovery'...<69440KB>" and this never goes away
recovery
I got the twrp file I tried to flash with ADB from here https://www.mediafire.com/file/nbri46sx50makis/recovery.img/file
I am also trying to flash the firmware and/or twrp with ODIN but for this one, It says "Odin protocol version error" and this does not got away either.
I have Samsung drivers on my computer.
I tried following this guide https://www.droidthunder.com/install-twrp-recovery-on-galaxy-a51/
I am pretty sure I am not using the right file, or some smaller problem like that, I am almost certain I am not using the right twrp file for Odin.
Becasue the file twrp file name in Odin is C:\Users\User\Desktop\recovery.tar.md5
I also tried these firmware files on Odin
BL_A515FXXS4DUD2_CL20899478_QB39563096_REV00_user_low_ship.tar.md5
AP_A515FXXS4DUD2_CL20899478_QB39563096_REV00_user_low_ship_meta_OS11.tar.md5
CP_A515FXXU4DUAE_CP18079213_CL20899478_QB37857056_REV00_user_low_ship.tar.md5
CSC_OMC_OWA_A515FOWA4DUB1_CL21017316_QB38149066_REV00_user_low_ship.tar.md5
any help is greatly appreciated, thank you
Take it to authorized repair service.
A friend had me look at his water damaged a51. After opening the device, I noticed corrosion. I cleaned the phone which then turned on with a green display. It was stuck on the Samsung splash screen. Nothing seemed to work, it loaded firmware from Odin successfully.
I went further to remove the screen and noticed corrosion there, It was beyond saving but the phone booted successfully without the screen attached. So I now know that a bad screen can cause the device not to boot.
I think water made its way through the under screen camera hole and damaged the lcd components.