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
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.
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
So first off, here is what i know about my device.
Samsung Galaxy S4
SCH-I545VRUGOC1
I installed TWRP because i guess i had no idea what i was doing, and locked myself out of my recovery mode, then tried to fix that by flashing the stock rom which didn't work either.
when booting this is what happens.
Recover - Nothing
Odin/Download mode - Works.
Power only - boots to black screen that says "Samsung Custom OS" then the screen turns black, blue LED comes on and it doesn't restart or turn off, it just seems to be frozen. (I expect this is because i've attempted to flash multiple times thinking the issue was my cable connection)
no idea what to do now, can't boot can't think straight since i've been at it for hours finding things on these forums but nothing seems to work through odin.
Can't download VZW Repair assistant (no online link, and phone wont recognize through my pc)
samsung kies wont recognize it either.
Help?
Need any info, ill be at my computer for a few hours trying to hash this out.
-Don't care about my data on the phone, it's replaceable.
Thanks.
Fixed it Via SmartSwitch
Was able to recover all of the aforementioned.
I have a very exaggerated problem for this device, the first time I gave Stock ROM through Download Mode, it started, I went to lunch, when I came back he had given a (Blocked Writing) error in the middle of the process, now at that moment I know how to solve this problem, but as I did not know, I tried to flash ROM again in Odin, and every time I was locking in aboot.mbn, after several attempts, several different computers, different USB cables ... different tests, now in this exact Odin crashes in Initialization, does not leave there for nothing, leave a long time it says that the device did not respond, I tried to reestablish the PIT that is the Partition Table using Odin, however it hangs anyway in initialization, I researched a lot, I tried Unbrick methods through files on SD Card, tried several Rom Stock and also tried to install a Custom Recovery, however everything fails, after all, in all cases it crashes in initialization, hey sso not only happens in a single System, then I decreed this cell phone as deceased .. the ****ing thing died, I saw in some places that they said that the problem was Hard Brick, that is to say, problem in the motherboard parts, and the solution would be change the motherboard of the entire device, but this is very expensive ...
Sansung Kies is only connecting and after a while he says that the device did not respond, if I turn the phone on, and do nothing, it goes to a Download screen only instead of the green android in the middle, a message appears talking to do Firmware Upgrade using Sansung Kies, and if I hold the buttons to enter the recovery mode, nothing happens and it's the same thing to turn it on normally, and if I hold the Download Mode buttons, it goes into Download Mode normally only in both cases Odin locks in initialization ..
Model: Samsung GT-I9192 Galaxy S4 Mini Duos
As i have mentioned in the topic i have an old phone and its brand is so rare that i don't think i can find any solution and i dont really need to revive that phone but at least i wanted to give a try on this forum so, i have just created an account well. As i have mentioned its probably hard bricked and if you ask me how it hapened actually tried to install rom and it just failed so it does stucks on boot section just flushes android writing second by second. So it would be probably a reason of why it doesn't boot into fast boot etc. so it blocks the connection between the pc and phone but at least in download mode, pc can see the phone but not as an usb-disk just sees as a cable or something, i tried to install rom but failed because of "download mode" i think and i have tried to push all of the buttons it just flushes android writing except for trying both pressing volume up and down keys (which leads download mode i think) they just appears black screen and does nothing but it does let the computer sees it as something otherwise it wont be seen as a device in other boots. So im open for all of the suggestions. Thanks for at least giving some time to read that wall of text.