Develop Bugs

[Q] Phone went from Soft bricked to FULLY bricked, What are my options?

Hi, first let me give you the background of my phone.
I bought it off eBay used and it came in an almost perfect condition, preinstalled with Gingerbread 2.3.6. The only problems known with the phone is that it won't get recognized by Samsung Kies, but it does by my PC. Onto the problem...
My friend introduced me to the Cyanogen Mod 9, telling me it could increase battery life, performance, etc. I was interested and wanted to install this mod. I first rooted my phone with a Zip off a tutorial and that worked flawlessly and I had Super User. I then installed Rom Manager and proceeded to installing the mod. He gave me two zips to put into my SD card to install for the Cmod and Google Play. Long story short, after wiping cache, data user, and every other wipe before installing these two zips, I was stuck in a boot loop with the Samsung Logo and Cyanogen Mod 9 Animation. I didn't think much of it and turned off my phone for the night, leaving it for the morning.
This morning, I tried going to Download Mode and flashing a stock os with Odin3 and it went from boot loop to soft bricked. It gave me a message to connect the phone to Samsung Kies in order for it to before restored, but the problem is that the phone isn't recognized by the program. I tried .tar files and it led to nothing on Odin3 because it wouldn't get past "Get Pit for Mapping...". I tried numerous times and on one occasion, I accidentally had Re-Partition ticked but the flash didn't go through so I unplugged my device. After that, the phone turned off and no response after that.
It won't turn on, no device recognized through USB or Odin3. I tried the wall charger to see if it was the battery's fault but it led to nothing. What are my options in reviving my Samsung Galaxy S2 ?

Yikes. Sounds hard bricked. I think your only option is to pay to get try a jtag recovery. Search the board on that.
Sorry man.
Sent from my SGH-T989 using xda app-developers app

I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.

yoft1 said:
I agree. Not a lot of options especially since warranty will be difficult without proof of purchase.
For future reference (for you and anyone else in this situation) the boot loop you experienced is due to cwm v5.0.2.7 not wiping caches correctly. After flashing an ics rom, if you are running this recovery, you have to flash the darkside cache wipe to get the rom to boot.
Click to expand...
Click to collapse
Thanks for the replies! I was wondering how reputable is MobileTechVideos on doing JTAG repairs on bricked phones. Also, do you have a tutorial on how I can try to install Cyanogen Mod 9 again with the Dark Side cache wipe so i wont get the same problem again? Thank you.

[Q] Boot Loop trying to return to stock Gingerbread 2.3.6

I have the Samsung Galaxy S2 for T-Mobile SGH T989
My phone does not completely start up (stays in Samsung logo screen aka boot loop) ever since I tried returning to the stock Gingerbread 2.3.6.
My phone was running AOKP's version of Jellybean build 3 and I did not factory reset my phone before I went ahead and followed the directions in the following link to try and return to Gingerbread: galaxys2root.com/t-mobile-galaxy-s2/how-to-unrootunbrick-to-ics-stock-on-t-mobile-galaxy-s2-sgh-t989/
The reason why I was returning to stock Gingerbread is because one week after rooted my phone I formatted my SD card by accident which is where I believe Clockworkmod was stored therefore, causing clockworkmod to be deleted. I thought because I did not have clockworkmod on my phone that was the reason why the Jellybean rom was making my phone restart every 45 minutes. So my thoughts were to return to stock how I first got my phone and then just root my phone all over again and then the jellybean Rom would perform better... Unfortunately not.
In the link above, I noticed that its for people who were using ICS and I was on Jellybean which is where I went wrong. However, I'm sure there is a way this can be reversed.
By the way I tried going back to recovery mode and clearing/ factory reset and even wiping cache, however, when I choose any option that's not "reboot phone now" nothing happens so the only thing I can do in recovery mode is reboot my phone.
Whoever has even the slightest clue as to what I can do please comment I really need my phone for everyday purposes. Anything helps.
Thank you.

Sambucks said:
I have the Samsung Galaxy S2 for T-Mobile SGH T989
My phone does not completely start up (stays in Samsung logo screen aka boot loop) ever since I tried returning to the stock Gingerbread 2.3.6.
My phone was running AOKP's version of Jellybean build 3 and I did not factory reset my phone before I went ahead and followed the directions in the following link to try and return to Gingerbread: galaxys2root.com/t-mobile-galaxy-s2/how-to-unrootunbrick-to-ics-stock-on-t-mobile-galaxy-s2-sgh-t989/
The reason why I was returning to stock Gingerbread is because one week after rooted my phone I formatted my SD card by accident which is where I believe Clockworkmod was stored therefore, causing clockworkmod to be deleted. I thought because I did not have clockworkmod on my phone that was the reason why the Jellybean rom was making my phone restart every 45 minutes. So my thoughts were to return to stock how I first got my phone and then just root my phone all over again and then the jellybean Rom would perform better... Unfortunately not.
In the link above, I noticed that its for people who were using ICS and I was on Jellybean which is where I went wrong. However, I'm sure there is a way this can be reversed.
By the way I tried going back to recovery mode and clearing/ factory reset and even wiping cache, however, when I choose any option that's not "reboot phone now" nothing happens so the only thing I can do in recovery mode is reboot my phone.
Whoever has even the slightest clue as to what I can do please comment I really need my phone for everyday purposes. Anything helps.
Thank you.
Click to expand...
Click to collapse
Download a stable ICS ROM on your SD card from your PC, Darthstalker is pretty stable Put SD back in phone. Boot into recovery. Format system, cache, dalvic cache and data in recovery. (or darkside superwipe if you are on CWM 5.xx) Flash said ROM. Success!

