Related
I thought I should share this with everyone in case it helps someone out there. I might have gotten lucky, so YMMV.
Basically like everyone else my SGS (I9000M from Bell) died due to an internal SD error, but in my case I haven't updated the phone since I got it in September 2010 (it had the JG9 firmware). The good thing is I was able to flash it to the stock Froyo 2.2, and I'm currently using it as normal and can access the internal SD without problems.
Summary of steps that most likely fixed the problem:
Go into recovery mode and "wipe data/factory reset". If your phone boots (but still have problems accessing the SD card) then it's a good indication that you maybe able to fix it.
Flash JL2 (from samfirmware.com) using ODIN. Not sure if this is needed, but you may need to ask ODIN to Re-partition. You still get an error "Can't mount DBDATA", and the phone won't boot. That's ok.
Flash the SpeedMod Kernel using ODIN (I used SpeedMod K12J with HZ=256). Your phone should boot into JL2 and the SD card should be accessible again.
At this point your internal SD card is fixed and you should be able to flash whatever you want. Just note that Kies will sometimes not work properly with the SpeedMod installed. In my case I flashed 2.1 (JH2) again (this won't work if you have 2.2 without speedmod kernel), then used Kies to update to 2.2 (JL2).
For those who are interested in the details, please read on.
Bought the phone in September, it's a Samsung Galaxy S I9000M from Bell. It says 10.07 on the back of the phone, and it had the JG9 firmware on it.
Since the 2.2 update came out I've been following closely the problem of the internal SD failures and the grief it's causing to a lot of people. So I decided to hold off updating until Samsung gets their act together. (I know it's better to update as soon as possible in case it dies so that I can use the warranty, but I had 9 months remaining so I decided to wait a little more.)
Close to the end of 2010 I noticed that my Android Market has changed, and that it now allows me to "Update All", so I just hit that and noticed that after updating several apps, all the remaining updates failed. I knew this wasn't a good sign. My SD card was still fine though.
After the above incident the phone felt a bit sluggish and less responsive than it used to be. I hadn't correlated this to anything yet, but now I know it was most probably due to the internal SD on its way to die.
On January 7 the phone suddenly died. When I rebooted it, I got the infamous symptom of seeing the S logo animation then black screen, then if I touch the two buttons at the bottom they light up indefinitely. At that point I knew it was the internal SD card.
I put the phone into recovery mode and confirmed my guess when I saw the red error message "Can't mount SDCARD".
I took the phone to the Bell store, the guy told me Bell now has an expedited shipping process for this problem and gave me a number to call to get a new replacement phone.
I called the number and they verified the symptoms with me, and said they're going to send me a new phone. I asked for the $100 credit but I was told I can't get it since I didn't update to 2.2. Apparently they only give you the credit if you actually tried to update and the update caused the phone to die (which doesn't make any sense to me).
So, while waiting for the new phone to arrive, I decided to try a few things. Here's what I did:
First thing I did was going into recovery mode and doing a "wipe data/factory reset". To my surprise, the phone actually booted after I did that, but I got force closes on almost all apps, and when I checked the internal SD card it wasn't mounted at all. The phone response was extremely slow and barely usable. I was able to make phone calls though.
I wondered if the SD problem is a corrupt partition rather than a physical error. After searching for a while I found someone posted a solution to fix a problem with his internal SD card by using the "parted" tool to mkfs the partition. Unfortunately I couldn't copy the tool using adb; my phone wasn't rooted and I couldn't access the SD card, so there was no place to copy the binary to. I get either a read-only error when trying to copy to the root, or a permission denied error when trying to copy to other mounted partitions.
Then I figured if I could flash 2.2 somehow (even if it doesn't work) I can try to ask Bell for the $100 credit Kies was useless as it couldn't recognize the phone, so I grabbed the stock JL2 firmware from samfirmware.com and used ODIN 1.7 to flash it. I asked it to Re-partition (not sure if this was needed). After reboot I saw another red error message, but this time it was complaining "Can't mount DBDATA" (as opposed to SDCARD). Then all reboots after that resulted in the same problem (S logo then black screen).
I searched for the "Can't mount DBDATA" error and found a post on xda that shows a method that should fix this by first using a 512 PIT file to repartition (no ROM involved), then flashing a stock firmware. I did that but it didn't help.
Then I found a site called "AKA skriller" that shows a way to reflash a stock firmware after the phone is bricked. So I followed the instructions by flashing a "nobrick" image (apparently made by someone called eugene), and then flashing a stock firmware. I flashed nobrick then JH2 in attempt to go back to 2.1. After doing this the phone went into a boot loop where it keeps showing the I9000M screen then rebooting. At that point I couldn't go into recovery mode, but I could go into download mode.
After searching again I found out that this was due to a new bootloader in 2.2 that prevents going back to a 2.1 firmware. I wanted to stop the boot loop so I flashed JL2 again, which stopped the boot loop but still the phone won't boot (black screen).
After more searching I found that I could go back to a 2.1 firmware only if I flash a custom kernel, someone suggesting the SpeedMod kernel (not sure if it has to be SpeedMod or any other kernel). So I flashed SpeedMod (I used SpeedMod K12J with HZ=256) using ODIN 1.52. First thing I got is a custom recovery menu with more options, I just skipped it and rebooted. THE PHONE ACTUALLY BOOTED this time into 2.2. Not only that, but the SDCARD problem was FIXED, and the phone was responsive and fast again.
I wanted to load my contacts again using Kies from a backup I made earlier. Kies recognized the phone but for some reason the contacts widget keep saying "please connect your phone" and I couldn't copy back my contacts.
I thought this might be due to the custom kernel and I was right. I flashed a stock 2.1 (JH2) with a bootloader included using ODIN. It just worked. I could copy my contacts again back to the phone.
I was also able to update to 2.2 (JL2) again using Kies this time, and it even kept my contacts. This is what I have now on the phone.
P.S. I can't post external links due to a restriction by the forum (since I'm new).
I had my doubts when I opened this thread... I've gone through 5 phones already and just finished killing my sixth...
I had tried flashing JL2 stock after killing it through the usual process (transferring over my music collection)... and got the EXACT same errors you wrote about.
What I didn't try was then flashing the custom kernel... so I tried that...
and it was too good to believe... didn't work for me. after the boot animation, display goes blank and buttons off... you can tell it's not going to work if it starts vibrating during boot.
I'm sorry it didn't work for you. As I said I might have been lucky.
Although that I just found another thread on androidforums where the guy managed to fix his sd card in a very similar way to what I described*. I actually haven't seen his post before I fixed my card, so it was independent.
Here are the commonalities between what I did and what he did:
* We both flashed a 2.2 firmware with a PIT file and Re-partition (using ODIN)
* We both got the black screen afterwards
* We both then flashed a custom kernel with no Re-partition
* We both got recovery menu right after flashing the kernel
* We both ended up in Android 2.2 aftwerwards with the SD card fixed
Here are the differences between us:
* I used JL2 firmware while he used JPM
* I used a 512 PIT while he used an 803 PIT (that's just what samfirmware.com said to use for each firmware)
* I flashed the firmware using ODIN 1.7 while he used ODIN 1.3
* I used the SpeedMod kernel while he used the YAOK kernel. He flashed using ODIN 1.3 while I flashed using ODIN 1.52.
* Once in the recovery menu I rebooted right away into 2.2, while he "ended up selecting every option that had something to do with mounting, formating, erasing. Anything to do and sounding to do with the SD card [he] pressed." then rebooted successfully with no SD card errors.
(*)http: //androidforums.com/samsung-galaxy-s/235987-clueless.html
what slaman encountered was REAL hardware failure, like I did
what you encountered was just a Corrupt SD card, which can be fixed all the time, using the process you described, and many other methods.
Real hardware failure, even if you manage to boot into the OS, it will show no internal SD, or 0 available space, or simply an error message complaining about the internal SD
You can only see that with custom ROMs, with a stock ROM you wont even get past the black and white SGS logo screen
internal SD card
Hi,
I have followed a few discussions on this board as also my internal and external SD card was "gone". I couldn't access or mount it any more after flashing with Odin to european JPY 2.2.1 ... and I found out where at least my internal memory has gone.
In fact the internal memory couldn't be accessed after installing an exchange email account. My OWA account requires security like password protection and NO external SD card.... but it seems that version 2.2.1 does not make a difference between internal and external SD card and removes the access to both away. It looks like disappeared but it comes back after uninstalling your exchange email account.
May be this is all known and logic but I couldn't find the explanation to it therefore I would like to post the information.
Thanks
Thank you very much for this! I indeed had the mpbk01 (whatever) error, and did exactly what was posted above (using 512 pit, and 1.7 odin) and now have my pone working just fine.
Again, thanks a lot for the post!
Edit: While all this is true.. seems like i have 0.00b of internal phone storage available, so I cannot install any apps. The internal SD card space is reporting normal at 13.03gb though.
Glad it worked for you. Hope you can solve the internal phone storage problem though.
As I mentioned I might have been lucky, I don't expect everyone to be able to fix the internal SD card problem by just flashing custom roms/kernels. If it works for a few people then I'm happy I saved them the hassle of going through Bell to replace the phone.
just a suggestion to send it out for repair, before you run out of warranty
Uss_Defiant said:
Thank you very much for this! I indeed had the mpbk01 (whatever) error, and did exactly what was posted above (using 512 pit, and 1.7 odin) and now have my pone working just fine.
Again, thanks a lot for the post!
Edit: While all this is true.. seems like i have 0.00b of internal phone storage available, so I cannot install any apps. The internal SD card space is reporting normal at 13.03gb though.
Click to expand...
Click to collapse
uys I have a very serious problem. I'm on Darkkys latest rom...
I took out my battery for 1 hour... put battery back in and the phone did not boot up.
All I got was the screen saver and the phone kept on virbarting...
I tried wiping cache through clock work recovery, resetting to factory settings via clock work.. still nothing..
I just updated phone via odin to latest JPY...the phone goes to black screen and keeps vibrating... It won't boot.
Guys what's wrong with my phone? I am really worried...and I need to use it
I appreciate your help.
Ps. Phone can go into download mode..
Edit: XWJM8 worked
jUsT2eXy said:
uys I have a very serious problem. I'm on Darkkys latest rom...
I took out my battery for 1 hour... put battery back in and the phone did not boot up.
All I got was the screen saver and the phone kept on virbarting...
I tried wiping cache through clock work recovery, resetting to factory settings via clock work.. still nothing..
I just updated phone via odin to latest JPY...the phone goes to black screen and keeps vibrating... It won't boot.
Guys what's wrong with my phone? I am really worried...and I need to use it
I appreciate your help.
Ps. Phone can go into download mode..
Edit: XWJM8 worked
Click to expand...
Click to collapse
well I have this problem and cant get it sorted at all, it seems to have also created another partion and i have no idea how to wipe the sd card clear of all partions so it can recreate them!!!!
please help !!!
Hii there,
this thread seems to be very helpful, so I want to value your help with something in return. if any of you can get me out of this mess I will donate you appropriately so that you can constantly offer this helps to others too.
some details are as follow:
1. my Galaxy S (korean) M110s was on USB downloading Market update when I disconnected it abruptly to make a call. It was downloading some updates then.
2. moment than its showing SD card damage error and even showing 00 for external SD card which I inserted post that.
3. this means neither internal nor external SD card are being detected. Though it shows that ext SD card is mounted when I insert in and also let me unmoutn it.
BTW I have tried flashiing using odin and eclair 2.1 version which didnt help much.
Need urgent help
usb jig only gets me into download mode. and not recovery mode
so can Odin still get it to work while in download mode instead
It worked for me but I can't access the internal memory nor the external one. Hence, I can't use the camera or install any app. I don't have any kind of warranty so I believe this is the best I can get, right?! At least I can use as a phone and browse the internet!
Thanks for your help, even though it worked half-way for me!
http://forum.xda-developers.com/showthread.php?t=1020278
Please take a look of this thread:
http://forum.xda-developers.com/showthread.php?t=1188482
It may fix your internal sd card problem permanently.
Hi All,
Please HELP.
I was a complete noob to rooting until I started this but spurred on by successfully rooting and overclocking / undervolting my defy I thought I would try to install Gingerbread so I can use the stupid stupid sky+ app which no longer supports 2.2.2.
Its all gone horribly wrong and I still dont know why as I checked and rechecked the prep but S..t happens so they say.
I have pretty much given up on this and will buy a new phone tomorrow if I cant sort today but would like to ask everyone that has more knowledge than myself on this subject (which doesn't narrow the field much!) if they have any ideas.
Well where do I start, I bricked my defy.
Apart from when I flash shadows rom (see below) I have only black screen, white led on usb connection, no recovery boot. phone is visible to rsd lite but nothing else. This happened after I lost sd card availability after reset / wipe trying to install a fixed gingerbread rom using RSD lite.
I could not flash back to froyo and every other recovery sbf i tried wouldn't work until I found an old sbf from shadow which actually booted up! YESS!! but then Nooo!. phone screen looks very nice - not sure what version it is but assume ICS (its got spareparts folder which I`ve not seen before) - and works as alarm clock and web browser but no phone function at all - no signal, no call or end call buttons - just not there! this (http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143) is the link where I found shadows version, couldn't wipe in between each step so just flashed 3 files in turn using rsd lite and it seemed to work - phone booted up after 3rd sbf was flashed. The rom is set up for developers and has some developing tools included acr, api demo,dev tools, hstcmd & redlinecap
Main problems:-
The rom is a tmobile version and I`m on vodaphone so maybe this is why there's no phone service but I wasn't prompted for an unlock code so assume its not locked.
The 2nd boot recovery no longer works even after reroot and reinstall (see below). I can surf the web very well via wifi - much quicker than before but downloads dont seem to work but only tried shortfuse.org and that site is apparently down atm and anything that requires google wont work as Gapps got deleted. I cant install GAPPS without boot menu.
recovery from main boot menu is unavailable and zip from sd just reboots.
I also cant connect my phone to my pc via usb and have the sd card available at the same time, as soon as the USB is connected the sd card is not available to the phone, I can see it on the pc and can read / write / delete from the pc - (usb debugging is disabled). when I access the sd card via file manager on phone (with usb disconnected) I can install some programmes that I have transferred from my pc; 2ndinit installed and said 2nd init installed ok again (after re-rooting) but still no blue led on reboot.
I've since tried everything I can think of or search for - After loosing the sd card availability I copied card contents to pc and reformatted sd card on pc. copied back the files immediately before flash attempt to sd as well as the rooted froyo backup I had and nothing changes. I have a titanium backup on the card but have so far been unable to install titanium again to try and restore it. no play acces as no gapps and when I try to access via pc and send it to phone it says installed but its not on the phone. every other file on the sd card results in error parsing file or file type not supported.
BTW when I say originally that I lost sd card availability I have now realised that it was the problem with having the usb installed at the same time which caused it and if I had unplugged it may have worked but still dont understand where this problem came from but I did have usb debugging turned on at the time.
I have scoured these holy pages for 2 whole days and tried several fixes which have probably really messed up everything even more but nothing has changed with the usability (or not) of the phone. A lot of the old links found were dead or taken over by a fake install of filemanager that my antivirus caught was a trojan. Due to this I may have missed an avenue or 2 but think I`ve tried everything I can.
At this stage I do not know exactly what I`ve tried as the list is endless but it includes reflashing the green lense kernel, attempting to reflash the original rom and any other recovery, fixed or stock roms I have found which don't specifically say only for defy+ and the only rom that allows the phone to boot is shadows above and that has no functionality.
I would love to install the latest cm10 build but cant get into the 2ndinit menue so unless someone knows away to flash it using RSD lite I`m stuck.
I do not even know if the cm10 would work as I`ve probably messed up the kernel and the original rom so the 2nd init may not get a look in.
Any help would be greatly appreciated. You'll find me under the stairs mumbling to myself and probably dribbling a bit - my wife thinks I`ve gone mad and is not talking to me until I get another phone or fix this one but I hate admitting defeat on technical problems.:crying:
PS I dont mind if I fix the issues with shadows rom, go back to any stable build or get cm10 working I just need the phone.
Thanks in advance, Tim
update
Hi All,
Just a quick update on this thread as I`ve had a bit more of a play and think I`m getting somewhere possibly.
I have now eliminated the problem of not being able to see the sd card files in file manager when the usb is connected.
How? - i haven't got a clue, i just unsuccessfully tried flashing a few more roms and when I reinstalled shadows rom i could view files whilst connected.
Also the 2ndinit now gives me the green led when it installed the 2nd boot but unfortunately I still dont get the blue led on reboot.
Another strange thing is I dont get the round M logo on boot but motorola written in white??
If I could just get to the CW recovery on boot I could install cm10.
Any suggestions?
Thanks
Tim
fixed by flashing with JDGC_U6_2.13.0
YESS FIXED BY FLASHING JDGC_U6_2.13.0 SBF using RSD lite.
Many thanks to everyone that helped via another thread http://forum.xda-developers.com/showthread.php?t=1217016&page=2, I thought they were far too many issues with this phone to repair but the latest froyo rom and kernal in the above sbf worked fabulously.
As has been said on several posts flashing this SBF will not allow you to return to the uk stock rom after (to return a phone under warranty etc) but if you're stuck with a brick then this should clean up your phone to original settings to allow the install of cm10 or another rom of your choosing (as long as its build 6 or later)
Hey guys
Just got a S5 (previously owned a S2 and S4 Active, which I have rooted and put custom ROMs so many times. Hence I'm familiar with Odin, Recovery, etc etc).
About a week ago, I installed Shohat v5 ROM, everything went fine. I was quite happy with it.
I installed back my app from my S4 Active through a big update.zip (backed up with Titanium paid version) thanks to custom recovery.
And just now, when my battery was like 5% left, I decided to make a hard reboot (as Xprivacy warned me that I needed to restart to have my changes into effect).
I charged my phone and THEN I push the reboot button (not the hot boot).
While charging, the screen went normally black, but stayed black with the blue LED notification ON (not sure if that info is important).
Then, black screen stays forever:
- no logo
- no download mode
- no recovery
- When phone is connected through USB to my laptop, I hear the usual "tadaam" sound from Windows, but no "USB notification".
It seems a JIG would be the solution, but no idea if that would work for a S5 (I guess Samsung has now worked to avoid that solution)
Well, if anyone can help, that would be cool
Obvious I know but you have pulled the battery for a while and tried again right?
Sent from my SM-G900F using Tapatalk
Goldie said:
Obvious I know but you have pulled the battery for a while and tried again right?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Hello
Indeed, I just removed the battery for a few hours a tried, no success.
But is it normal that a hardbrick can occur 1 week after installing a custom ROM?
Right now I can't bring it to Samsung store for repair...
(Adding a new post as editing is not working properly)
Isn't there a way to use ADB with commands through Windows (as there is the "tadaam" sound when I connect it through USB)?
A friend of mine bricked his Nexus tablet and went through such solution to remove the brick ...
OK ............
Here's the magic
After removing on and off the battery many times, trying to boot in recovery or download (trying about 15 times)
Now I managed to boot in recovery (I was like "huh?" and "wooohoooooo")
Did Wipe cache
Did Wipe Dalvick
No Factory reset
Fixed root (seems like I lost it, no idea why)
Let's see if I can reboot it
I think maybe the issue came from the huge update.zip created from my S4 Active (i9295) with Titanium backup (I was in Android version 4.2.2).
Maybe the reinstalled apps, messed up something as the ROM was in version 4.4.2...
Desanusseur2porc said:
OK ............
Here's the magic
After removing on and off the battery many times, trying to boot in recovery or download (trying about 15 times)
Now I managed to boot in recovery (I was like "huh?" and "wooohoooooo")
Did Wipe cache
Did Wipe Dalvick
No Factory reset
Fixed root (seems like I lost it, no idea why)
Let's see if I can reboot it
I think maybe the issue came from the huge update.zip created from my S4 Active (i9295) with Titanium backup (I was in Android version 4.2.2).
Maybe the reinstalled apps, messed up something as the ROM was in version 4.4.2...
Click to expand...
Click to collapse
OK ... bad news again
I performed a hard reboot to check that everything was stable, and phone rebooted fine.
then I turned off and removed to battery to put back the SD card and the SIM card, and now the phone is not being turned on again.
And now the phone is not able to be turned ON again...
What's going on, any idea?
*** EDIT ***
I managed to reboot in custom recovery totally randomly after playing with the battery (removing, putting it back, trying to boot)
I made a full factory reset and reinstalled the custom ROM Shohat.
After rebooting, it went directly to ODIN as it was displaying error messages "ddi: MMC_read failed"
I guess the internal SD card is dead.
Questions:
1/ Is warranty OK if
- KNOX counter is at 0 (no idea why it is at zero)
- Current Binary is set to OFFICAL
- BUT SYSTEM STATUS is set to "CUSTOM"
2/ Can a custom ROM do this or is it a hardware failure?
Did you try with another sd card did you have apps installed on this sd card for me this sounds like a dead sdcard issue with some apps on it. I had the same issue with my X8 when a lot of apps ware running from the sd card btw sd cards are totally unreliably for storing important data as they usually die after some writing on them.
Change the SD Card and I think your phone will come back to normal.
SD Card Reader
Desanusseur2porc said:
After rebooting, it went directly to ODIN as it was displaying error messages "ddi: MMC_read failed"
I guess the internal SD card is dead.
Click to expand...
Click to collapse
I don't know if this helps but I had an GS-900H (S5 octacore version) and struggled with it for a week trying to debug this problem, ordered new memory cards, installed different ROMs, etc. only to find out that the card reader was bad.
In my case it would corrupt the card every time so that my PC would need to 'repair' it before I could begin using it in the PC.
Maybe the card reader is a common point of failure?
EDIT: I also had issues with different cards working and not working based on the speed of the SD card (different S5). I know for a fact that it will switch you over to main memory when taking pictures that require advanced features -- I got a popup telling me that my memory card wasn't fast enough.
alex_tytn said:
I don't know if this helps but I had an GS-900H (S5 octacore version) and struggled with it for a week trying to debug this problem, ordered new memory cards, installed different ROMs, etc. only to find out that the card reader was bad.
In my case it would corrupt the card every time so that my PC would need to 'repair' it before I could begin using it in the PC.
Maybe the card reader is a common point of failure?
EDIT: I also had issues with different cards working and not working based on the speed of the SD card (different S5). I know for a fact that it will switch you over to main memory when taking pictures that require advanced features -- I got a popup telling me that my memory card wasn't fast enough.
Click to expand...
Click to collapse
Hello guys
Thanks for your input.
Unfortunately I do not have an external SD card, the issue is with the Internal memory
So i can not request new ones or try to replace it, or work on the card reader...
Amazing that you are about to lose your phone forever and you don't even consider installing the original Samsung firmware.
What da f*** are you doing?
100%. Numb nut doesn't deserve the great phone It's like he got OCD.
Sent from my SM-G900H using XDA Free mobile app
lcmazza said:
Amazing that you are about to lose your phone forever and you don't even consider installing the original Samsung firmware.
What da f*** are you doing?
Click to expand...
Click to collapse
Hello
Well, not sure that ODIN will work as the internal MMC is not recognized, so where would that be installed?
Furthermore, I'm waiting for the feedback from Samsung (as knox counter is at 0, Binary is set to OFFICIAL and only status is set to Custom).
I did not want to change these counters with manipulating ODIN.
If Samsung gives it back to me with a new one, then wooohoooo
If Samsung says "f*** off, you manipulated it, warranty is off", then I'll use ODIN with STOCK ROM from Samfirmware + PIT file (they are ready for use on my computer)
If you can't get to download mode how do you propose to use Odin to flash stock ??
Sent from my HTC One using Tapatalk
Some time ago I tried to update the CWM 5.5.0.4 installed on my Huawei U8800, but unfortunately I did it with a wrong mobile version. In that moment I could get access to pink / blue screens and trying to recover the phone I inserted a copy of the stock ROM in the internal memory.
But after that the update process never works (failed on step 2) , and was not possible to get access to pink / blue screens again. Now, it doesn't matter what I do the phone goes straight to the update process (and of course, fails) . I tried inserting a SD card with stock roms on many versions but seems not be seeing it.
Any suggestions ?
Thanks
U8800kid said:
Some time ago I tried to update the CWM 5.5.0.4 installed on my Huawei U8800, but unfortunately I did it with a wrong mobile version. In that moment I could get access to pink / blue screens and trying to recover the phone I inserted a copy of the stock ROM in the internal memory.
But after that the update process never works (failed on step 2) , and was not possible to get access to pink / blue screens again. Now, it doesn't matter what I do the phone goes straight to the update process (and of course, fails) . I tried inserting a SD card with stock roms on many versions but seems not be seeing it.
Any suggestions ?
Thanks
Click to expand...
Click to collapse
Some people have reported successful update when they have removed battery and then power the device by using USB. Perhaps it works for you too.
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
Click to expand...
Click to collapse
You're in a rough spot here. You only have two possible options:
1) See if someone with your phone can make a debrick img file similar to this idea -
http://forum.xda-developers.com/showthread.php?t=2660566
I haven't seen anyone say they have tried something similar on your phone, but the only other option will be...
2) JTAG Service such as this -
http://mobiletechvideos.mybigcommerce.com/
If you're getting QHSUSB drivers, you're past the help of conventional unbricking methods using tools like Kies, Odin, or Heimdall.
Thanks, you've given me some hope! I have some data I would really like to restore..
I'll try and post back here if I get some results
johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
hope anyone kan fix my problem i returned back to the stock rom 4.0.4 after i was on cm 12 then tried to ger back to cm11 the wifi and the bluetooth is not working on both cm11 and cm12 what can i do
Click to expand...
Click to collapse