Related
I don't really know what happened actually...I was on quickwiz 1.0.3 for about a week and last night my battery drained off completely and the skyrocket shut itself off...after I charged it up this morning, I saw a series of force closes and I did see some interesting message about "system UDI" or something not being compatible...dont remember what it was exactly though...
after that, i thought the device was soft bricked and used k0nane's method of odin to revert it back....the odin said that it was successful and rebooted my device...but, my mobile is now stuck at the bootlogo(at&t rethink possible) and keeps running that boot animation over and over without booting up entirely...
Any suggestions on how to recover from this plz?
I saw that the counter was incremented...so returning this is an issue now...trying to order my jig for that...any help will be greatly appreciated
Did you revert back to stock recovery? If so have you tried flashing cwm recovery using Odin?
Sent from my SAMSUNG-SGH-I727 using xda premium
If you can get into cwm recovery try restoring a nandroid if you made one if not try flashing a rom but wipe data and cache first
Sent from my SAMSUNG-SGH-I727 using xda premium
LoGaN- said:
I don't really know what happened actually...I was on quickwiz 1.0.3 for about a week and last night my battery drained off completely and the skyrocket shut itself off...after I charged it up this morning, I saw a series of force closes and I did see some interesting message about "system UDI" or something not being compatible...dont remember what it was exactly though...
after that, i thought the device was soft bricked and used k0nane's method of odin to revert it back....the odin said that it was successful and rebooted my device...but, my mobile is now stuck at the bootlogo(at&t rethink possible) and keeps running that boot animation over and over without booting up entirely...
Any suggestions on how to recover from this plz?
I saw that the counter was incremented...so returning this is an issue now...trying to order my jig for that...any help will be greatly appreciated
Click to expand...
Click to collapse
you should go into stock recovery Which you have if you flashed Konanes stock file.....and wipe data. if that does not do the trick. i would try wiping data again....doing the stock one more time. i been in that exact same boat, as have others. this is what i did to get out. but others have had luck just flashing 3e recovery and wiping data 3 times, flash CMW via odin and restore a nandroid to get back up and running or staying at stock. its up to you.
hope this helps.
Thanks for the reply man...but I didnt really follow what u said back there ...odining back the tar that k0nane gave should return the unit back to stock-meaning i should have the stock recovery as well...but I dont know why my skyrocket didn't boot up the whole way
Lemme explain what I did initially with my device actually- After I got my skyrocket, I used copperhed's method to flash clockwork cwm thru odin and rooted the device..after that, I flashed the quickwiz 1.0.3 thru the clockwork recovery and the thing I mentioned before happened to me...nothing more, nothing less...after this force close thing I had initially on quickwiz, I tried restoring my previous nandoid backups and all of them stopped at the bootanimation looping...nothing booted the whole way up and yes, I wiped for each restore...with none of them working, I started the k0nane's odining
I actually got this all worked out somehow now and want to share this info as it might help someone who had the same issue...After flashing the k0nane's tar thru odin, I went into the 3e recover and tried a factory reset...it asked me for a password there and i typed in the wrong password a couple of times as i dont know what the right one is...after some wrong attempts, it formatted everything(/data, cache and even the sdcad) and voila...my skyrocket booted up fine...i didnt worry much to do this as I had nothing on my sdcard and also since i have nandroid's of all my previous ROM's
But I still wanna know why this all happened..
all this panic cost me about 30 bucks to order a jig faster thru EMS....and my counter is up by 2 as I odin'd the tar twice thinking it might work
Thanks for the reply man...just figured it out...
A similar thing happened to me once, i flashed cm7 then i flash da_g kernal. After that, my phone was stuck on cm7 logo. I went back to stock and i was stuck at the rethink possible logo. After that i restared my phone into the stock recovery mode and i wiped everything and i was able to get my phone back.
LoGaN- said:
Thanks for the reply man...just figured it out...
Click to expand...
Click to collapse
i think you made this harder than it was, i honestly STILL dont know WHY this happens. but alot of people have had it happen. some say its undervolting( but i never did any of that) others thinks its Da 'gs Kernel which you were on if you flashed QuickWiz and i had his running as well. some think its the CWM itself that that is causing this because it is not for advice.
Over the past week i have STOPPED using Da g's kernel and have not that happen again.
either way, i think you went into a panic, the steps i listed WILL work weather you flashed 3e with odin or Return to stock to get 3e with Odin and WIPE ALL DATA, and CACHE. im glad you got it going though. sorry you waisted your 30 bucks bruh.
thanks for ur concern bro...i just panicked coz i wanted a working phone asap and i thought of returning mine at the att store...so used the ems shipping for faster delivery of the jig...and minutes after I ordered it, I got it all working...u can see the heights of irony here ...nyway....am glad to see it happen atleast once as I will know what to do if this happens again...for the moment, am gonna stay away from the OC kernels...
Did the flash counter reset?
Sent from my SAMSUNG-SGH-I727 using XDA App
LoGaN- said:
After flashing the k0nane's tar thru odin, I went into the 3e recover and tried a factory reset...it asked me for a password there and i typed in the wrong password a couple of times as i dont know what the right one is.....
Click to expand...
Click to collapse
So.... is there some secret 3e factory reset password we need??
DoctorQMM said:
So.... is there some secret 3e factory reset password we need??
Click to expand...
Click to collapse
i have never seen this in 3e.....i would like to know how to get to that screen.
Yeah wtf? Ive never seen a password in any recovery post a picture of this please
hmn...i will try to see if i can do this on the weekend...my flash counter is already up by 2...what harm will it do for one more
if you want,you can follow my procedure and it will ask for it again...just odin the tar given by k0nan and go into the 3e recovery by holdin volume up+down and power on...do a wipe and it will ask for it...
and no, my flash counter didnt reset...have to wait for my jig and try resetting it
silver03wrx said:
Yeah wtf? Ive never seen a password in any recovery post a picture of this please
Click to expand...
Click to collapse
now my skyrocket back screen wont turn on, everytime i tried to get into download my computer pop up messege that cant not find QHSUSB_Dload, anyone can help me out?
So you phone wont so anything? No download mode and no recovery? If so order a usb jig
FIXED- I found the stock ODIN Rogers file rooted and that got me going.
The unbrick ROM does NOT work for ROGERS phones.
Hello Everyone,
Problem: Infuse will boot up and you see the ATT screen then 2 seconds later it sits on the SAMSUNG screen.
I have tried just about everything posted. I even tried the Infuse unbrick Odin pkg.
I CAN get into download mode. I can flash with ODIN. But upon reboot the phone goes back to the SAMSUNG screen.
How did I get here?
I had was running ZEUS. I had the issue with ppl not hearing me unless I turned speakerphone on and off for every call. I did a master reset. I had an issue with something else so I tried using a CWM flashable file which caused the problems needing the master reset.
I have tried many things but I am stuck.
I am trying to get an ODIN kernel that is moded like the V8 community kernel BUT all the links are broken.
droiduzr2 said:
Hello Everyone,
Problem: Infuse will boot up and you see the ATT screen then 2 seconds later it sits on the SAMSUNG screen.
I have tried just about everything posted. I even tried the Infuse unbrick Odin pkg.
I CAN get into download mode. I can flash with ODIN. But upon reboot the phone goes back to the SAMSUNG screen.
How did I get here?
I had was running ZEUS. I had the issue with ppl not hearing me unless I turned speakerphone on and off for every call. I did a master reset. I had an issue with something else so I tried using a CWM flashable file which caused the problems needing the master reset.
I have tried many things but I am stuck.
I am trying to get an ODIN kernel that is moded like the V8 community kernel BUT all the links are broken.
Click to expand...
Click to collapse
Seems obvious to a rookie like me, but shouldn't you just use GTG's ultimate unbrick back to D5 stock and go from there?
droiduzr2 said:
I have tried just about everything posted. I even tried the Infuse unbrick Odin pkg.
Click to expand...
Click to collapse
Hmm... EVERYTHING?? I dunno about that... 2 second search bro.
http://forum.xda-developers.com/showthread.php?p=22459950
Really 5 hrs?
Sent from my SGH-I997 using XDA App
SnowBeer said:
Seems obvious to a rookie like me, but shouldn't you just use GTG's ultimate unbrick back to D5 stock and go from there?
Click to expand...
Click to collapse
I wrote that in my OP that I tried the ultimate unbrick with ODIN still stuck on Samsung Screen.
Erik_T said:
Hmm... EVERYTHING?? I dunno about that... 2 second search bro.
http://forum.xda-developers.com/showthread.php?p=22459950
Click to expand...
Click to collapse
I said I needed ODIN files...if I am stuck ont he SAMSUNG screen it means NO CWM for me. The links in the original community kernel thread are broken and several ppl have contacted the OP including me asking to fix the links.
droiduzr2 said:
I said I needed ODIN files...if I am stuck ont he SAMSUNG screen it means NO CWM for me. The links in the original community kernel thread are broken and several ppl have contacted the OP including me asking to fix the links.
Click to expand...
Click to collapse
Soo....
Erik_T said:
YES THERE IS! God. MediaFire Y U take so long!
Mirror for Odin. All credits to GTG. I am going to pm him to ask him to add it to the op.
http://www.mediafire.com/?c85mj690uk5vaw5
Thanks >>
Click to expand...
Click to collapse
Posted http://forum.xda-developers.com/showthread.php?t=1112555&page=17
And that is the "original" community kernel.. Dunno why you'd say it's not?
---------- Post added at 04:04 PM ---------- Previous post was at 04:02 PM ----------
Ltilt2 said:
Really 5 hrs?
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
Yeah.. I dunno about that...
Guys, I already posted that I tried that NO GO
I need the files from here BUT the links are broken
http://forum.xda-developers.com/showthread.php?t=1119598
I think I can get it working again with a kernel that will convert to ext4.
I can not get into the phone to delete or change the voodoo lagfix.
It seems that the boot partition is not working right.
I can flash with ODIN the unbrick file and it will install but upon reboot still stuck at samsung screen. I can NOT get into recovery either.
WTF? Did I make a brick?
Someone has to know how to fix this
droiduzr2 said:
Guys, I already posted that I tried that NO GO
I need the files from here BUT the links are broken
http://forum.xda-developers.com/showthread.php?t=1119598
I think I can get it working again with a kernel that will convert to ext4.
I can not get into the phone to delete or change the voodoo lagfix.
It seems that the boot partition is not working right.
I can flash with ODIN the unbrick file and it will install but upon reboot still stuck at samsung screen. I can NOT get into recovery either.
WTF? Did I make a brick?
Someone has to know how to fix this
Click to expand...
Click to collapse
Dude.. if you can't figure this out with those links that I posted, then I don't think that I can help you.. I can somehow manage to odin myself and bring myself back to a rom with those files and the respective rom. And I know that there are other people that can too... good luck bro.. I'm done..
Edit: May I suggest this?
Edit 2: Actually, if you need the 3e recovery file. I just remembered that you need that too. Haven't seen a mirror posted for that. Maybe that is the element that you are missing? If it is lemme know..
It is really quite on xda today
Flash any GB kernel that's rooted, but uncheck reboot.
Then try to boot to recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium
Thamma513 said:
It is really quite on xda today
Click to expand...
Click to collapse
Kinda random place to put that bit I agree.
Truckerglenn said:
Flash any GB kernel that's rooted, but uncheck reboot.
Then try to boot to recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Try Entropy's DD
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Erik_T said:
Dude.. if you can't figure this out with those links that I posted, then I don't think that I can help you.. I can somehow manage to odin myself and bring myself back to a rom with those files and the respective rom. And I know that there are other people that can too... good luck bro.. I'm done..
Edit: May I suggest this?
Edit 2: Actually, if you need the 3e recovery file. I just remembered that you need that too. Haven't seen a mirror posted for that. Maybe that is the element that you are missing? If it is lemme know..
Click to expand...
Click to collapse
I am well aware of using this stuff. I flashed many phones and tablets hence why I like Samsung.
Yes, can you provide me the 3e Recovery ODIN file.
That would be a good thing to try.
Truckerglenn said:
Flash any GB kernel that's rooted, but uncheck reboot.
Then try to boot to recovery.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I can only use ODIN files because I can ONLY get into download mode. I can NOT get into recovery to use any CWM files.
I have been trying to find ODIN kernel files but the ones available the download links are broken and I pm'd the OP as well as others that need the files but still no luck yet.
Can someone please post an ODIN kernel for me to try.
Edit:
Just to be clear I have now flashed the Unbrick ROM several times. It will load up and install. I get a green pass in ODIN but on reboot I see the ATT screen then stuck at the Samsung screen.
I have started to flash odin kernels from my captivate and tablet. They do get past the ATT screen and no Samsung screen but all I see is grainy stuff all over SO that tells me that changes are being made. I just need to try with an INFUSE ODIN kernel that might convert to ext4. I think that will solve the problem.
btw- thanks for the help...I am just ticked trying to get my phone to work.
I just need one damn file or small command to wipe the phone so it will take the stuff we are trying to push.
FIXED- I found the stock ODIN Rogers file rooted and that got me going.
The unbrick ROM does NOT work for ROGERS phones.
I went through the same thing about a month ago on mine... I eventually found the same file you did... it was a pain and since then if I've bricked I've flashed ultimate unbrick then flashed stock Rogers and it resolves my issue... I keep both saved on my computer now
Sent from my SAMSUNG-SGH-I997R using Tapatalk
So.. you're good? Yes? Problem solved? Close thread...?
Sent from my A500 using Tapatalk
Simple Fix...
Use. GTG's ultimate unbrick.
Download http://www.mediafire.com/?i57410xodydx5l1
Follow the easy steps.
This will bring to how you bought the phone.
SECOND to all with BLACK screens.
Turn off the phone using power and volume up and down.
While plugging in the phone to the USB. Release power button.
This may take multiple tried, but you will get the download screen eventually.
Its all about timing.
YOUR PHONE CAN NOT BE BRICKED.
The down loader is not on the internal memory,
it is on a FLASH ROM separate from everything else.
Thanks to "secretasianman"
Original:http://forum.xda-developers.com/showpost.php?p=22404594&postcount=392
People need to remember that not everyone is using AT&T Infuse, gotta clarify that before posting guides.
And yeah keep the stock rogers rooted rom on your desktop, comes in handy for a quick return to stock if anything goes wrong.
I was caught in a boot loop and tried to re flash, when in my haste I forgot that Odin will recheck partition when loading .Pit files (pretty lame feature)
Still it was my fault for clicking start in haste.
**phone was partitioned, and would not go into download mode, it was stuck in a screen that said "Firmware update error, please restore in Kies", but it wouldn't connect to kies**
I sent my phone to XDA member Connexion2005
http://forum.xda-developers.com/member.php?u=1602851
I haven't got it in my hands yet, but he just told me it was fixed, I can't wait to get it back and leave it the hell alone (until someone makes CM7 or better work on it)
anyhow, this is out there so if you do what I did (DON'T) there's a solution. Set me back $50 plus shipping to TX from NYC but still, I didn't have to get a whole new phone.
for 50 bucks im sure k0nane would have made an uberfixit tar :/
shabbypenguin said:
for 50 bucks im sure k0nane would have made an uberfixit tar :/
Click to expand...
Click to collapse
Absolutely.
shabbypenguin said:
for 50 bucks im sure k0nane would have made an uberfixit tar :/
Click to expand...
Click to collapse
Please elaborate. Not finding much info on this "uberfixit", but it sounds like it's some method of re-creating the stock filesystem that's flashable in odin?
I was putting this out there, because I'm not the only one that this will happen to.
yea it happens when you repartition, an uberfixit requires a complete dump of the phone and quite a bit of time, but will completely fix what you described
the problem with repartitioning is that it wipes the phone clean and then starts to reinstall everything, problem is neither one of teh tars has the full dump (we do it for the sake of saving actual bricks)
knowing someone who can jtag is great we have had a few epic 4g touches that crashed and burned and were saved via jtag.
shabbypenguin said:
yea it happens when you repartition, an uberfixit requires a complete dump of the phone and quite a bit of time, but will completely fix what you described
the problem with repartitioning is that it wipes the phone clean and then starts to reinstall everything, problem is neither one of teh tars has the full dump (we do it for the sake of saving actual bricks)
knowing someone who can jtag is great we have had a few epic 4g touches that crashed and burned and were saved via jtag.
Click to expand...
Click to collapse
You may not remember, but I did go onto your IRC and spoke with you regarding this issue.
oh sorry, the irc channel we have is for a bunch of devices currently we house blaze 4g, attain 4g, conenct 4g, lucid and optimus m+ owners. so i probably thought you were an attain owner since we have had a good number of attain owners repartition as well :/
shabbypenguin said:
oh sorry, the irc channel we have is for a bunch of devices currently we house blaze 4g, attain 4g, conenct 4g, lucid and optimus m+ owners. so i probably thought you were an attain owner since we have had a good number of attain owners repartition as well :/
Click to expand...
Click to collapse
it's all good, bottom line is I f'd up my device, but now its fixed.
um...yeah...
So i did the exact same thing as you... Been trying to find anyone who can help me out. Is there anyway I can fix it myself? I haven't found a single place in my whole state that can fix the problem. If at all possible, I'd like to avoid sending it out for repair.
So how do I get this uberfixit?
I stupidly re-partitioned using Odin, also: I did not realize that Odin re-checked the check box -even after unchecking- when a new pda file was loaded. My bad. Totally though it was bricked until i was able to flash this stock gingerbread rom, but now kies says that my Blaze S does not qualify for upgrades... Did the re-partitioning do this?
I can no longer get to the recovery screen, although if I restart my blaze while connected to a pc via usb, it does allow the "re-install OS?" page to display, and I can get to recover from there: But absolutely no more access to the recovery "menu" which allows me to wipe cache/restore to factory/etc.
Just Odin cwm back then flash away
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Thanks for the quick reply; I will try that right now: My fingers are crossed.
2vivid said:
Just Odin cwm back then flash away
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
thomassino said:
Thanks for the quick reply; I will try that right now: My fingers are crossed.
Click to expand...
Click to collapse
It's just a soft brick, I have done that at least 10 times.
Will you make this?
k0nane said:
Absolutely.
Click to expand...
Click to collapse
Hi, k0nane I too have bricked my phone due to not unchecking re-partition. Now no matter what I do the phone displays the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. It is frustrating. I will certainly pay you if you make a fix for this that I can flash in odin! I don't care if it wipes my phone completely as I was trying to flash a new rom anyways. Please reply I'm desperate to get this thing working again.
runboyrun said:
Hi, k0nane I too have bricked my phone due to not unchecking re-partition. Now no matter what I do the phone displays the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. It is frustrating. I will certainly pay you if you make a fix for this that I can flash in odin! I don't care if it wipes my phone completely as I was trying to flash a new rom anyways. Please reply I'm desperate to get this thing working again.
Click to expand...
Click to collapse
That's a soft brick.
No need to pay anyone lol just pull the battery and go back to download mode (for Odin) again and revert back to stock. A quick search through 'bricked' type threads would have netted this info :thumbup:
Sent from my SGH-T769 using xda app-developers app
So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Just search in the stickies for bootloaders. That will solve your problems
Sent from my SGH-I997 using xda app-developers app
COfatboy said:
So I have an old Infuse that my kids use and it went crazy the other day. Not sure what happened. Long story short I keep getting a boot loop at the ATT screen. This phone is not rooted and I'm not sure if it was on Froyo or GB. I've flashed every return from brick I can find on XDA. I'm using Odin and I'm pretty familiar with flashing/rooting etc. Can't figure this one out. The only thing I can think is the boot loaders are not the correct ones? Not sure, I keep seeing GTG's ultimate unbrick but all the links I get to it don't work. this is the only thing I haven't tried. Any help would be appreciated.
Edit to add: After I flash in Odin it goes to reboot then does the open update, verifying update, installing update, successfully installed update package.
Copying media files it says failed to mount/sdcard, can't mount /sdcard your storage not prepared yet please use UI menu for format and reboot. ??? I think that's the problem. How do I fix??
Click to expand...
Click to collapse
If you'd like to try GTG's Ultimate Unbrick, you can find a working download here:
http://forum.xda-developers.com/showpost.php?p=22404446&postcount=391
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
COfatboy said:
Tried everything and no go. Not sure where to go from here. Sure seems like a hardware issue.
Click to expand...
Click to collapse
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
prairied0gg said:
You mentioned it's boot-looping at the Samsung logo - perhaps there's an issue with the power button.
Here's a couple of threads that may be helpful:
http://forum.xda-developers.com/showthread.php?t=2107558
http://forum.xda-developers.com/showthread.php?t=1996709
Click to expand...
Click to collapse
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
COfatboy said:
It goes past the Samsung logo screen then to the ATT Rethink Possible screen then keeps looping on that screen over and over. It charges normally also.
Click to expand...
Click to collapse
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
prairied0gg said:
I would try flashing just a kernel (not the whole unbrick package). I have been in a similar situation and after trying everything imaginable that's what ended up fixing it for me.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
COfatboy said:
Tried that earlier I thought, tried again just to make sure. Still no go. I appreciate all your help! :good: I'm gonna give up for tonight anyways.
Click to expand...
Click to collapse
This happened to me earlier. What I did was-
1 Went to full stock using heimdal one click, After completetion, U may stuck in bootloop in at&t as you said
2 Flash efs.zip found in the link below using odin. put efs.zip in odin and untouch any other setting and flash, (Ur imei may be previously corrupted so u got bootloop). This doesnot do any harm. So flash with confidence. If ur device doesnot show up in odin after u flash with heimdal one click , reinstal drivers with kies mini
Link for download http://forum.xda-developers.com/showthread.php?t=1729838
3 Now u'll be out of AT&T bootloop if ur imei was previously corrupted.
I was in similar situation. And this solved my proble.
Hit me thanks if I helped you :good:
Thanks for all the advise. Still not working. Tried everything above and much more. Different things I do give different results but pretty much the same in end. Either sticks in recovery or boot loops one way or another. Really don't see how this could be related to software but you never know I guess.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Looks like I've soft-bricked my S3 and cannot get it back working at all.
When you power it on, it shows the yellow triangle and "Firmware Upgrade encountered an issue. Please use software repair assistant and try again."
I can get into download mode but nothing flashes through. I've tried ML1, MF1, the VRALEC bootchain method, including the PIT file, everything. Odin just won't complete any of the flashes. On some it hangs on Initializing (and I've tried all USB ports, different cables, and two laptops), on others it hangs on nand write partition. I even tried the trick where I add the PIT file but unselect Re-Partition. Nada. Oh, and I tried the actual verizon repair assistand and at 83% it says "phone was disconnected, please reconnect and try again."
Here's what the download mode screen looks like if that helps anyone http://i.imgur.com/zpNGAy4.jpg
Help please? I would really appreciate it.
What did you exactly do that brought you to this state?
thebballkid said:
Looks like I've soft-bricked my S3 and cannot get it back working at all.
When you power it on, it shows the yellow triangle and "Firmware Upgrade encountered an issue. Please use software repair assistant and try again."
I can get into download mode but nothing flashes through. I've tried ML1, MF1, the VRALEC bootchain method, including the PIT file, everything. Odin just won't complete any of the flashes. On some it hangs on Initializing (and I've tried all USB ports, different cables, and two laptops), on others it hangs on nand write partition. I even tried the trick where I add the PIT file but unselect Re-Partition. Nada. Oh, and I tried the actual verizon repair assistand and at 83% it says "phone was disconnected, please reconnect and try again."
Here's what the download mode screen looks like if that helps anyone http://i.imgur.com/zpNGAy4.jpg
Help please? I would really appreciate it.
Click to expand...
Click to collapse
Are you brick with 4.3?
I'm having the same problem (stock rooted 4.3). I flashed clockworkmod via ROM manager and when I went to boot into recovery... yellow triangle of death. I too have tried Odin back to stock, but everything fails. Trying Odin from the triangle screen right now. Seems to be hanging on "SetupConnection".
Update: Failed.
jpmi23 said:
I'm having the same problem (stock rooted 4.3). I flashed clockworkmod via ROM manager and when I went to boot into recovery... yellow triangle of death. I too have tried Odin back to stock, but everything fails. Trying Odin from the triangle screen right now. Seems to be hanging on "SetupConnection".
Update: Failed.
Click to expand...
Click to collapse
If you took the 4.3 OTA you will be unable to flash a custom recovery. This very helpful thread created by @BadUsername will get you back up and running:
http://forum.xda-developers.com/showthread.php?t=2639337
Looks like that's working! Thanks man!
buhohitr said:
Are you brick with 4.3?
Click to expand...
Click to collapse
I think so? I tried going back to stock from being rooted and on CM and I'm actually not positive if I'm on 4.3 now or not since the flash never succeeded. I may have had the wrong bootloader when trying to flash 4.3.
Any ideas?
BattsNotIncld said:
What did you exactly do that brought you to this state?
Click to expand...
Click to collapse
Great question. I was rooted and on CM 10.2 when the phone started shutting down randomly. Reinstalled everything CM-related and it was still happening. I then used TriangleAway to reset root counter which worked flawlessly. Tried putting on a stock rom (the latest off of sammobile I believe 4.3), when the flash failed and then I got where I am now. Maybe I had the wrong bootloader for 4.3? Throughout my research I kept leaning towards this being the case similar to many that flashed OTA 4.3 and got a brick, but all the solutions for that haven't worked for me
thebballkid said:
Great question. I was rooted and on CM 10.2 when the phone started shutting down randomly. Reinstalled everything CM-related and it was still happening. I then used TriangleAway to reset root counter which worked flawlessly. Tried putting on a stock rom (the latest off of sammobile I believe 4.3), when the flash failed and then I got where I am now. Maybe I had the wrong bootloader for 4.3? Throughout my research I kept leaning towards this being the case similar to many that flashed OTA 4.3 and got a brick, but all the solutions for that haven't worked for me
Click to expand...
Click to collapse
You can tell which bootloader you are on from download mode. Use this thread it has all the info you need including how to fix it:
http://forum.xda-developers.com/showthread.php?t=2639337
Unless you've tried all those methods already? I think specifically this is the method you should try:
http://forum.xda-developers.com/showthread.php?t=2586319
BattsNotIncld said:
You can tell which bootloader you are on from download mode. Use this thread it has all the info you need including how to fix it:
http://forum.xda-developers.com/showthread.php?t=2639337
Unless you've tried all those methods already? I think specifically this is the method you should try:
http://forum.xda-developers.com/showthread.php?t=2586319
Click to expand...
Click to collapse
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
thebballkid said:
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
Click to expand...
Click to collapse
You're using Odin right?
Try to flash it with the pit file. If that doesn't work then try to use the Verizon utility. That thread should work if you follow those directions perfectly, at least I haven't heard of it not working yet.
Sent from my SCH-I535 using Tapatalk 2
thebballkid said:
Thanks, at least I've confirmed I'm on the 4.3 baseband. However, I tried the guide on there and the guide you provided and am still unable to get past the "Initialzation" step in Odin. Any ideas?
Click to expand...
Click to collapse
Hmm. Well at this point I would suggest you make sure you're using a quality USB cable and make sure you use the USB port right on the motherboard. But it looks like you already tried all that. What version of ODIN are you using?
Sent from my SCH-I535 using Tapatalk
BadUsername said:
You're using Odin right?
Try to flash it with the pit file. If that doesn't work then try to use the Verizon utility. That thread should work if you follow those directions perfectly, at least I haven't heard of it not working yet.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Hey thanks for chiming in, really appreciated your guide. I followed everything to the T and had no luck. Tried both Odin 3.07 (PDA) and 3.09 (AP) and your method kept getting stuck at Initialzation in Odin. I tried the PIT file on both too, same thing. Tried the Verizon Utility and at 83% it says "phone is disconnected, lease reconnect and try again."
I will say this: when it gets stuck on Initialzation and I unplug the phone, Odin says "PIT file not found." Not sure if that means anything since the phone is unplugged but only other info I can think to share.
Got any other ideas? Would hate to be the first one that couldn't be helped by your directions. Thanks anyways!
BattsNotIncld said:
Hmm. Well at this point I would suggest you make sure you're using a quality USB cable and make sure you use the USB port right on the motherboard. But it looks like you already tried all that. What version of ODIN are you using?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I have tried, been using two official Samsung USB cables that came with the phone and my Nexus 10. I'm working on two laptops and tried all of the different ports getting the same result, Odin hangs on Initialzation.
I tried using both Odin 3.07 (PDA) and 3.09 (AP).
Any other ideas? Thanks!
thebballkid said:
Hey thanks for chiming in, really appreciated your guide. I followed everything to the T and had no luck. Tried both Odin 3.07 (PDA) and 3.09 (AP) and your method kept getting stuck at Initialzation in Odin. I tried the PIT file on both too, same thing. Tried the Verizon Utility and at 83% it says "phone is disconnected, lease reconnect and try again."
I will say this: when it gets stuck on Initialzation and I unplug the phone, Odin says "PIT file not found." Not sure if that means anything since the phone is unplugged but only other info I can think to share.
Got any other ideas? Would hate to be the first one that couldn't be helped by your directions. Thanks anyways!
Click to expand...
Click to collapse
I didn't write the softbrick guide, @ThePagel deserves that credit. I just made a sticky thread to have everything in one place.
I think you followed everything perfectly and did all that you could, you've read around a lot and tried everything you found. My guess is somehow your system partition is in a read only state and simply isn't letting anything write to it. That would explain what is happening.
What I would do is treat this as a hard brick. I would do one of 3 things:
1) try to hardbrick the phone yourself, maybe run the old version of casual and flash the insecure aboot file to unlock the phone, this obviously will corrupt the 4.3 bootloader and hardbrick the phone. Then you could use the hardbrick restore guide to fix it that way.
2) or you could send it in "as is" for jtag that will write the bootchain for you and most likely fix the problem.
3) try to use the methods in this thread but use all the 4.3 files. If you could somehow get this to work you should write a guide for it and I'll post it in the sticky. I think you have enough know how to attempt it.
http://forum.xda-developers.com/showthread.php?t=1840030
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I didn't write the softbrick guide, @ThePagel deserves that credit. I just made a sticky thread to have everything in one place.
I think you followed everything perfectly and did all that you could, you've read around a lot and tried everything you found. My guess is somehow your system partition is in a read only state and simply isn't letting anything write to it. That would explain what is happening.
What I would do is treat this as a hard brick. I would do one of 3 things:
1) try to hardbrick the phone yourself, maybe run the old version of casual and flash the insecure aboot file to unlock the phone, this obviously will corrupt the 4.3 bootloader and hardbrick the phone. Then you could use the hardbrick restore guide to fix it that way.
2) or you could send it in "as is" for jtag that will write the bootchain for you and most likely fix the problem.
3) try to use the methods in this thread but use all the 4.3 files. If you could somehow get this to work you should write a guide for it and I'll post it in the sticky. I think you have enough know how to attempt it.
http://forum.xda-developers.com/showthread.php?t=1840030
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I tried the method you posted under 3) and Odin is still stuck on Initialzation
As for hard bricking it myself, it does look like that's my only choice now since booting into download mode does nothing for me since I can't flash anything. When you talk about the insecure aboot file from casual, can you please be more specific? I looked at the casual thread (http://forum.xda-developers.com/showthread.php?t=2332825) and in the jar file I downloaded, there's a Scripts folder, under which there's a d2vzw toolkit zip file, in which there's a aboot.mbn file. Is this what you were referring to?
If I can avoid JTAG I would prefer that. Guess my next goal is to hard brick then try the write to SD Card and boot method.
thebballkid said:
I tried the method you posted under 3) and Odin is still stuck on Initialzation
As for hard bricking it myself, it does look like that's my only choice now since booting into download mode does nothing for me since I can't flash anything. When you talk about the insecure aboot file from casual, can you please be more specific? I looked at the casual thread (http://forum.xda-developers.com/showthread.php?t=2332825) and in the jar file I downloaded, there's a Scripts folder, under which there's a d2vzw toolkit zip file, in which there's a aboot.mbn file. Is this what you were referring to?
If I can avoid JTAG I would prefer that. Guess my next goal is to hard brick then try the write to SD Card and boot method.
Click to expand...
Click to collapse
Just make sure you have all the equipment for a hard brick restore first.
There's an old version of casual, not the most recent one, it's on the thread. It has an option to unlock the device. I'm not sure it will work in this circumstance, but if you can get it to recognize your phone you should be able to select that option only.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Just make sure you have all the equipment for a hard brick restore first.
There's an old version of casual, not the most recent one, it's on the thread. It has an option to unlock the device. I'm not sure it will work in this circumstance, but if you can get it to recognize your phone you should be able to select that option only.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
thebballkid said:
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
Click to expand...
Click to collapse
Man you have a tough situation.
I'd just get it a jtag repair. It'll start you clean and you can start over. I can't think of anyway to force download mode to write something to your phone.
That other guide is your exact symptom, but we don't have a way to fix a read only state on a 4.3 system.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
thebballkid said:
Casual won't recognize the phone
I tried flashing a GSM radio and it hung on initialzation again. Am I somehow stuck between a soft and hard brick now?
Click to expand...
Click to collapse
Technically you're softbricked in a read only state.
Sent from my SCH-I535 using Tapatalk 2
NEED HELP
I have the same problem as the OP. Nothing will work. Any ideas? :/. I have tried absolutely everything