[Q] Need help fixing soft bricked phone - Android Q&A, Help & Troubleshooting

:highfive: Hi !
I run Windows 7, Samsung Galaxy S7390G (rooted) originally under stock rom (because there's no custom rom for my phone :crying:,) and without any custom recovery (because there's no custom recovery for my phone)
I had problem with my internal SD card, I posted on forums, but not this one, and had no help, so I decided to restock my phone.
I used Odin, because I failed with Heimdall, and Odin began flashing my Rom, but gave me a red "fail" message error.
I tried the SamMobile's stock rom for my device, S7390. I tried several ones, always S7390, and Odin failed each time, and stuck me in half-bricked state.
Note: My old computer is with Linux Mint, but I can't use it for now, but I can make a live USB with a Linux distro under the Window computer that I use now if it helps.
I have sometimes some trouble with the USB drivers, and I have been forced to reinstall them many times, trying different packages. For now, but I don't know if it will last, Odin is able to recognize my phone, but each time I try to flash a Rom, it fails. I tried another USB cable, and other USB ports, same thing...
I don't know what to do? I read that there was solution with the adb command, I'll read about it, because I have poor knowledge, but I despair
Even if I know it can be repair, but I can't do it! :crying:
I can only access to download mode.
Please, help a poor despaired French girl. Thank you very much.

Nobody?
None to help? :crying:

Same Problem

No worrys darling you can just go to recovery mode of your phone and select wipe factory data reset and then your phone will reboot and it will be as new as you bought it that time only.
Hope it helps
Sent from my GT-I9300 using XDA Free mobile app

Related

[Q] Need help to unbrick, can´t even get to download mode

Hello guys,
I really really need your help, I have spend like two weeks reading articles and possible solutions to my problem and none of them worked.
My cell is the international version GT-I9100 and my PC has W7 Ultimate installed
I have my phone in USB debug mode and have installed USB drivers with KIES
2 weeks ago I was able to get to download mode by using the 3 buttons method with no problems... so I decided to try to install the latest ICS I9100XXLPQ with ODIN
Odin did recognized the cellphone and the yellow label appeared and show the message accepted... so far so good, put the I9100XXLPQ file in PDA, check the Auto Reboot and F. Reset Time options and hit the Start button but the problem started there.... it just sits at setup connection and wont do a thing. wait for more than 30 mins and nothing just sits there.
So I unplugged the cellphone from the cable thinking that it would be ok since Odin didn´t started with the flashing process (or at least that what i thought)... there´s the problem, now my cellphone does not came up and I´m not even able to get into download mode. I just get a black screen (see attachment)
I have tried with the 3 buttons, with One-Click Unbrick and with the Jig cable and none of them worked, I just keep getting the same screen.
(by the way... i tried with One-Click Unbrick but it still saying that the drivers are not installed properly so it keep installing the drivers over and over and I have not been actually able to use it.)
Odin is still able to recognized the cellphone so I tried to re-flash the cellphone doing the same thing this time it passed the connection setup and seems that it will worked but after 5 to 10 mins it failed but with no error message. I guess that it wont do anything since the cell is not in download mode.
Any ideas or suggestions would be more than appreciate!
Regards...
I once had the same problem. When odin sees the mobile even if its not in download mode. This means its connected but the bootloader is broken.
To fix this u need to use some program called hamedal or hamidal or something. I used it to unbrick my galazy tab. you can flash the boot section (bootloader image) manually thru it and it will fix your mobile.
Try to google about it and how to use it. If you don't find anything. Pm me and I will try to help u .
Sent from my GT-I9100 using xda premium
try to use a JIG,it will force the phone to enter the download mode
fearkillerr said:
I once had the same problem. When odin sees the mobile even if its not in download mode. This means its connected but the bootloader is broken.
To fix this u need to use some program called hamedal or hamidal or something. I used it to unbrick my galazy tab. you can flash the boot section (bootloader image) manually thru it and it will fix your mobile.
Try to google about it and how to use it. If you don't find anything. Pm me and I will try to help u .
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I think that you are taking about Heimdall
One Click Unbrick is the same thing.... (Heimdall One-Click project)
I tried that already... but thanks
I haven't worked much with i9000 or i777 to figure out heimdall compatibility. Your option is Odin right now.
Your only solution is a USB JIG.
shesho07 said:
I think that you are taking about Heimdall
One Click Unbrick is the same thing.... (Heimdall One-Click project)
I tried that already... but thanks
Click to expand...
Click to collapse
Just open that program, install the usb drivers for it while connecting your phone and try to flash the zimage.img into the phone manually. I believe it will work. I've fixed many bricked galaxy devices with that.
Sent from my GT-I9100 using xda premium