[SOLVE] 4 issues remains after restoring to stock rom

Dear Experts,
Is there anybody that can help me to resolve these problems.
I just got my Note 2 3 weeks ago and last week I tried to use custom rom by Hypernote v0.4. While using it, some issues had arises. So, I thought that I should go back to stock hoping that the issues will dissappear. Unfortunately, after flashing stock rom via Odin and did a factory reset after that. Those issues remains, the issues are:-
1. Keyboard stop responding after a while.
2. Bluetooth not turning on.
3. USB to PC connection not detected. (Samsung USB driver installed on PC)
4. After screen auto shut down, cannot turn back on. Have to restart or reboot.
I have been searching high and low on the net on how to resolve it....
Hope something positive can be obtain here from the XDA experts.TQ in advance for any of your attention.:fingers-crossed:

Have you tried wiping everything after installing stock ?if not then try it.

nm8 said:
Have you tried wiping everything after installing stock ?if not then try it.
Click to expand...
Click to collapse
yup, did that. factory reset, wipe cache, wipe dalvik. still the same. thanks anyway for the respond.
I found out on HTC Desire thread they mention about "USB Brick" that cause the problems. I suspect it is the same thing is happening here but I can't follow the guide they gave for HTC device. Can any experts here convert it into Note 2 use.TQ.

Just for updated info.
I've manage to resolve the 1st issue of keyboard stop responding.
What I did was I flash back stock rom provided by dr.ketan link and together with pit file. Using Odin 307, I checked the repartition and nand erase. put the pit file on pit section and the tar file on pda section.
First boot stuck on samsung logo screen, reboot to recovery and factory reset.
Normal first boot procedure, keyboard working fine. but the other 3 issues still remain. still hunting for solution at the moment.

SOLVE
Thank to The Almighty God, finally I have got back my Note 2 on the track.
I upgrade my firmware with Stock 4.1.2 leaked by eybee. Flash with Odin 304 that come with it and repartition with the pit file that also come together with it.

Phone Not Booting - Very Weird Issue

I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?

OfficialDoughboy said:
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.

Ali7000 said:
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Click to expand...
Click to collapse
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Thanks for the response and taking time to answer.

OfficialDoughboy said:
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
OfficialDoughboy said:
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Click to expand...
Click to collapse
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).

aybarrap1 said:
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
Click to expand...
Click to collapse
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.

OfficialDoughboy said:
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
Click to expand...
Click to collapse
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.

hednik said:
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
Click to expand...
Click to collapse
I actually did that, sorry I wasn't clear in my original post. This last time, I wiped the cache and rebooted the phone, that didn't work. Then I tried Odin to see if I could save internal data, re-flashed and again couldn't boot. Last thing I did was do a factory reset through stock recovery and got the phone to boot.

[Help] I9250 gets stuck on "Google"-screen

Hello,
I've been searching for a while now to solve my problem, but I haven't found anything yet and hope that you might be able to help me here.
My Galaxy Nexus doesn't boot anymore, it get's stuck everytime on the "Google"-screen. I haven't done any updates or anything else. The last night it was working I just switched to flight mode and went to sleep, leaving it with about 70 percent of battery. The next morning it didn't turn on and when I connected it to the charger, it showed me an empty battery and started charging as usual.
However, I'm running the phone in stock with the latest official update (Jellybean 4.3.1 Yakju Maguro I guess) and I haven't done any custom changes like rooting, unlocking etc.
It's still possible to access ODIN mode and the bootloader. I tried with cache wiping and reboot system, but it didn't work.
I have important personal data on the phone, which I can hopefully recover. That's why I didn't try the hard reset yet.
My computer still recognizes the phone when I connect it via USB. It just doesn't show up in Windows Explorer, so I can't transfer any data this way.
If you have any idea, how to recover my data and to rescue my phone I would be really grateful.
Thanks for any help and advise.

Search up for Google factory images and try to reinstall using the guide on their page
Sent from my RCT6573W23

macromoto said:
Hello,
I've been searching for a while now to solve my problem, but I haven't found anything yet and hope that you might be able to help me here.
My Galaxy Nexus doesn't boot anymore, it get's stuck everytime on the "Google"-screen. I haven't done any updates or anything else. The last night it was working I just switched to flight mode and went to sleep, leaving it with about 70 percent of battery. The next morning it didn't turn on and when I connected it to the charger, it showed me an empty battery and started charging as usual.
However, I'm running the phone in stock with the latest official update (Jellybean 4.3.1 Yakju Maguro I guess) and I haven't done any custom changes like rooting, unlocking etc.
It's still possible to access ODIN mode and the bootloader. I tried with cache wiping and reboot system, but it didn't work.
I have important personal data on the phone, which I can hopefully recover. That's why I didn't try the hard reset yet.
My computer still recognizes the phone when I connect it via USB. It just doesn't show up in Windows Explorer, so I can't transfer any data this way.
If you have any idea, how to recover my data and to rescue my phone I would be really grateful.
Thanks for any help and advise.
Click to expand...
Click to collapse
I think it's in bootloop. Try flashing the stock ROM through fastboot using CMD.
It worked for me.

Android Wizard said:
I think it's in bootloop. Try flashing the stock ROM through fastboot using CMD.
It worked for me.
Click to expand...
Click to collapse
Do you have any links with further instructions for me?
How about my personal data on the phone? Is there still a chance to recover it when I use this method?
Thanks.

I'm still looking for a solution...
I tried to flash with wugfresh Nexus toolkit, but it's not possible since the bootloader is locked.
Is there any way to get access to my personal data such as pictures???