[Q] How do I Unbrick a Samsung Conquer? SPH-D600 - General Questions and Answers

How do I unbrick a Samsung Conquer? Model SPH-D600, FE16 stock firmware, unmodified. I was unsuccessful obtaining root with Super One Click or the root exploit for Evo 4G which purportedly works (SPH-D710.FE16_CL579416_ROOTED-oc-sfx.exe). My phone worked fine after trying these 2 methods, but the root would never take.
Next I tried the Odin method from the files upped to this thread: [ROM] Custom Stock Samsung Conquer 4G FC17 Rooted With Tweaks
I downloaded both .rar archives to extract valid files. I followed the instructions in the included text file, puting my phone in download mode, loading the 2 files in Odin, and pressing the start button (easy, right?). After letting Odin run for several minutes, it hung on step 5/8, and the Odin program closed, but my phone remained in download mode. I couldn't get my phone to respond to any keys, so my only choice was to remove the battery. Now the phone will not power on. No bootloader, no response at all. Please help!

Hey bro what's the screen look like at the moment cause I done a very similar thing and I soft bricked my phone when I used ordinary the first time because odin closed so I pulled the USB cord out and then I softball bricked it. If its a computer then,? Triangle then Android guy on your screen then you have soft bricked it and I'll be able to have lip you fix it.
And remember do not panic as that's when you really screw stuff up.
Sent from my YP-G70 on ics using xda premium

Evoium said:
Hey bro what's the screen look like at the moment cause I done a very similar thing and I soft bricked my phone when I used ordinary the first time because odin closed so I pulled the USB cord out and then I softball bricked it. If its a computer then,? Triangle then Android guy on your screen then you have soft bricked it and I'll be able to have lip you fix it.
And remember do not panic as that's when you really screw stuff up.
Click to expand...
Click to collapse
I can't get anything to show on the screen at all. No lights come on or anything.

Can you get into clockworkmod?
By holding up volume key + menu key + power key.
If yes, when you get into clockworkmod wipe data cache and do a factory reset.
Then power down or switch your mobile and then enter into download mode and use odin to flash your desired GB Rom.
Hope this solves your problem.

Once I realized it was't even responding to the charger, I knew it must be dead. I tried several button combos, and I spoke with my carrier's tech support who suggested other methods. This phone is hard-bricked with a capital B. I'm just have to deal with getting a new phone. At least the Credo people are pretty nice about discounts.

hollacoast said:
Once I realized it was't even responding to the charger, I knew it must be dead. I tried several button combos, and I spoke with my carrier's tech support who suggested other methods. This phone is hard-bricked with a capital B. I'm just have to deal with getting a new phone. At least the Credo people are pretty nice about discounts.
Click to expand...
Click to collapse
My samsung screen loads then the warning a custom os can cause critical problems in phone are. is it bricked oh no!

Related

I think Kies just bricked my phone...