[Q] Mobile Odin Boot Loop No recovery Access & Not recognized by computers... HELP!!!

[Q] Mobile Odin Boot Loop No recovery Access & Not recognized by computers... HELP!!!
Full Story (summary below):
OK, here's my story. My GT-P7510 (Galaxy Tab 10.1-Wifi) was running AOKP's ROM a while ago and something went terribly wrong. It would not boot and was unable to mount to the computer.The only way I could think of fixing it was a full erase (minus storage). It didn't help. After a long time of being idle and thoroughly searching its storage I stumbled upon a ROM that was hiding in its depths, and immediately flashed it. It was a Cyanogen Mod. After flashing however the tablet was still unable to mount to the PC. After changing PC's, driver's, OS's, the whole nine yards, etc. It still did not mount to the PC. So I gave up on it. I was able to do nearly everything without access to PC mounting. So I kept it like that for awhile. Until pure idiocy struck me and I took hold of the notion that if I used Mobile ODIN and flashed a stock firmware with it, My tablet would be restored to its former glory. Big Mistake. Immediately after flashing Stock with Mobile Odin, I entered a Boot-loop of Mobile Odin's devise. All it does is run some Mobile Odin text really fast, and then restart. Again, and again, and again. (I really hate Mobile Odin now) And Mobile Odin has seized control of trusty CWM Recovery (at least I assume it has, but it could have also just replaced CWM with itself); So that whenever I choose recovery It simply runs the same faulty Mobile Odin text and restarts. And going to Download mode is pointless as the computer always says that "It cannot connect because the device has malfunctioned." (In Windows 8) . . . That's my story... Help?
:fingers-crossed: :crying: :fingers-crossed:
Very simplified summary:
In Mobile ODIN Boot-Loop, No Recovery, PC does not recognize, ODIN and ADB do not recognize. Trapped. Help?!?!
I am in a similar situation with my note II I am going to try to enter Download mode, with windows vista and see what I can come up with. Have you had any luck?
I plugged in and flashed the latest update via odin, and am booted into a fresh install. GL
Still at it.
Good to see that you got yours fixed.
Sigh... but alas my problem is a bit more complex. After a chat with Samsung about it they said that the OS is corrupted (duh) and that they wouldn't help me without quite a bit of money. Seeing as how the warranty is long gone.
However I have been tinkering with nvflash and there's a glimmer of hope in it. But that whole unable to connect thing is really complicating things.
I have a TAB 10.1 GT P7510, I used mobile Odin for flash a recovery, and don't boot, solution?

Galaxy Player 5.0 Intl bricked- Help?

