Related
Hi everyone. I have a samsung galaxy s vibrant on android 2.2. I am a total noob with any modifications but am going overseas next month and wanted to unlock my phone. After looking into rooting etc. I downloaded odin and darky's ROM resurrection edition. I followed the prompts to go into recovery and wipe etc. and remove battery and turn back on. After using odin and restarting my phone now just flashes the start screen showing galaxy s GT-I9000. I can't enter recovery mode just download mode. I'm unsure what to do and even tried mounting another recovery file on odin which lead me to the same point. Any help would be greatly appreciated.
Try re-flashing it and see if that works, sometimes that's all it takes. It's possible you just had a bad flash.
I've tried about 5 times now and it seems to keep failing to boot after flash and sticking on the initial boot screen and flashing on and off. Is there a way to download and flash an original ROM and mount on odin to start over?
Try getting into download mode. Hold and continue to hold up & down volume controls while holding in the power button. When the Vibrant logo comes up release only the power button. If you do get into recovery that way scroll down to install zip from sd card and install whatever rom you've got on there that you want to use. Let me know if that works or not.
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Spike84 said:
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Click to expand...
Click to collapse
Look for a hard surface... concrete for example.. now take your phone and throw it as hard as you can... Just kidding don't do that, that's a permanent reboot. I know the frustration, I've been there many times. You may want to go back and read through the noob guide, I'm not sure what else to suggest. Hopefully someone else will read this and have a better suggestion. Good luck.
haha yeah the thought crossed my mind. I appreciate your help. I'm still reading through the forum. Most instructions seem to require me to reach recovery mode or usb debugging. My phone is no longer being recognized on the computer but odin is obviously still recognizing so I'm going to try a fresh 2.2 on odin and see if that works.
Good luck, I'm rooting for ya. If that does not work and your close to a T-mobile store I'd just run it in and have them check it out, they may have to replace it.
Thanks again. I'm actually in Canada and using a sub provider from bell "virgin mobile".
hey everyone, im having a little trouble with my galaxy2.
its the canadian bell hd lte version, unrooted, running gingerbread 2.3.3. obviously i want to upgrade.
im comfortable with the rooting process using odin...etc.
heres my issue, ive done some looking but couldnt find anybody with the same issue or a solution.
upon attempting to enter download mode, with the phone off, using the vol down + home + pwr key, it does just that, totally skipping the "warning!" screen.
ive also found that odin will not recognize my phone, though the computer does, i am unsure if this is because of the bypass of the warning screen? maybe its time for a jig?
tldr phone will go into download mode, but odin will not recognize, no warning about custom os displayed.
thanks for looking.
Only reason I can think of for it not showing the warning screen before going directly into download mode is because you are holding down all the buttons for so long that it uses that as the "up" which it needs to go from the warning screen straight into download mode. *Like if you need to hold for 5 seconds to get into DL mode, try holding for 4.5 seconds so that you know it's booting into DL mode, but that you're certain you're not stilling holding down the UP button prematurely, so that it's going by the warning screen too quickly for you to notice -- if you really care enough at all*
What's most likely going on with ODIN not recognizing your device is that your Phone's Drivers has for some reason not installed correctly on your PC. That's not too rare of an occasion (happened to my brothers phone the other week when I tried to root it - wouldn't install drivers on my pc [thus not showing up in odin], so we had to use his computer (where they were already installed). What you can do (assuming this is the problem) is 1) Try using a different computer, and if you plug the phone in and the drivers do not start installing within the first minute and a half of connection then you can either look at the device option of windows (device and printer or w.e - see if there's an option for drivers, or uninstalling drivers [so that you can re-install] or something like that), or try downloading Kies (now used for official samsung updates), as I believe there is an option there to install your phone's drivers. Hope that helps, lemme know the results. I'm like 80% sure the problem you're having is the Drivers not being installed proplery on the comp.
dub_lyfe said:
hey everyone, im having a little trouble with my galaxy2.
its the canadian bell hd lte version, unrooted, running gingerbread 2.3.3. obviously i want to upgrade.
im comfortable with the rooting process using odin...etc.
heres my issue, ive done some looking but couldnt find anybody with the same issue or a solution.
upon attempting to enter download mode, with the phone off, using the vol down + home + pwr key, it does just that, totally skipping the "warning!" screen.
ive also found that odin will not recognize my phone, though the computer does, i am unsure if this is because of the bypass of the warning screen? maybe its time for a jig?
tldr phone will go into download mode, but odin will not recognize, no warning about custom os displayed.
thanks for looking.
Click to expand...
Click to collapse
Seems a little odd that it's skipping the warning but don't think it's a big issue.
As for the drivers I would suggest downloading the latest Kies software and installing any updates that should install all necessary drivers
I would then reboot computer and not launch Kies or anything else before opening Odin, Whenever I flash my phone I always run Odin from a fresh reboot just so I know that Kies isn't running or anything else to interfere with flashing process.
*Make sure Kies isn't running in the background when flashing things in Odin or strange things happen and flashing can get interrupted leading to possible bricked device.*
Also make sure USB debugging is enabled on your phone when you use Odin.
thanks for the reaponses!
it is wierd that its skipping the warning.
if a person puts the phone in dl mode, and at the warning screen chooses no, what happens? does the phone still go into dl mode or just reboot?
as for odin i cant check at the moment but ill try that, i have a feeling that the warning may have something to do with it, if someone wants to try to confirm my suspicions above?
will get back on the odin issue when i get a chance.
"ive done some looking but couldnt find anybody with the same issue or a solution." ... then look harder.
yea download the kies drivers or install a temporary cwm on your phone and go through that.
still have yet to get to a computer but messed with the device a bit.
it boots in recovery fine, still no warning for download mode.
also, if i dont continue to hold the dl mode button sequence till it goes straight into.dl.mode, the phone boots as normal.
so the theory of holding the buttons too long seems unlikely.
dub_lyfe said:
still have yet to get to a computer but messed with the device a bit.
it boots in recovery fine, still no warning for download mode.
also, if i dont continue to hold the dl mode button sequence till it goes straight into.dl.mode, the phone boots as normal.
so the theory of holding the buttons too long seems unlikely.
Click to expand...
Click to collapse
Alright I mean if you can get into recovery mode at this point (and download mode seems to work anyway, just doesn't give warning) shouldn't be a problem. If you do try getting the drivers from kies and use download mode then you can figure out if it's bonkers. If not, just use recovery to flash something and all should be well. That's quicker and easier anyway
Also, you should probably note that since you said you have the "canadian bell hd lte version", that you PROBABLY do not have a GT-I9100. So don't go flashing random stuff from the forum (which is for the I9100) - else I can almost guarantee you will run into problems.
(refer to this article, and this post)
If you are right about having the HD LTE version of the Galaxy S II, I'm betting you actually have the SGH-I757M. (you can verify this by looking on the label under the battery)
That phone (the SGH-I757M) doesn't have a dedicated forum, unfortunately. Your best bet is to search XDA for that model number, like this.
I was feeling generous, so I did a bit of legwork for you. The current latest Samsung official version is still 2.3.6. You can get it from sammobile.com. That will offer only minor updates from your current version of 2.3.3.
There IS the CyanogenMod9 custom ROM for your device, if you want to go that route. It'll be listed on the xda site search for your model number that I linked above.
In any case, I must warn you again against flashing anything that is meant for the i9100 Galaxy S II.
EDIT to add: the fact that the model is different from an I9100 could also explain the lack of a warning screen before download mode. There was no warning screen on my girlfriend's old Captivate prior to download mode, so maybe there isn't one on the SGH-I757M, either.
So, like everyone else, I rooted my phone and decided I dont need all this bloatware and other nonsense system apps.
I was foolish enough not to back up things I were removing, and nothing SEEMED important, but all of the sudden my "Htc dialer": Has stopped working.
My phone will turn on, but I cant turn it off, it just reboots without actually turning the phone off when I hold the power down.
I cant get it into recovery mode ( power vol up) and when it turns on, it goes to the default lock screen the phone comes with, and then I CANT see my home screen at all. The home button doesnt work either.
I cant get to my apps, I have to use my girlfriends DNA to beam whatever app im trying to get to onto my phone.
I can go to settings, but cant factory reset.
I tried killing the battery to get power it off, but then cant get to recovery screen there either.
I'm not sure if anyone has the system apps apk's just laying around so I can attempt to repair my phone, ( my girlfriend wont let me root her phone, but thatll be the next step if no one can help) but any insight as to what I can do would be appreciated.
Try fastboot flashing recovery and then dirty flashing the rom you were on before you started deleting things. This may help you keep your rom setup. If this doesn't work then go to the moonshine thread run the ruu and start from scratch.
xiastro1ix said:
So, like everyone else, I rooted my phone and decided I dont need all this bloatware and other nonsense system apps.
I was foolish enough not to back up things I were removing, and nothing SEEMED important, but all of the sudden my "Htc dialer": Has stopped working.
My phone will turn on, but I cant turn it off, it just reboots without actually turning the phone off when I hold the power down.
I cant get it into recovery mode ( power vol up) and when it turns on, it goes to the default lock screen the phone comes with, and then I CANT see my home screen at all. The home button doesnt work either.
I cant get to my apps, I have to use my girlfriends DNA to beam whatever app im trying to get to onto my phone.
I can go to settings, but cant factory reset.
I tried killing the battery to get power it off, but then cant get to recovery screen there either.
I'm not sure if anyone has the system apps apk's just laying around so I can attempt to repair my phone, ( my girlfriend wont let me root her phone, but thatll be the next step if no one can help) but any insight as to what I can do would be appreciated.
Click to expand...
Click to collapse
Honestly I don't know where to begin with your post. Its all over the place. The phone turns off by holding the power button for 10 seconds and waiting for the capacitive buttons to stop flashing. If your phone turns on its really not possible for this NOT to work. Yes it will reboot this is normal, though once the lights stop blinking you can quickly hold volume down and power to access boot loader and power down fully from there. Recovery is accessed from bootloader too assuming you have one installed. A lot can be done from both bootloader and recovery to solve problems so finding out if you can access them is the first step. I don't understand your statement about the default lock screen showing and you can't see your home screen. Which ROM is it? Which lock screen are you referring to? Why can't you simply unlock the phone? What is stopping you from doing that? Your home button doesn't work and you can't get to your apps...meaning? You can't access the app drawer? I thought you couldn't unlock the device there is conflicting info there. I don't see how you are beaming tasks one at a time through this painful process but I would just avoid that until you've fixed the problem. You can access settings but no factory reset, why? What can you do from settings? And finally you are asking for some apk's "just lying around".....dude your issues seem severe, obviously you are inhibited from using your phone right now but someone giving you some apps won't solve your problem in fact it would probably make it worse. Get into recovery perform a full wipe and flash a different ROM. Also don't mess with deleting apps if your not sure it might screw up your system.
xlxcrossing said:
Honestly I don't know where to begin with your post. Its all over the place. The phone turns off by holding the power button for 10 seconds and waiting for the capacitive buttons to stop flashing. If your phone turns on its really not possible for this NOT to work. Yes it will reboot this is normal, though once the lights stop blinking you can quickly hold volume down and power to access boot loader and power down fully from there. Recovery is accessed from bootloader too assuming you have one installed. A lot can be done from both bootloader and recovery to solve problems so finding out if you can access them is the first step. I don't understand your statement about the default lock screen showing and you can't see your home screen. Which ROM is it? Which lock screen are you referring to? Why can't you simply unlock the phone? What is stopping you from doing that? Your home button doesn't work and you can't get to your apps...meaning? You can't access the app drawer? I thought you couldn't unlock the device there is conflicting info there. I don't see how you are beaming tasks one at a time through this painful process but I would just avoid that until you've fixed the problem. You can access settings but no factory reset, why? What can you do from settings? And finally you are asking for some apk's "just lying around".....dude your issues seem severe, obviously you are inhibited from using your phone right now but someone giving you some apps won't solve your problem in fact it would probably make it worse. Get into recovery perform a full wipe and flash a different ROM. Also don't mess with deleting apps if your not sure it might screw up your system.
Click to expand...
Click to collapse
Alright let me try to be a little more descriptive.
So as for the lock screen, I can unlock the screen, but then I see a black screen, no home page/icons. I cant get into the app drawer, when i try to factory reset, it says "rebooting" for a few seconds, screen turns off, right back on to lock screen, sim card says preparing, and then i'm back to where i was, doesnt actually reset. As for the beaming, I can say, open system app remover or file viewer on my girlfriends phone, then beam it, and my phone will open the corresponding app. This is the only way I can get apps to open, since I can't get to drawer or go to home screen.
When I hold down the power button down, the buttons flash, I get a message saying " continue to hold for 3 seconds" it counts down to 1, and then nothing. I can hold it til my arm falls off, nothing at all happens when it hits 1, I also can't power the phone down. If i try to, the screen goes black, capactive buttons turn white, back to lock screen and phone does " preparing sim" and the network/wifi reconnect as if it was just rebooted.
I have the default rom the phone came with, I believe I have a bootloader, I used a guide from this site to perform my root. The folder I have contains distiller, dnashellroot.apk, boot_secure, busybox, su and superuser.apk
dude your issues seem severe, obviously you are inhibited from using your phone right now
Click to expand...
Click to collapse
The weird part is, other then not being able to turn it off/get into drawer/see home screen, everything else works. If i get a text, i can drag down and select it and it opens. If i open gmail on my GF's phone and beam it, will open Gmail and function 100%. Same goes for any app we both have that I beam.
I just used my rooting method to force bootloader up, which worked, but when i hit recovery, im looking at a picture of a phone laying down with a orange triangle/exclamation point in the center of it.
xiastro1ix said:
The weird part is, other then not being able to turn it off/get into drawer/see home screen, everything else works. If i get a text, i can drag down and select it and it opens. If i open gmail on my GF's phone and beam it, will open Gmail and function 100%. Same goes for any app we both have that I beam.
I just used my rooting method to force bootloader up, which worked, but when i hit recovery, im looking at a picture of a phone laying down with a orange triangle/exclamation point in the center of it.
Click to expand...
Click to collapse
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
mushroomhead13xx said:
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
Click to expand...
Click to collapse
I can get into bootloader, i tried recovery, i get a verizon screen bootloader but just resets phone after a few minutes.
At my friends suggestion i just got TWIP installed and now i'm just waiting to see what she suggests next. I figured out thanks to my advance app killer I can get to the play store whenever i need to, and then open any apps i've installed through there. Stupid work around, but hey, it works lol.
xiastro1ix said:
I can get into bootloader, i tried recovery, i get a verizon screen bootloader but just resets phone after a few minutes.
At my friends suggestion i just got TWIP installed and now i'm just waiting to see what she suggests next. I figured out thanks to my advance app killer I can get to the play store whenever i need to, and then open any apps i've installed through there. Stupid workout, but hey, it works, lol.
Click to expand...
Click to collapse
Well if you just got TWRP installed via fastboot or goo manager you should be pretty well set. Download a new ROM, reboot into recovery and install. I would suggest wiping the davik and cache - possibly even the system just to give you a fresh start.
mushroomhead13xx said:
Ok - fact of the matter is that you might want to try getting into recovery via the bootloader (vol down + power from off). If you can access the recovery module from there, you are then able to click advanced (using TWRP) then click sideload. You will then need to use ADB to sideload a new ROM onto the phone, then install via TWRP. Hopefully you might even still have the old .zip for the current ROM that you're using and just really need to get to recovery.
Click to expand...
Click to collapse
mushroomhead13xx said:
Well if you just got TWRP installed via fastboot or goo manager you should be pretty well set. Download a new ROM, reboot into recovery and install. I would suggest wiping the davik and cache - possibly even the system just to give you a fresh start.
Click to expand...
Click to collapse
So far Ive used goo to get twrp installed and now we are working on getting sense 5 working.
Appreciate all the input, might be getting somewhere finally lol.
xiastro1ix said:
So far Ive used goo to get twrp installed and now we are working on getting sense 5 working.
Appreciate all the input, might be getting somewhere finally lol.
Click to expand...
Click to collapse
I highly suggest NOS M7 Sense 5 Build ( http://forum.xda-developers.com/showthread.php?t=2184706 ) - Absolutely stunning at how well it works. I just switched from that to the GPE port from NOS M7 as well. Good work on getting somewhere, I remember the days of IDK WHAT IM DOING OMG WHAT IS THE ADB ...FASTBOOT..... UGH WHATS WITH THIS VERIFICATION ERROR! lol
mushroomhead13xx said:
I highly suggest NOS M7 Sense 5 Build ( http://forum.xda-developers.com/showthread.php?t=2184706 ) - Absolutely stunning at how well it works. I just switched from that to the GPE port from NOS M7 as well. Good work on getting somewhere, I remember the days of IDK WHAT IM DOING OMG WHAT IS THE ADB ...FASTBOOT..... UGH WHATS WITH THIS VERIFICATION ERROR! lol
Click to expand...
Click to collapse
[ROM] Sense 5 M7 Digital Dream ROM v2.1 7/30/13
Im actually all set, i got the phone up and working on this rom, and now im SAFELY using the list below to delete all the apps I dont want.
http://forum.xda-developers.com/showthread.php?p=34704106
This rom kicks ass, i cant believe i stayed with default rom all this time to begin with, turned a bad situation into a much better one
Love XDA so much, this sites a life saver. The first thing that came into mind when I bricked it was, Yep, time to hit XDA.
xiastro1ix said:
[ROM] Sense 5 M7 Digital Dream ROM v2.1 7/30/13
Im actually all set, i got the phone up and working on this rom, and now im SAFELY using the list below to delete all the apps I dont want.
http://forum.xda-developers.com/showthread.php?p=34704106
This rom kicks ass, i cant believe i stayed with default rom all this time to begin with, turned a bad situation into a much better one
Love XDA so much, this sites a life saver. The first thing that came into mind when I bricked it was, Yep, time to hit XDA.
Click to expand...
Click to collapse
Absolutely! I first started out on XDA when I got my first android phone; MyTouch 3g (HTC Magic). I then took my tinkering to full fledged modding where I was charging to overclock, root and unlock phones. It used to be fairly profitable, now there's one click steps for everything. Glad you were able to figure it out instead of having to take it to someone! Good work!
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
Hi, I've been browsing the forums for people's attempts to fix a problem. At first the phone just turned off and I was unable to turn it on because it was stuck in a boot loop. The rom I had running was an ICS stock rom from hk. During this time i was still able to get into download mode but unable to enter recovery. I have tried many times to get to recovery and then tried to flash with several stock roms too. Upon failing around 10 times I moved on to a custom rom.
This one here:
http://forum.xda-developers.com/galaxy-s2/help/guide-26-12-flash-stock-firmware-rom-t2365701
The Jelly bean one here.
Upon failing from this too and unable to do anything but reset the phone and try again. I managed to turn it off... but now unable to turn it on in any way or get into download mode or recovery.
Is there anything I can try to do to get the phone to be working? What can I do?
Try a jig but understand it's very unlikely to get you into download mode. Service centre or local mobile repair shop for diagnosis (I also doubt it will be JTAG'able).
Edit - Also, search for KingRat's 'jump start' method where you try & boot the phone with just the charger/without the battery.
medow70 said:
Hi, I've been browsing the forums for people's attempts to fix a problem. At first the phone just turned off and I was unable to turn it on because it was stuck in a boot loop. The rom I had running was an ICS stock rom from hk. During this time i was still able to get into download mode but unable to enter recovery. I have tried many times to get to recovery and then tried to flash with several stock roms too. Upon failing around 10 times I moved on to a custom rom.
This one here:
http://forum.xda-developers.com/galaxy-s2/help/guide-26-12-flash-stock-firmware-rom-t2365701
The Jelly bean one here.
Upon failing from this too and unable to do anything but reset the phone and try again. I managed to turn it off... but now unable to turn it on in any way or get into download mode or recovery.
Is there anything I can try to do to get the phone to be working? What can I do?
Click to expand...
Click to collapse
Don't loose hope mate...
Try remove battery and insert charger (optional)...
Press voldown+home+power button then let someone (your mother, father, brother, sister, neighbor or friends) insert the battery for you while still pressing those 3 keys...
I hope it will enter to download mode again...and report back please...
Try to use an other battery, my original one is fuked up, it does nothing.
I bought a new one and it works
I tried plugging my charger to the phone and pressing the 3 buttons and then having someone plug the battery in for me, still wouldn't start up. Also tried it with another battery i have on hand, also no luck.
You know what the options are then. Ignore people making ridiculous suggestions which don't work. My aim is to be honest with people, tell them the truth, and have them either get their phones fixed or replaced as quickly as possible in this situation (let's face it, nobody likes to be without a phone), rather than fill them with false hope & waste their time.
I think I fried my mobo while trying to flash it cause it does head up the phone without showing anything. I am going to order parts on ebay. I got this confirmed by someone at a shop near where I live, however they won't replace the mobo for me even if i do find a working one.
=) luckily this isn't my phone but my dad's who works at home and doesn't mind using an OLD OLD flip phone just for calls for the time being.
Side question, even if i replace the mobo and I get it booted but I still get stuck in the boot screen loop and unable to flash to any stock roms what can I do?
If you replace the motherboard you should fix it without further problems. New motherboard = new NAND, no more bootloop - unless you flash again & the flash is bad; you can't mitigate the risk of a bad flash, you can only do all the sensible things like making sure you're using a PC with reliable USB ports, that you're flashing the correct firmware for your device, that you're using an original Samsung USB cable. Basically, if you're careful, the risk with any given flash is very low.
So, fix the hardware problem, flash stock for your country/carrier once you've done that, and go from there.