My phone is a SGH-i896, Samsung Galaxy S Captivate from Rogers,
I am extremely frustrated. My phone isn't rooted. I recently found out my phone was available for a 2.2->2.3 update so I decided to do it.
I downloaded Kies and connected my phone to the computer. Kies picked it up and told me to initiate the update. I did. After a while it told me there was an "error" with the update and I'd have to do an emergency firmware repair... what the hell? I proceeded to do what it asked me to do an emergency repair, but even that failed and it told me to "try again later"...
So, I tried "again later" but this time instead of getting the digger android I when I initiated the recovery mode (Hold volume up+down and connect the USB) I get the "phone-!-computer" screen. Now I'm stuck like this.
I searched around and someone said if you hold volume up+down and then hold power, and then when you see the BSOD, and it flashes, release power and it should boot up in download mode... but when I attempt there it just flashes then goes back to the BSOD.
What are my options to fix the phone aside from going to a service center and most likely having to send it in for repair?
Kies broke my phone. Ugh.
Vinhwut said:
My phone is a SGH-i896, Samsung Galaxy S Captivate from Rogers,
I am extremely frustrated. My phone isn't rooted. I recently found out my phone was available for a 2.2->2.3 update so I decided to do it.
I downloaded Kies and connected my phone to the computer. Kies picked it up and told me to initiate the update. I did. After a while it told me there was an "error" with the update and I'd have to do an emergency firmware repair... what the hell? I proceeded to do what it asked me to do an emergency repair, but even that failed and it told me to "try again later"...
So, I tried "again later" but this time instead of getting the digger android I when I initiated the recovery mode (Hold volume up+down and connect the USB) I get the "phone-!-computer" screen. Now I'm stuck like this.
I searched around and someone said if you hold volume up+down and then hold power, and then when you see the BSOD, and it flashes, release power and it should boot up in download mode... but when I attempt there it just flashes then goes back to the BSOD.
What are my options to fix the phone aside from going to a service center and most likely having to send it in for repair?
Kies broke my phone. Ugh.
Click to expand...
Click to collapse
In your case, try (from a powered-off state) holding Vol+/Vol-, and then plug in your USB cable. That should kick you to download mode. If you still get the phone--!--pc screen, just try flashing from there. As far as ODIN and other programs are concerned, that's download mode.
jmtheiss said:
In your case, try (from a powered-off state) holding Vol+/Vol-, and then plug in your USB cable. That should kick you to download mode. If you still get the phone--!--pc screen, just try flashing from there. As far as ODIN and other programs are concerned, that's download mode.
Click to expand...
Click to collapse
Doing this still shows the phone--!--pc screen... I've tried tons of combinations and fiddling around with it but nothing works it seems.
Vinhwut said:
Doing this still shows the phone--!--pc screen... I've tried tons of combinations and fiddling around with it but nothing works it seems.
Click to expand...
Click to collapse
Just so we can give you clear directions, at the end of this, where do you want to be? On the stock rom, on a custom rom, Froyo, Gingerbread, etc? The steps to do those different things will vary what you need to do.
As a first step in all of those, though, you'll need to use either Heimdall or Odin to flash your phone, and you should have the Samsung drivers downloaded and installed (if you haven't already).
I want to be able to upgrade it to 2.3 more or less. If that's not possible, just to get my phone back in working condition... I'm close to calling Rogers to see what they can do if I can't figure this out on my own.
I guess I'll look up some information on Heimdall/Odin then about flashing (I really have limited knowledge in this area) - will doing any of this void my warranty?
Vinhwut said:
I want to be able to upgrade it to 2.3 more or less. If that's not possible, just to get my phone back in working condition... I'm close to calling Rogers to see what they can do if I can't figure this out on my own.
I guess I'll look up some information on Heimdall/Odin then about flashing (I really have limited knowledge in this area) - will doing any of this void my warranty?
Click to expand...
Click to collapse
I was hoping that would be your response. Go to this thread. TRusselo whipped up a bunch of Odin one-clicks to get you back to stock Rogers packages, one of which is called "2.3.3 Gingerbread WITH bootloaders" (you can CTRL+F for that exact phrase). That should get you back to a working state.
Just make sure you don't pull out the cable or lose power while you're using it. That would guarantee you'll end up having to send it back.
And technically, it will and won't void your warranty. Flashing anything but stock stuff directly from Rogers probably voids it, but if this works properly, it's going to look exactly the same as if they did it, so you should be fine.
Thanks jm, I'll give this a try and post my results
Good luck. Just make sure to read the directions very carefully - it should be pretty self-explanatory, but it's better to be as safe as possible.
All fixed following jmtheiss' instructions! Thanks plenty!
Glad to hear you are back up and running Vinhwut. And jmtheiss, you provided clear instructions to get him there. That's how help should be given.

Reviving the Samsung Galaxy S 4G

I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!

[Q] Accidental Update, Now Frozen - Please Help