Hello everybody,
I know this question has been asked multiple times, but after Googling for hours and searching in almost every thread about this subject here, I haven't found the solution yet.
What you need to know first
What happened is:
I tried flashing cm11, it went wrong, so I tried it again. Went wrong again. I decided to reboot the device and try it one more time. I couldn't even try that, cause I wasn't be able to go to recovery anymore. Booting into Download mode was possible though. So I decided to flash back to stock trough Odin, but Odin failed (posssibly a corrupted file), leaving me with the:
Phone--- exclamation mark ---PC sign, I wished I never needed to see.
What I tried and what still works is:
*Connecting to PC works (I can't see the files on the player, though). Odin does still recognise the device.
* Because Odin still recognised the device I tried flashing stock back. Odin failed in doing that, so then I tried using the pit file provided. This time Odin hanged at: DO NOT TURN OFF TARGET (please note: Odin on pc said this, player stil showed the phone-exclamation mark-pc sign). After Googling around I found I could just pull the USB cable out and try again, but unfortunately this didn't work.
HELP!!
So my question is: Is it possible for me to recover my international GP 5.0, and if so HOW?
Once again, Sorry for asking this question and thanks in advance.
-BrickedPlayer
P.s. Sorry for my bad English, it isn't my first language
P.P.S I wondered if Unbrickable Mod or OneClick Unbrick work, I'll try them asap (that means: when I have access to a Ubuntu PC, what I haven't now.

Bricked S2

Was trying to go from GB 2.3.3 to OmniROM 4.4.4 on a friend’s S2 (GT I-9100).
I rooted using Framaroot (the first version, the latest wouldnt work), got root, checked with RootChecker. Then I tried to install CWM.
Spent hours trying, I wanted to do everything "on device" rather than use Heidal or ADB (use inux on my desktop), tried MobileOdin, but there was no "recovery" option, so tried ROM Manager using a guide ( http://luvis.se/tipstricks/root-and-install-kitkat-on-samsung-galaxy-s2-i9100-without-a-computer/ ), but kept failing cos of E signature verification, even though ROM Manager said it was installed.
I d spent hours and hours on the internet looking for how to install, seems its difficult because the device was GB.
So I tried MobileOdin again and just installed the "CWM-KitKatCompatible-i9100.zip" I downloaded from the above guide using the "install update.zip" option, I cancelled it when the warning came up about firmware can brick your device, but then hit "ok" (partly in frustration and partly cos I ve never bricked a device before as I m (USUALLY) always careful).
Now it just boots the the Samsung Galaxy S2 screen, then the screen goes blank after 10 seconds or so. Stupid, stupid me.
So can anyone help me recover it using ADB, Android Studio or maybe Heimdal or direct me to a guide on how to ? Everything I read uses Odin and assumes you can get into recovery. All that time trying to avoid connecting it to a pc and now I ve deffo got to.
typos1 said:
Was trying to go from GB 2.3.3 to OmniROM 4.4.4 on a friend’s S2 (GT I-9100).
I rooted using Framaroot (the first version, the latest wouldnt work), got root, checked with RootChecker. Then I tried to install CWM.
Spent hours trying, I wanted to do everything "on device" rather than use Heidal or ADB (use inux on my desktop), tried MobileOdin, but there was no "recovery" option, so tried ROM Manager using a guide ( http://luvis.se/tipstricks/root-and-install-kitkat-on-samsung-galaxy-s2-i9100-without-a-computer/ ), but kept failing cos of E signature verification, even though ROM Manager said it was installed.
I d spent hours and hours on the internet looking for how to install, seems its difficult because the device was GB.
So I tried MobileOdin again and just installed the "CWM-KitKatCompatible-i9100.zip" I downloaded from the above guide using the "install update.zip" option, I cancelled it when the warning came up about firmware can brick your device, but then hit "ok" (partly in frustration and partly cos I ve never bricked a device before as I m (USUALLY) always careful).
Now it just boots the the Samsung Galaxy S2 screen, then the screen goes blank after 10 seconds or so. Stupid, stupid me.
So can anyone help me recover it using ADB, Android Studio or maybe Heimdal or direct me to a guide on how to ? Everything I read uses Odin and assumes you can get into recovery. All that time trying to avoid connecting it to a pc and now I ve deffo got to.
Click to expand...
Click to collapse
Can you get into download or recovery mode?
noppy22 said:
Can you get into download or recovery mode?
Click to expand...
Click to collapse
Cant get into recovery but can get into download mode. Tried One-click Unbrick and it cant connect to device, which reminded me that when I connected it to my (Ubuntu) pc (before I bricked it) I got an error message saying it couldn’t mount Android device (I got rid of my S2 a couple of years ago but it always connected to my pc with no problems). Which seems to me like a real problem - how can I un-brick it if I cant connect via USB ?
typos1 said:
Cant get into recovery but can get into download mode. Tried One-click Unbrick and it cant connect to device, which reminded me that when I connected it to my (Ubuntu) pc (before I bricked it) I got an error message saying it couldn’t mount Android device (I got rid of my S2 a couple of years ago but it always connected to my pc with no problems). Which seems to me like a real problem - how can I un-brick it if I cant connect via USB ?
Click to expand...
Click to collapse
First, I don't have any experience with ubuntu, so I would suggest connecting to a windows pc via usb, making sure you install the drivers for the s2, then download odin. Once you have odin setup, I would flash a stock rom .tar from sammobile.com. From there you can flash a kernel such as philz to gain root access, and then omni or other rom.
noppy22 said:
First, I don't have any experience with ubuntu, so I would suggest connecting to a windows pc via usb, making sure you install the drivers for the s2, then download odin. Once you have odin setup, I would flash a stock rom .tar from sammobile.com. From there you can flash a kernel such as philz to gain root access, and then omni or other rom.
Click to expand...
Click to collapse
Heimdal on Ubuntu (or a Mac) will do the same job as Odin on Windows (and is more reliable), but I have this USB problem I mentioned above, so I m not sure anything is going to work if theres a problem with USB on the device (USB debugging was enabled). One-Click Unbrick cannot connect to it and nor can my pc.
typos1 said:
Heimdal on Ubuntu (or a Mac) will do the same job as Odin on Windows (and is more reliable), but I have this USB problem I mentioned above, so I m not sure anything is going to work if theres a problem with USB on the device (USB debugging was enabled). One-Click Unbrick cannot connect to it and nor can my pc.
Click to expand...
Click to collapse
Probably obvious, and you've maybe tried already, but will a different usb data cord work? And I would try a different pc just to rule it out.
Here is something to read as well about recovering from soft bricks. Hope it helps -
http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771
noppy22 said:
Probably obvious, and you've maybe tried already, but will a different usb data cord work? And I would try a different pc just to rule it out.
Here is something to read as well about recovering from soft bricks. Hope it helps -
http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771
Click to expand...
Click to collapse
Thanks, already read that, its not the cable as I use it on other devices without problems.
typos1 said:
Thanks, already read that, its not the cable as I use it on other devices without problems.
Click to expand...
Click to collapse
Mate, the only thing I can suggest is make sure you have drivers for the phone(although the message saying can't mount device indicates a problem like corrupted partitions or nand, rather than missing drivers), and try a different pc. The fact you can get into download mode at least suggests you can flash a kernel or something, but you need a connection to the pc to do that(as you already know). I hope someone else has some other ideas
noppy22 said:
Mate, the only thing I can suggest is make sure you have drivers for the phone(although the message saying can't mount device indicates a problem like corrupted partitions or nand, rather than missing drivers), and try a different pc. The fact you can get into download mode at least suggests you can flash a kernel or something, but you need a connection to the pc to do that(as you already know). I hope someone else has some other ideas
Click to expand...
Click to collapse
I wont need drivers as Linux has drivers built into it - it works out of the box, no messing around installing them like with Windows.
I just gotta spend some time getting the firmware and finding instructions on doing it with Heimdall, theres so many versions of the S2 it makes finding the right software complex.
And I ve just got to hope there isnt a problem with the usb port on the device or I m really buggered
typos1 said:
I wont need drivers as Linux has drivers built into it - it works out of the box, no messing around installing them like with Windows.
I just gotta spend some time getting the firmware and finding instructions on doing it with Heimdall, theres so many versions of the S2 it makes finding the right software complex.
And I ve just got to hope there isnt a problem with the usb port on the device or I m really buggered
Click to expand...
Click to collapse
Lol, I forgot that on Samsung devices you have to press home as well as power and vol up for recovery, found this out while trying to fins out how to unbrick it !
It wouldnnt boot but it WOULD boot to recovery, CWM recovery !
So flashed a CM kernel then Omni and all is fine, OmniROM installed !
typos1 said:
Lol, I forgot that on Samsung devices you have to press home as well as power and vol up for recovery, found this out while trying to fins out how to unbrick it !
It wouldnnt boot but it WOULD boot to recovery, CWM recovery !
So flashed a CM kernel then Omni and all is fine, OmniROM installed !
Click to expand...
Click to collapse
Haha! The simple things in life....
noppy22 said:
Haha! The simple things in life....
Click to expand...
Click to collapse
Yeah !
Ta for your input !
Try flashing official frimware with odin or flash siyah kernel with heimdal
Should fix your problem

Am I doomed

Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
muddled said:
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
Click to expand...
Click to collapse
Hey Mate,
Firstly we all are noobs here helping each other, secondly from my experience of S3, it is such a device that under any condition, if your hardware is intact, you can recover your phone from almost anything, so yeah you might have a solution to your problem.
Coming to the problem at hand, i had the same thing happen to my S3, (only twrp logo showed, couldn't access recovery, no ROM, only download mode available) the way i fixed it was using odin, now i know you say that odin is not recognizing your device, the thing is firstly Kies is useless in this situation acc. to me, it only works stock ROM and that too with difficulty, what i would say is go here - http://developer.samsung.com/technical-doc/view.do?v=T000000117
and then install the drivers to your PC, next up download the official firmware from sammobile or any other site (careful of the version you are using), now put the phone in download mod, start odin and then connect your phone. Now, hopefully odin will recognize your phone and you can flash the official firmware, also i would recommend to stay on the official firmware for like a week before returning to flashing again as i have noticed that constant flashing and wiping leads to not only errors like "unable to mount EFS" but also serious errors like "Unable to mount /system" or "Unable to mount /Data" ,which clearly sucks
Please try the method and tell me if it worked , if not we'l try something else but we sure as hell will get your device working again
If still not recognized then here is a suggestion :
Exit/uninstall from nokia/ovi suit.
Exit/uninstall bluestack. (if u r using it)
Update your drivers(phone specific)
Use correct odin version acc to ur phone
Sent from my Micromax E352 using XDA-Developers mobile app
I'm just gonna throw my 2 cents in too. I didn't read your whole thread as I'm in a slight rush right now.
But basically -
Can your PC recognise your phone when it's plugged into USB in Download Mode? If so, use ODIN to flash any stock firmware and you're back to square one (working, but stock) phone. Then go from there. Obviously try to flash the right firmware or you'll end up no further forward.
If it can't recognise it, try reinstalling the drivers, uninstalling the programs mentioned above and using another USB cable. My experience with my own S3 has shown potential wear with the USB port on the bottom of the phone presumably due to it's age and as a result it doesn't recognise many USB cables.
Regards

Categories

Resources