Well...
I stupidly deleted everything of my phone as I felt as though it needed a fresh start.
Now I cant get past the samsung and yellow triangle boot phase.
I can enter recovery mode and download mode and have been messing around with ODIN all day to try get this thing to work.
From the reading I've done I realize that I will need to flash the ROM via ODIN but have no idea how to approach this.
Is this a soft brick? Or have I screwed my phone completely?
How do I go about fixing this problem?
Thanks.
chopzor said:
Well...
I stupidly deleted everything of my phone as I felt as though it needed a fresh start.
Now I cant get past the samsung and yellow triangle boot phase.
I can enter recovery mode and download mode and have been messing around with ODIN all day to try get this thing to work.
From the reading I've done I realize that I will need to flash the ROM via ODIN but have no idea how to approach this.
Is this a soft brick? Or have I screwed my phone completely?
How do I go about fixing this problem?
Thanks.
Click to expand...
Click to collapse
yea it is soft brick ... and if you are running custom Tom you can just reflash it on recovery mode..
or you can flash it thru Odin
Related
This is for the people who got a new captivate through return or purchase or how ever you obtained it. If you tried flashing a new rom and now are stuck at the att boot loop or the battery loop and your phone will not boot up here is help.
1. See if your phone will do the 3 button recovery to get into download mode.
2. If you cant get into download mode you might need a Jig or do the resistor technique to get into download mode.
3. See if this odin (I897UCJF6-final-OCD-REV0.exe) will flash your phone back to the stock 2.1.
4. If after flashing the 2.1 odin and your phone still has boot loop then try the 2.2 stock odin
5. Next do the same as previous but try with this odin (I897UCJI6-OCD-REV02-Low-designgears_1_.exe) which is the 2.2 stock odin.
Note all of these flashes require you to be in download mode and have odin fired up on your pc the plug in your phone so odin can recognize it so
a. be in download mode (not connected to PC)
b. have odin open on pc
c. Plug in phone to pc and start odin.
odin likes to stop flashing when setting pit file so if it freezes give a sec and if nothing try it again.
if odin freezes on the set pit file your phone will have the dreaded phone to pc icon during boot but dont panic set your phone into download mode and try again.
If any questions should arise PM me or leave a comment and others and i will try and help.
Took me two days to fix my phone after flashing to stock to root it but i hope this helps you turn your 400 dollar paper weight back into a phone.
umm thanks but we know how to use odin there are a million guides in every ginerflash and captivate sticky.
and the 2.2 odin is actually an internal samsung beta 2.2 not official.
returning it with the designgears 2.2 will be an obvious warranty breach if they notice.
and your Step 4 and 5 seem to say the same thing... "flash 2.2 odin" (which isnt official)
and THE REAL FIX FOR THE BOOTLOOP:
reboot into RECOVERY > (not download)
wipe cache and data! (or factory reset)...
DONE!
reboot into the rom that you were trying to use!
takes 20 seconds and no reflashing anything.
i ran into this a few days ago while trying to root a friends captivate(1008) purchased from walmart recently. after trying to flash back to stock i was stuck on att boot loop and could not get into download mode via button combo to save my life. tried everthing minus a jig....after getting fed up with it, i sat it aside. to my amazment, after about 10-15 minutes the mf booted up. i had to use adb to reboot into download mode. flashed with odin(from aio toolkit) back to 2.1. everything worked fine, no problems except for one thing...sometimes it will still loop for a few minutes before it boots...sometimes it boots right away. Im still investigating the whole ordeal but my point here is: if you think your phone is stuck on att screen, just let it sit for a while....maybe a long while. and it should boot. then use adb to get back to download mode. i read every forum post on the web about this issue...just found this thread and thought id give ppl a heads up. hope it helps
I'm stuck in a bootloop right now on the Galaxy S animation screen and this wipe cache and data method doesn't seem to work for me.
so i recently tried flashing a darky rom theme onto my captivate running mosaic 8.
it worked the first time. then i tried another theme didnt like it, so flashed the darky rom one, and now, bootloop....
i can get my cappy into download mode, but odin doesn't recognize it.
i cannot get it into recovery mode with holding down the volume up and down and power button.
i need help
--edit--
fixed!
biggest help i have EVER had in custom roms/rooting etc..
http://forum.xda-developers.com/showthread.php?t=1351224
TRusselo said:
umm thanks but we know how to use odin there are a million guides in every ginerflash and captivate sticky.
and the 2.2 odin is actually an internal samsung beta 2.2 not official.
returning it with the designgears 2.2 will be an obvious warranty breach if they notice.
and your Step 4 and 5 seem to say the same thing... "flash 2.2 odin" (which isnt official)
and THE REAL FIX FOR THE BOOTLOOP:
reboot into RECOVERY > (not download)
wipe cache and data! (or factory reset)...
DONE!
reboot into the rom that you were trying to use!
takes 20 seconds and no reflashing anything.
Click to expand...
Click to collapse
ok cmw is not mounting cache or anything else any other ideas
I need help guys,
I used Odin to root the phone and did my first custom rom which is the clean rom...it went through the process and when it was about to reboot i got the system software not approved by verizon and take phone to store
I have been told to odin back to stock but it wont let me. The stock image on odin wont work it says fail
I tried the first method and used odin in download mode to flash the stock image
Failed:
This is what I get
added
Odin V3 engine
File Analysis
all threads completed (succeed 0 / Fail 1)
In the Odin Download mode on the phone the top left reads as follow
Odin Mode (Red Letters)
Product Name (SCH-I535)
Custom Binary Download : Yes (1 counts )
Current Binary Custom
System Status Custom
Qualcomm Secureboot: Enable
One thing I gotta mention is that when I got the phone last week it had an OTA update from Verizon which I did install and then a few days later I rooted the phone and when I tried to use Clean Rom it gave me the dreaded Verizon message
Sounds like you didn't unlock the bootloader.
Ya your bootloader is locked again ... unlock it and redo the steps everything should be fine after that
Guys I know that the bootloader is locked but i cannot get back to stock to unroot phone and then unlock the bootloader
Odin recognizes phone but the stock image goes into fail mode right away
I cannot get into recovery and the only thing I can do is go to download mode and Odin but nothing else
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Stranger_84 said:
http://forum.xda-developers.com/showthread.php?t=1840030&highlight=jtag
http://forum.xda-developers.com/showthread.php?t=1798850
http://rootzwiki.com/topic/29256-tutorial-rootrecoverybootloader-unlockicsjb-verizon-galaxy-s-iii/
http://www.android.gs/fix-bricked-verizon-galaxy-s3/
one of these may be able to help you ... i lost the original link i had but saved these for bootloader issues hope they help they should
Click to expand...
Click to collapse
You are aware he can Odin flashed the latest OTA instead of that you have provided. Here it is :http://forum.xda-developers.com/showthread.php?t=2046439. This will also help fix his phone being that it is recent. Forgot this link to get him back on track: http://forum.xda-developers.com/showthread.php?t=1974114.
i thought thats what he already tried? but yes you can odin any ota file being that an unlocked bootloader isnt needed.
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
I'm not sure being ive never had that issues ... im sorry and good luck
try flashing odin stock ROM, not bootchain
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
Did you put the file in PDA in Odin they only work if you checked PDA.
NYGiants4Natic said:
When I try the VRBLK3 chain it goes into set up connection for like 10 minutes on Odin with a fail at the end each time
Click to expand...
Click to collapse
I had a similar issue once. This helpful post by h3llsdr0id eventually got me up and running. Took a total of like 4 hours though lol.
http://forum.xda-developers.com/showpost.php?p=30569324&postcount=26
Make sure you have the correct files. This is for the original root66 so it's ICS. Once I booted up and activated I took the Verizon OTAs all the way to JB and then rooted/unlocked bootloader.
edit: I actually had to go back to ICS to reprovision my SIM so not sure you have to go through all of this. Try to odin stock JB ROM like mentioned above.
Thank YOU so much guys you have made my day.
After trying all last night and today I got it back to stock with the OTA file through ODIN. That is all I needed and it went right back to brand new stock phone using 4.1.1
WOW.
I thought I was going to have a dead phone.
Thank you all
Glad you got it up and working!!!!!
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
I'm having the same problem and can't get into download mode
Gatanater said:
Yea I had the same problem but all it needed was a handy flash back to stock. The good thing with making these mistakes is that if it happens again you know what to do.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
You have to get into download mode to use Odin. It will go into download mode, if you will search, there are ways to pull battery along with button combo to get it there. After rooting, use EZ Unlock 1.2 and that will unlock your bootloader without then unauthorized message from Verizon. Make sure you use only that version, the others don't work.
Re: I'm having the same problem and can't get into download mode
mj76 said:
Hi there,
Could someone please help me. I bricked my phone 3 days go and went through odin and root66 stock to unbrick it. I installed CWR and backed up everything, then i purchased triangle away to reset the flash counter. When I did that I got the software not authorized by verizon error screen. It won't let me get into download mode or recovery. Can I still try to use odin? What should I do? I'd really appreciate some help today is the 4th day I have been trying to fix my phone, only to make it worse.
Thank you in advance
Click to expand...
Click to collapse
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
flammablepez said:
Pull battery, hold volume down+home+power keys while you put the battery back in. If that's too many buttons to fumble with at the same time you can try pulling battery, put it back, hold all three keys while plugging it into your computer. My old phone worked that way, idk about the s3. You SHOULD get the download triangle and it asking you if you want to continue. Hit volume up to continue then plug it in and odin should recognize it. Get the stock rom image to flash in the PDA slot of odin. Accept the OTA's until you're up to date then unlock bootloader, root, then flash custom roms/kernels AFTER you've done the appropriate reading. Theres a sticky in development takes you step by step on how to unbrick, then unlock and root. Those should help once you get into download. Hope this helps! :fingers-crossed:
Click to expand...
Click to collapse
Thank you for your response. I tried pulling the battery out and holding volume down, home and power keys at the same time while putting battery in, even as i plugged it into my phone, but nothing but the unauthorized error screen comes up. I should note that my phone is note 2 not s3. I apologize for posting it here, but this thread seemed to be just like the problem i was having.
So a few weeks ago I rooted and installed a custom rom on my cousins tablet. He said it started acted weird and then said his rom had an available update so he downloaded and installed it. Now its stuck in a boot loop. I tried to tell him to put it in recovery mode but he ended up putting it in odin instead. I then told him to reboot it into recovery mode saying doing the opposite of what he just done, given the fact that this is all thru texting bc he lives 500 miles away. He said that the tried recovery mode but just shuts off instead. Would odin wipe the recovery image off his tablet? If so what can he do to fix it? I told him that he can try to go thru odin and reinstall cwm recovery again but I'm just taking a wild guess at it. I feel bad and personally responsible for the problem bc I convinced him to let me work on it but its hard to provide tech support when its not in front of u...any ideas or solutions to this?
Thanks!
Sent from my CM10 Samsung Skyrocket
jrodbrown58 said:
So a few weeks ago I rooted and installed a custom rom on my cousins tablet. He said it started acted weird and then said his rom had an available update so he downloaded and installed it. Now its stuck in a boot loop. I tried to tell him to put it in recovery mode but he ended up putting it in odin instead. I then told him to reboot it into recovery mode saying doing the opposite of what he just done, given the fact that this is all thru texting bc he lives 500 miles away. He said that the tried recovery mode but just shuts off instead. Would odin wipe the recovery image off his tablet? If so what can he do to fix it? I told him that he can try to go thru odin and reinstall cwm recovery again but I'm just taking a wild guess at it. I feel bad and personally responsible for the problem bc I convinced him to let me work on it but its hard to provide tech support when its not in front of u...any ideas or solutions to this?
Thanks!
Sent from my CM10 Samsung Skyrocket
Click to expand...
Click to collapse
if he can get in to download mode, tell him to download the latest firmware for his product from sammobile.com, then flash it through Odin. it would wipe everything including the recovery image - but the firmware should install stock recovery on his tab so he can do a wipe data/factory reset from there. Don't feel too bad, i'm sure he knew the risks (unless you skipped that bit)
P.S Which tab is it? which rom was installed?
He got it to work by reflashing cwm thru odin and everything booted up normally from what I understand with all his apps still there.
He's on the 7" tab 2 and running the newest pacman rom.
Sent from my CM10 Samsung Skyrocket
This is a very noob thing to do.
I have a Verizon S3 with a broken screen. So I was fooling around with it without reading the forum.
I have a fresh MF1 installed, then rooted and also installed ROM Manager. The foolish thing is that I used ROM manager to boot into recovery.
The boot failed. Now the stock recovery is gone. The worst thing is that, now I can't even get into Odin. The phone kept vibrating and give the yellow triangle, saying, System software not authorized by Verison wireless has been found on your phone.....
I do not know what to do now. I think the first thing I have to do is to get rid of the CWM recovery, which never worked in this case. Then I can get the Odin back.
I tried the download button combo. I got to Odin just once. And the Odin session did not complete stating that it could not find a COM port. So Odin is no go now.
Do I have to get on adb or bootloader level? How?
deleted.
Well, I think I made a fool of myself.
After repeated failures to boot into Odin, I put the phone to some rest. Then I just tried it one more time and my lovely Odin has returned. So I flash the phone with the stock ROM and the phone is back to normal.
I was thinking I have another hard bricked phone. I think by pulling the battery and put the phone to rest, it changed something.
BaSingSe said:
Well, I think I made a fool of myself.
After repeated failures to boot into Odin, I put the phone to some rest. Then I just tried it one more time and my lovely Odin has returned. So I flash the phone with the stock ROM and the phone is back to normal.
I was thinking I have another hard bricked phone. I think by pulling the battery and put the phone to rest, it changed something.
Click to expand...
Click to collapse
You got that warning message at boot because you didn't unlock your bootloader.
Sent from my SCH-I535 using Tapatalk
Hey guys,
I am totally freaking out because I was trying to flash my phone back to a somewhat stock position to erase it and just sort of get back to a stock place and then start flashing again. I tried keeping all the different instructions straight and I think I got turned around someplace.
This is where I am at for what is going on:
Flashed the VRALEC bootchain after I flashed the Stock rooted rom root66_VZW_I535VRBMB1.tar.md5.
The phone currently is accessible for the Odin download mode and when it boots I show the Samsung logo with the lock logo that is unlocked. I am totally not sure where to go from here and need some serious help with what to do next. The phone seems to be simply stock at booting on the 4Glte screen with the Verizon logo.
Any help would be very much appreciated as I am so mixed up as to what to do I don't know where to go and I don't want to make matters worse.
:crying:
NeCr0mStR said:
Hey guys,
I am totally freaking out because I was trying to flash my phone back to a somewhat stock position to erase it and just sort of get back to a stock place and then start flashing again. I tried keeping all the different instructions straight and I think I got turned around someplace.
This is where I am at for what is going on:
Flashed the VRALEC bootchain after I flashed the Stock rooted rom root66_VZW_I535VRBMB1.tar.md5.
The phone currently is accessible for the Odin download mode and when it boots I show the Samsung logo with the lock logo that is unlocked. I am totally not sure where to go from here and need some serious help with what to do next. The phone seems to be simply stock at booting on the 4Glte screen with the Verizon logo.
Any help would be very much appreciated as I am so mixed up as to what to do I don't know where to go and I don't want to make matters worse.
:crying:
Click to expand...
Click to collapse
Pull the battery, boot into recovery (hold volume Up, power, and home), then do a Factory reset.
SlimSnoopOS said:
Pull the battery, boot into recovery (hold volume Up, power, and home), then do a Factory reset.
Click to expand...
Click to collapse
Booting into recovery gives me some message about unauthorized software as I had tried that. I was trying this method but the VRALF bootchain was showing as invalid. I just found a copy of it on invisiblek's site and flashed that and was going to continue with that method trying to get this working. I will update once that has gone through as the stock.vzw_root66.tar image is flashing now. Wish me luck!
Ok, so this time when it finished flashing it rebooted, then it showed the android with the spinning hexagon type thing that you would see when doing a rom backup or something of the sort. I pulled the battery rebooted and did a factory reset along with wiping cache directory and now I am waiting at the 4Glte screen again... Keeping fingers crossed and hoping this works.
AND OMG AWESOME!!!!!
Man, now it is time to get back to flashing. Thank you so much SlimSnoopOS for that last thing I was missing, I really appreciate it.