This morning in my half-awake state I accidentally pressed "OK" to my phone asking me to go ahead with the (I'm guessing) 2.3.6 update. I KNEW I would end up doing something stupid like that. GRR!!
Anyway, the phone then launched itself into a white screen with blue text saying that it is doing the update, but nothing happens and it appears to be frozen.
I am rooted and was trying to avoid this update; like I said, I was half-awake.
I can't even get it to boot into download/recovery mode, it always goes straight to the white screen. Hopefully this isn't a double post; I checked here and google first but couldn't find anything for this phone. I'm really at a loss here. I have Titanium Backup and I got an external SD card, but I'm not sure if I actually backed up the apps to the external card (new to TB). I did a Kies contacts backup a few days ago so that at least is safe.
Is there any hope for my phone? If I can just get it back to a working state, I can live with my apps' data being erased. Any help appreciated.
Thank you!
Doh... sorry to hear that.. are you also running a custom rom, or customized ATT rom (I have the stock rom from the developers forums over the standard root after having tried a few custom roms).
I got the update message as well this morning, but I postponed it for 8 hours, however I am unable to get rid of the stupid notification, and am curious if after the 8 hours, it will force the update or let me postpone it agian (that will get annoying fast if I cannot disable the OTA update..)
I'd like to know how to cancel the update as well. I have it sitting in my notification bar. >_<
jvanbrecht said:
Doh... sorry to hear that.. are you also running a custom rom, or customized ATT rom (I have the stock rom from the developers forums over the standard root after having tried a few custom roms).
Click to expand...
Click to collapse
I'm still running stock 2.3.5. All I've had time to do is root and TB apps, haven't had the chance to play around with ROMs yet for this phone.
Yeah I postponed it for 8 hours, too. The 8hrs must have expired right as my alarm went off because the "Install this update?" message popped up and I hit it, thinking it was the snooze button -_-
Let me know if there's any way to get off of this screen my phone is stuck on! And then disable the obnoxious message for good.
Thanks again =)
Maybe try to remove battery.
lyndone58 said:
Maybe try to remove battery.
Click to expand...
Click to collapse
I have about 10-15 times since it first happened this morning. I also tried taking out the SIM and microSD cards. It's the only way I can get it to stay off to try to boot to recovery mode (which it still won't boot into); if I hold the power button to turn it off it just resets back into the white Software Update Screen (won't stay off).
Has anyone successfully applied this update yet?
Any other ideas? I appreciate the feedback so far!
Similar thing happened to me. I pulled the battery and booted in to CWM just fine. Restored from there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
I don't believe I have CWM installed? How would I have known if I did? When I volume up + volume down + power and wait until the Samsung logo comes up it boots back to the white screen. Maybe I'm doing that process wrong?
Same thing happened to me this morning!
almost identical story
I've tried literally every combination to get to the reboot screen. ugh :'(
mrl3086 said:
I have about 10-15 times since it first happened this morning. I also tried taking out the SIM and microSD cards. It's the only way I can get it to stay off to try to boot to recovery mode (which it still won't boot into); if I hold the power button to turn it off it just resets back into the white Software Update Screen (won't stay off).
Has anyone successfully applied this update yet?
Any other ideas? I appreciate the feedback so far!
Click to expand...
Click to collapse
I haven't been rooting as much as some of the guys here, but I think if you take the battery out and it won't boot back even into recovery, you're hard-bricked and you're gonna have to start from scratch with a fresh stock rom. Go to download mode (turn off, hold vol up + down, insert powered usb cable) and put a stock rom back on using odin.
http://forum.xda-developers.com/showthread.php?t=1342348
You will basically get back to what your phone was when you took it out of the box and you'll have to install everything, your data (other than the data that is on a microSD card) won't be there.
If you have a backup that you did with CWM, then you can restore the backup after you do all this.
I think you got unlucky with the worst case scenario of what shouldn't happen during an update.
Thanks for the advice. I'll give it a try when I get home from work and will let you guys know how it goes.
For the future, is it generally recommended to de-root before doing any straight carrier update? Or is this just a total fluke that some of us are experiencing?
Will adb recognize your phone? If it does just adb reboot recovery
Sent from my SAMSUNG-SGH-I727 using xda premium
Lucidmike said:
I haven't been rooting as much as some of the guys here, but I think if you take the battery out and it won't boot back even into recovery, you're hard-bricked and you're gonna have to start from scratch with a fresh stock rom. Go to download mode (turn off, hold vol up + down, insert powered usb cable) and put a stock rom back on using odin.
http://forum.xda-developers.com/showthread.php?t=1342348
You will basically get back to what your phone was when you took it out of the box and you'll have to install everything, your data (other than the data that is on a microSD card) won't be there.
If you have a backup that you did with CWM, then you can restore the backup after you do all this.
I think you got unlucky with the worst case scenario of what shouldn't happen during an update.
Click to expand...
Click to collapse
AMAZING!! Thank you so much! Not only is my phone up and working but the update has installed!
I learned the following:
-you pretty much need a pc (not a mac) to do all the downloads correctly. I used a friends.
-to get your phone into download mode when it's frozen from the update, you have to hold down either vol + AND vol - (or just vol -) as well as the power button, simultaneously hold down power and also simultaneously plug in the usb. Then let go of the power button and remain holding down one or the two volume buttons.
THIS WAS JUST WITH MY SKYROCKET EXPERIENCE
I'm so happy. Thank you LucidMike
This just happened to my friend's phone. White screen no matter what. Stock everything, too. She's pretty bummed that there's no way to recover the videos and pictures on her phone before resetting it. Apparently she went to AT&T and they couldn't figure it out. They called tech support for her and THEY couldn't figure it out. She's currently on the phone with Samsung, but I doubt they'll be able to help either.
viralriot said:
This just happened to my friend's phone. White screen no matter what. Stock everything, too. She's pretty bummed that there's no way to recover the videos and pictures on her phone before resetting it. Apparently she went to AT&T and they couldn't figure it out. They called tech support for her and THEY couldn't figure it out. She's currently on the phone with Samsung, but I doubt they'll be able to help either.
Click to expand...
Click to collapse
AHHH!! Tell her to hang up the phone right now!! Use this method to fix her phone!! All of her data will still be there after it's done! After the process is complete, back it up to a computer (enable USB storage and just copy + paste and I used Kies to copy my contacts) and THEN do a full factory reset (reset recommended by everyone to ensure smooth function of phone). The method in the link will return her to the original stock version; I believe it may trip a counter that AT&T can use to determine if you've hacked your phone, but if you want a working phone...and there's also a chance that it WON'T trip the counter (some people say it did and some say it hasn't).
EDIT: Pictures and videos that I took with the phone are saved in /sdcard/DCIM/Camera, so you know where to copy her stuff from.
jessielooloo said:
AMAZING!! Thank you so much! Not only is my phone up and working but the update has installed!
I learned the following:
-you pretty much need a pc (not a mac) to do all the downloads correctly. I used a friends.
-to get your phone into download mode when it's frozen from the update, you have to hold down either vol + AND vol - (or just vol -) as well as the power button, simultaneously hold down power and also simultaneously plug in the usb. Then let go of the power button and remain holding down one or the two volume buttons.
THIS WAS JUST WITH MY SKYROCKET EXPERIENCE
I'm so happy. Thank you LucidMike
Click to expand...
Click to collapse
I'm trying to fix my boyfriend's phone (he actually didn't hack/root it or anything...but yesterday's update messed up his phone so it was stuck in the "SOFTWARE UPDATE" and "Loading..." frozen white screen). We tried taking out the battery, restarting it, everything. I tried your method of holding all three buttons while plugging in the USB and then letting go of the power button. What do you press when it asks you if you want to continue (up vol +) or cancel (vol -)? I chose vol -, and when it took me back to the white screen, I did it again and pressed vol +. Now I'm on a ODIN MODE page...will this affect his warranty or anything? What do I do next?
You need to have odin on your pc and the stock .tar and flash it. Here go here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1509978
Read carefully follow directions exactly
silver03wrx said:
You need to have odin on your pc and the stock .tar and flash it. Here go here http://forum.xda-developers.com/showthread.php?goto=newpost&t=1509978
Read carefully follow directions exactly
Click to expand...
Click to collapse
Thanks! I read on the first page of the thread that it needs to be rooted though? This phone is brand new and never been rooted or hacked...will doing this void the warranty or anything unpleasant? (I'm the one that likes hacking my devices like my Nook Color...my boyfriend is a little more paranoid and would rather have it stay covered under warranty )
No actually. Thats incorrect..the stock tar. Is just as it sounds. The stock firmware the phone comes with.....dont need to be rooted to use odin. Actually if u odn the stock tar. It removes root.
mrl3086 said:
AHHH!! Tell her to hang up the phone right now!! Use this method to fix her phone!! All of her data will still be there after it's done! After the process is complete, back it up to a computer (enable USB storage and just copy + paste and I used Kies to copy my contacts) and THEN do a full factory reset (reset recommended by everyone to ensure smooth function of phone). The method in the link will return her to the original stock version; I believe it may trip a counter that AT&T can use to determine if you've hacked your phone, but if you want a working phone...and there's also a chance that it WON'T trip the counter (some people say it did and some say it hasn't).
EDIT: Pictures and videos that I took with the phone are saved in /sdcard/DCIM/Camera, so you know where to copy her stuff from.
Click to expand...
Click to collapse
Tried doing this, but this is all I get.
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/006> Added!!
That's it. Nothing else happens. Help?
EDIT: Nevermind! Plugged it into a different USB port (COM:6) and it worked flawlessly. All data is still on phone and it works like new! Thank you!

[Q] Beyond Bricked my infuse

Hey there, apologies in advance if I have submitted this thread in the wrong section. I really looked as hard as I could before posting.
Well I rooted my phone, got super user on there, then got clockworkmod red, and then attempted to put the ice cream sandwich mod on my phone, thats where everything went sour. Phone would not go past screen that says samsung. I tried a few times to get it to go past that point, and just nothing. I then attempted to use odin to have my phone put back, but now I cannot even get the phone to open up clockworkmod.
To put it very simply. The only thing I have access to now is the download option (holding both volume up and down while inserting the usb cable from the computer) I have searched the internet high and low for something to run through odin to put my phone back to the way it was. I keep coming up with dead links and long dead downloads. I was able to use the gtg ultimate unbrick, but all that managed to accomplish was to have my phone say at&t instead of rogers.
Im still at the screen that says samsung, with no access to a recovery menu at this point. I only have the download option.
Can anyone help me salvage my phone?
edit: I appear to have been able to reput clockworkmod back on the phone with odin. Thats all I have been able to do.
When flashing any ics Rom/port from.gingerbread/red recovery you will need to double flash...I'm seeing a lot of people.with bricks lately and I think the problem is they are not reading enough before flashing ics...
So you have cwm correct? Boot into cwm by holding volume up down and power button. If you have no roms hen go to mounts and storage and mount USB then plug it into the pc and copy over the Rom...if its gingerbread Rom.just one flash...if its ics then flash, you will get stuck on Samsung screen so boot back into cwm...you will either boot into a blue or some distorted rainbowy cwm...just reflash he Rom
If you can't do that...then idk what else to do as I don't know much about rogers phones and what is and isn't compatible with them...but u would suggest qksters heimdal one click back to stock uclb3...its always worked for me...but not sure if it will work with rogers...
Sent from my HTC PH39100 using XDA
Mytheos said:
Hey there, apologies in advance if I have submitted this thread in the wrong section. I really looked as hard as I could before posting.
Well I rooted my phone, got super user on there, then got clockworkmod red, and then attempted to put the ice cream sandwich mod on my phone, thats where everything went sour. Phone would not go past screen that says samsung. I tried a few times to get it to go past that point, and just nothing. I then attempted to use odin to have my phone put back, but now I cannot even get the phone to open up clockworkmod.
To put it very simply. The only thing I have access to now is the download option (holding both volume up and down while inserting the usb cable from the computer) I have searched the internet high and low for something to run through odin to put my phone back to the way it was. I keep coming up with dead links and long dead downloads. I was able to use the gtg ultimate unbrick, but all that managed to accomplish was to have my phone say at&t instead of rogers.
Im still at the screen that says samsung, with no access to a recovery menu at this point. I only have the download option.
Can anyone help me salvage my phone?
edit: I appear to have been able to reput clockworkmod back on the phone with odin. Thats all I have been able to do.
Click to expand...
Click to collapse
If u can get to dl ur fine
Sent from my SAMSUNG-SGH-I717 using xda premium
http://forum.xda-developers.com/showthread.php?t=1331381
Use this link/program from download mode to get to stock 2.3.6.
Wait, if you can get to download mode, you can reflash JScott's option C from here, then get into CWM red, flash the ICS of your choice, reboot into CWM blue (press and hold vol up/vol dn/power 5 seconds when stuck at sammy screen), wipe data/cache/dalvik, reboot and you should have ICS.
I understand that some people will never get "it", but reading the entire post for flashing/modding firmware is a MUST.

[Q] Boot Loop with no recovery mode

Ok so I'm new to the thread and basically to android tablets, so please forgive my ignorance if it should become prevalent.
I bought a Galaxy Note Pro 12.2 32GB wifi and had it for about one day. I performed a factory restore on the device in which it froze for about 2 hours. (this is probably the stupid part) I turned it off since it was not progressing after a long time and it booted up as a new device. After about 5 minutes of use, it randomly restarted and went into a boot loop. About every 15 or so boot screens, it sometimes boots up, then freezes and goes back into a boot loop. The longest it stayed active without resetting was about 10 minutes. After hours of research, I have done the following
Tried to boot into recovery to no avail. It just continuously pops up the device name screen
I have tried to flash the device with a stock rom in odin 3.9.
It recognizes the device but hangs at the Initialization stage. Sometimes it will give me a fail notice saying that it couldn't open the COM port
I've tried it on another computer, changed usb ports, powered on and off multiple times and nothing changes.
please let me know if i've forgotten anything. Any help will be appreciated.
Also I live in Japan, so if I can fix it myself that would be nice since this device isn't sold here yet, I'm not able to get support from a store. I'd like to avoid waiting a month sending it back to america, replacing it, and getting it sent back. Thanks in advance ^_^
Make sure you have the correct and latest Samsung drivers for your tablet.
If you have an SD card installed, try removing it and see if you can boot up and get it stable.
roninb30 said:
Ok so I'm new to the thread and basically to android tablets, so please forgive my ignorance if it should become prevalent.
I bought a Galaxy Note Pro 12.2 32GB wifi and had it for about one day. I performed a factory restore on the device in which it froze for about 2 hours. (this is probably the stupid part) I turned it off since it was not progressing after a long time and it booted up as a new device. After about 5 minutes of use, it randomly restarted and went into a boot loop. About every 15 or so boot screens, it sometimes boots up, then freezes and goes back into a boot loop. The longest it stayed active without resetting was about 10 minutes. After hours of research, I have done the following
Tried to boot into recovery to no avail. It just continuously pops up the device name screen
I have tried to flash the device with a stock rom in odin 3.9.
It recognizes the device but hangs at the Initialization stage. Sometimes it will give me a fail notice saying that it couldn't open the COM port
I've tried it on another computer, changed usb ports, powered on and off multiple times and nothing changes.
please let me know if i've forgotten anything. Any help will be appreciated.
Also I live in Japan, so if I can fix it myself that would be nice since this device isn't sold here yet, I'm not able to get support from a store. I'd like to avoid waiting a month sending it back to america, replacing it, and getting it sent back. Thanks in advance ^_^
Click to expand...
Click to collapse
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root. Don't get me wrong, I have a list of things I want that require root and it will be happening but I figured I should at least run it for a couple weeks to make sure no defects pop up before I void the warranty. Good luck to you!
Russbad said:
Make sure you have the correct and latest Samsung drivers for your tablet.
If you have an SD card installed, try removing it and see if you can boot up and get it stable.
Click to expand...
Click to collapse
I've installed drivers a few times. No go.
I'm on it now and the boot loop seems to have stopped, but I still get random restarts. But each time it restarts, it's from factory, so it doesn't save anything I download or any settings such as enabling debugging in the developer settings.
rkirmeier said:
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root. Don't get me wrong, I have a list of things I want that require root and it will be happening but I figured I should at least run it for a couple weeks to make sure no defects pop up before I void the warranty. Good luck to you!
Click to expand...
Click to collapse
I didn't root, and I haven't voided my warranty. I can still get into download mode and my flash counter is still at 0. I never tried to root, I simply wanted to flash to stock, from stock.
[Edit] I'd also like to mention that Odin has not successfully done anything, Every time I tried to flash it was done with a stock ROM, and everything that has gone wrong has occurred on nothing but the stock ROM
Is it possible that I need a pit file for the device since no version of Odin will get past initialization? ....if so where can I get one for the this model?
roninb30 said:
I've installed drivers a few times. No go.
I'm on it now and the boot loop seems to have stopped, but I still get random restarts. But each time it restarts, it's from factory, so it doesn't save anything I download or any settings such as enabling debugging in the developer settings.
I didn't root, and I haven't voided my warranty. I can still get into download mode and my flash counter is still at 0. I never tried to root, I simply wanted to flash to stock, from stock.
[Edit] I'd also like to mention that Odin has not successfully done anything, Every time I tried to flash it was done with a stock ROM, and everything that has gone wrong has occurred on nothing but the stock ROM
Click to expand...
Click to collapse
If you are not rooted and you have a boot loop I'd be returning the device for a new one...
rkirmeier said:
If you are not rooted and you have a boot loop I'd be returning the device for a new one...
Click to expand...
Click to collapse
I hate to agree since you would have to wait for a while to get the replacement, however the device sounds to be defective. just my two cents as a developer, if you flash anything to the device, root, a new image, or even the factory software, Knox will be tripped and the counter will go from zero to a one. My advice would be to get a replacement for the defective one.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Huge 3rd.
Device should just plain WORK out of the box. There shouldn't have been a need to flash stock to begin with.
One last suggestion, factory reset from recovery. From complete power off, hold volume up+home button+power and after a few seconds let go until it boots into recovery. From there wipe cache, wipe davlik, and factory restore. Good luck!
Android.Ninja said:
I hate to agree since you would have to wait for a while to get the replacement, however the device sounds to be defective. just my two cents as a developer, if you flash anything to the device, root, a new image, or even the factory software, Knox will be tripped and the counter will go from zero to a one. My advice would be to get a replacement for the defective one.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
Yeah, it's unfortunate, but I have to suck it up and just pay the shipping back to Ameica....then again for it to come back. Just wanted to do everything I could before I had to send it. Thanks for the input though. I guess I learned quite a bit researching processes and terminology which will be helpful in the future. ^-^
Russbad said:
One last suggestion, factory reset from recovery. From complete power off, hold volume up+home button+power and after a few seconds let go until it boots into recovery. From there wipe cache, wipe davlik, and factory restore. Good luck!
Click to expand...
Click to collapse
Tried many times. The device pretty much gives me the finger by going blank and repeatedly showing the boot up logo when I hold the buttons down.
rkirmeier said:
Wow, you rooted (void warranty) on a day old tablet on a platform that is new to you? I've been rooting Android devices for over 3 years now and have had mine for a week now without root.
Click to expand...
Click to collapse
I voided my warrant after having mine for about an hour (though not new to Android). I did all my random "OCD does it work as I expect/want" tests and it passed, so I rooted. Had it for one week now, and I absolutely love everything about this tablet.
roninb30 said:
Yeah, it's unfortunate, but I have to suck it up and just pay the shipping back to Ameica
Click to expand...
Click to collapse
IMO, it will be worth it. This is my fourth tablet, and is the first one I've not had buyer's remorse with. Luckily with the gift credit for Google I was able to get the non-Tegra equivalents of some of my favorite games, too.
ExtremeRyno said:
I voided my warrant after having mine for about an hour (though not new to Android). I did all my random "OCD does it work as I expect/want" tests and it passed, so I rooted. Had it for one week now, and I absolutely love everything about this tablet.
IMO, it will be worth it. This is my fourth tablet, and is the first one I've not had buyer's remorse with. Luckily with the gift credit for Google I was able to get the non-Tegra equivalents of some of my favorite games, too.
Click to expand...
Click to collapse
After doing research, I think that even if I get a new one, I want to root it. With the problems I've read about for kitkat 4.4.2 I need to know how to fix problems, and start with a fresh install of roms and know how to use custom recovery. I haven't done anything yet, but I was wondering...
Since I'm stuck in a boot loop with no stock recovery, can I flash a custom recovery to fix my issues, flash the stock rom that is on sammobile.com and then root after that? From what I understand this is a soft brick since I can still sometimes access the device. I worked out why I couldn't access the device with adb and now it shows the device as listed. It stays on long enough to where I could flash a recovery before it restarts itself. I'm not trying to do anything stupid, just getting information before I pay the shipping for it back to the states. I've checked the knox counter in download mode, and it is still set to 0, so I haven't voided the warranty yet.
Any input would be greatly appreciated.
It's odd that a new device would not have recovery. I don't want to insult you, but just making sure we covered the basics, volume up+home+power gets you to recovery. The boot logo will flash about three times, make sure you're still pressing all three buttons, then let go after the 3rd flash of the boot logo then you should be in recovery. Volume down+home+power takes you to download mode, this is where you flash roms and recovery. I read in another post about someone not being able to get in recovery after numerous times, it turned out that he was hitting the volume down button instead of volume up. Just to be clear, if you do flash recovery, you will definitely trip knox, at this time there is no way around that.
Russbad said:
It's odd that a new device would not have recovery. I don't want to insult you, but just making sure we covered the basics, volume up+home+power gets you to recovery. The boot logo will flash about three times, make sure you're still pressing all three buttons, then let go after the 3rd flash of the boot logo then you should be in recovery. Volume down+home+power takes you to download mode, this is where you flash roms and recovery. I read in another post about someone not being able to get in recovery after numerous times, it turned out that he was hitting the volume down button instead of volume up. Just to be clear, if you do flash recovery, you will definitely trip knox, at this time there is no way around that.
Click to expand...
Click to collapse
I understand the skepticism. Yeah, I tried the button combination, usb in, usb out. I can power off the device completely only when it is plugged into power. When I hold the recovery combo from power on, the screen goes black with no flashing of the boot logo, looks as if it wants to go to recovery, and then then the boot logo comes up again, but just continues to the boot animation and continues the boot loop, even if i'm still holding down volume up and home buttons. It will sometimes boot up, then freeze after a couple of seconds, and return to boot loop. On rare occasions it will boot up, but turns me to setup like it's a brand new device. I can access everything for about 10 minutes, and then it will randomly restart and continue to boot loop again after that. I tried update/initialization in kies, but it would restart before the downloading and decompressing of binary could finish. It finished one time and then switch to a downloading screen (although it didn't say odin since you have to manually go there) but the update would freeze at 0 percent no matter how long I left the device there. It's all pretty lame ><

Categories

Resources