Samsung galaxy SCH-I535, rooted, stock rom (im pretty sure it was 4.3), Power button removed. The other day I was driving, I had my phone sitting on the passenger seat, checked the time everything was fine on the phone. Checked my phone again about 20 mins later and nothing, black screen. I knew the battery was full and I didn't have a charger to turn it back on (no power button) so I forgot about it until I got home. When I got home I went to turn it on ( hold down home + vol down while plugging it in.) pops up into download menu and I hit cancel and back to battery charge mode. I recently changed out the screen (after I removed the power button) so i thought maybe some loca glue got into the power button contacts on the board. I tore it down and thoroughly cleaned out my frame and board, put back together and now it will boot into download mode, hit cancel, popps up with samsung galaxy s3, then the samsung splash screen, then the verizon splash screen, then back to black screen/charge mode at that point every time. I can get into download mode but if I try to get into recovery it just vibrates every 5 sec or so on a black screen until I release a button then goes to charge mode. I am downloading stock firmware I535VRUCNC1 right now and plan to flash with ODIN am I on the right track or could someone point me in the right direction?
Thanks to all XDA has saved me multiple times in the past this is the first time I have posted and I'm sure you guys can help a noob out again THANKS ALL!!
Ok So I tries to flash both ML1 and NC1 also with a re-partition via ODIN 3.07 with a fail every time.... Finally got ML1 to flash but now it bootloops at the galaxy s3 logo again.... frustrated still cant get into recovery
If Odin is failing every time your more than likely on the locked bootloader. If so you cannot flash any custom roms which is why it isn't working
Sent from my Cataclysm Nexus 5
I am not flashing any custom roms.... both of the roms I am trying to flash (NC1 and ML1) are both stock 4.3 roms....
I'm pretty sure I am on a locked bootloader I never did anything with safestrap or never tried a custom rom. on a side note when I used to boot my phone up it showed a picture of an unlocked lock and said custom under it (never sure why it did this unless maybe rooting with towelroot) but it no longer shows this icon when boot(looping)
SpinalMushroom said:
I am not flashing any custom roms.... both of the roms I am trying to flash (NC1 and ML1) are both stock 4.3 roms....
Click to expand...
Click to collapse
If your on NC1 you cannot flash ML1 as it's the previous rom/modem. You'll have to flash back to NC1 using Odin. Even if it is stock what your trying to do will not work
Take a look at this thread, it should be of help to you
http://forum.xda-developers.com/showthread.php?t=2653902
Sent from my Cataclysm Nexus 5
I figured as much that I cannot go back to ML1 after the NC1 update but I got the phone used and am not totally sure which one it had so I tried both of them. And the links in the thread you posted are the exact same as the ones I am using following this guide http://forum.xda-developers.com/showthread.php?t=2586319
SpinalMushroom said:
I figured as much that I cannot go back to ML1 after the NC1 update but I got the phone used and am not totally sure which one it had so I tried both of them. And the links in the thread you posted are the exact same as the ones I am using following this guide http://forum.xda-developers.com/showthread.php?t=2586319
Click to expand...
Click to collapse
True they point to the same thing but are by two separate people. Just trying to help here
Sent from my Cataclysm Nexus 5
True that... I am just trying to give as much information as I can to anybody who might see this thread
think Im at the point of giving up... Will try again to flash NC1 when I get off work... If I get fails again I guess ill have to finda new board for it. Thanks for trying anyways.
ok so I can (ALMOST) get into my recovery. boots recovery but I get error message "Secure fail: Kernel". Tried Flashing the stock recovery as well there is a .tar file on here I just don't want to look around for the link right now. I can flash the recovery via ODIN with success.... still cant boot recovery on the phone
ShapesBlue said:
True they point to the same thing but are by two separate people. Just trying to help here
Sent from my Cataclysm Nexus 5
Click to expand...
Click to collapse
Seems like you are the only one trying to help..
I don't know if it is possible but could I try going up to 4.4.2? I think I'm also gonna try the Hardbrick fix on here cuz why not I don't think it'll hurt it any
SpinalMushroom said:
Seems like you are the only one trying to help..
I don't know if it is possible but could I try going up to 4.4.2? I think I'm also gonna try the Hardbrick fix on here cuz why not I don't think it'll hurt it any
Click to expand...
Click to collapse
Yea you could try that if you want to. You will have to unroot first. Some people will try to help where they can, I can't really speak for anyone else
Sent from my Cataclysm Nexus 5
ShapesBlue said:
Yea you could try that if you want to. You will have to unroot first. Some people will try to help where they can, I can't really speak for anyone else
Sent from my Cataclysm Nexus 5
Click to expand...
Click to collapse
How do I Unroot without getting into recovery?
SpinalMushroom said:
How do I Unroot without getting into recovery?
Click to expand...
Click to collapse
By chance are you using supersu?
Sent from my Cataclysm Nexus 5
ShapesBlue said:
By chance are you using supersu?
Sent from my Cataclysm Nexus 5
Click to expand...
Click to collapse
I believe so... cant remember tho honestly.
SpinalMushroom said:
I believe so... cant remember tho honestly.
Click to expand...
Click to collapse
If you have supersu there's an option to unroot within the app but off hand I forget if its only in the pro version or not. I'll look around to find another option
If not here's another possible option
http://forum.xda-developers.com/gal...laxy-siii-stock-updates-t1710613/post27407556
Sent from my Cataclysm Nexus 5
Stock 4.4.2 NE1 is currently flashing its already gotten farther than NC1 or ML1 will keep you posted... If I can't boot I don't think I can get into SU
SpinalMushroom said:
Stock 4.4.2 NE1 is currently flashing its already gotten farther than NC1 or ML1 will keep you posted... If I can't boot I don't think I can get into SU
Click to expand...
Click to collapse
That's great man. Glad I could help. Let me know if there's anything else I can help with
Sent from my Cataclysm Nexus 5
ShapesBlue said:
If you have supersu there's an option to unroot within the app but off hand I forget if its only in the pro version or not. I'll look around to find another option
If not here's another possible option
http://forum.xda-developers.com/gal...laxy-siii-stock-updates-t1710613/post27407556
Sent from my Cataclysm Nexus 5
Click to expand...
Click to collapse
ShapesBlue said:
That's great man. Glad I could help. Let me know if there's anything else I can help with
Sent from my Cataclysm Nexus 5
Click to expand...
Click to collapse
4.4.2 flashed successfully.... still bootlooping tho... when I try to get into recovery it popps up in blue "booting recovery" then it goes back to the galaxy s3 logo then back to charge mode... Im not sure but it seems to be the power button causing this since it is the power button you hit to execute commands in recovery (I think)... but since the power button is removed it looks like im back to finding a new board
Related
I just got a Samsung Captivate two days ago, and while trying to root it, I seem to have bricked it. When trying to flash initial root zip in stock recovery, the install always failed because it failed to verify the signature. Then I got the bright idea of ODIN one clicking back to stock, thinking maybe that'd help. Now, if the phone is unplugged, I get a boot loop with the white at&t screen, and if I try to plug it in to get into download mode, it just blinks the battery status screen, showing an empty battery. I tried replacing the battery with a fresh one, but no change. Any help would be greatly appreciated.
should have just ran a search for " captivate signature verification ".. million threads... and fix in my signature...
so you odin flashed to stock then flashed the root kernel?
or just flashed to stock? What stock? there are many. theres 3 odin packages and 4 one clicks just for ROGERS.. there are even more for att. some even ACTUALLY BRICK YOUR PHONE.
having the WRONG kernel for wrong rom causes bootloops.
you are not bricked. bricked your screen doesnt come on.
you really need to research.
Sounds like you flashed jf6 on a froyo shipped phone, losing your 3 button ability in the process.
shagdaddy said:
I just got a Samsung Captivate two days ago, and while trying to root it, I seem to have bricked it. When trying to flash initial root zip in stock recovery, the install always failed because it failed to verify the signature. Then I got the bright idea of ODIN one clicking back to stock, thinking maybe that'd help. Now, if the phone is unplugged, I get a boot loop with the white at&t screen, and if I try to plug it in to get into download mode, it just blinks the battery status screen, showing an empty battery. I tried replacing the battery with a fresh one, but no change. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Please, you have gotto give us a step-by-step on what you did.......especially on what you did !!!!
mrhaley30705 said:
Sounds like you flashed jf6 on a froyo shipped phone, losing your 3 button ability in the process.
Click to expand...
Click to collapse
we have a winner!!
op search usb download mode jig...easy to amke cheap to buy. it eill force dl mode and from there you can flash ANY other stock firmware than JF6...
One click root is much easier than whatever you tried doing
Sent from my SAMSUNG-SGH-I897 using XDA App
I did the same thing. You will have to get the USB jig to reflash it. Get the stock 2.2 ROM and use super one click. Odin can get you back the clock work mod.
Sent from my SGH-I897 using Tapatalk
studacris said:
we have a winner!!
op search usb download mode jig...easy to amke cheap to buy. it eill force dl mode and from there you can flash ANY other stock firmware than JF6...
Click to expand...
Click to collapse
I won! Ok, where's the bacon for winner?
Just picked up my G3, rooted and unlocked bootloader as soon as i got home. Downloaded one of the jelly bean roms and cwm, did a backup then flashed the rom. Everything looked fine but the screen went dark after the boot animation then nothing. Wont power up or reset using the power home volume combo. What the heck do i do now, thanks for any help.
Might be a stupid question, but have you pulled the battery?
Be more specific.
VZW GALAXY S 3 4G LTE
Do YOUR homework first
How about reading all the threads about unbricking. It certainly seems you did not read all the threads about rooting the phone. Do that too.
Finally, and I know this is not that helpful. Don't screw with a new phone. Use it at least for a month to make sure there are no problems with it.
That being said, there is plenty of information about how to handle your problem here in xda. Read all that and try what has already been posted before asking people to solve your self inflicted problem.
BTW when you do ask for help specify exactly what you did, with what script. I.E. don't ask someone to solve your problem without you taking the time to be very specific about how you got there.
pull the battery and go into recovery or odin and fix it.
Dead battery?
Sent from my Transformer TF101 using xda premium
Skubacb - Don't be a douche buddy. If you do not have any thing to add then shut the **** up.
With that being said I have been rooting phones for years, never had an issue when I couldn't get the phone to at least go into recovery. The phone is dead. Battery was fully charged and I have done a battery pull. It is a Verizon G3. I have read the unbrick articles but none explain if the phone will not boot into recovery. If someone could could just point me in the correct direction I would greatly appreciate it.
How did you actually do the flash? Odin? Some other way? As noted, more details are needed.
I flashed the new rom using Rom manager, went in to revovery and flashed it
jmill75 said:
I flashed the new rom using Rom manager, went in to revovery and flashed it
Click to expand...
Click to collapse
I don't believe rom manager is supported for our phone yet. U need to flash straight from recovery. That said I'm sorry I'm not sure where u go from here.
Sent from my SCH-I535 using xda premium
If you can't get into either recovery , or download mode you maybe SOL. However I would take this to IRC and see if someone can help on there. #verizons3 channel.
If the phone is under warranty, one other alternate solution is to take it into a VZW store and say it won't start. Of course I'd only go that route if I couldn't get it going any other way. On the plus side, your could at least confirm that battery didn't die on you.
Looks like you forgot to flash the insecure bootloader, buddy.
Sent from my SCH-I535
Rom manager is supported I flashed clockwork there And the 3 cm nightlies
Sent from my SCH-I535 using Tapatalk 2
Keep this discussion to technical solutions only, please. Leave gray area ethics out of it.
JMink said:
I don't believe rom manager is supported for our phone yet. U need to flash straight from recovery. That said I'm sorry I'm not sure where u go from here.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Completely incorrect.
mikeew83 said:
Rom manager is supported I flashed clockwork there And the 3 cm nightlies
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Me too, been doing it since 6.0.1.2
abissel22 said:
Looks like you forgot to flash the insecure bootloader, buddy.
Sent from my SCH-I535
Click to expand...
Click to collapse
I'm gonna go with this one (possibly). Did you unlock the phone? Sorry, did you say it won't boot into anything? Download/Odin mode? Recovery? Anything at all when you do the vol up/down, home key, and power button?
Idk if this would help but I'd order a downloader jig off ebay for a couple dollars and use that to see if it'll boot to recovery
Sent from my GT-I9300 using xda app-developers app
Me too
I went to turn on my Verizon SGS3 on this morning and nothing happened. I have not even rooted it yet. It was charged when I turned it off 5 minutes before that and even did a battery swap. Phone is completely dead. Will not turn on. I have had it since it first came out, so I called Verizon and they are over-nighting me a "like-new" one. I hope I don't hear more of these stories.
jmill75 said:
Just picked up my G3, rooted and unlocked bootloader as soon as i got home. Downloaded one of the jelly bean roms and cwm, did a backup then flashed the rom. Everything looked fine but the screen went dark after the boot animation then nothing. Wont power up or reset using the power home volume combo. What the heck do i do now, thanks for any help.
Click to expand...
Click to collapse
I had a similar issue. If you do the volume/home/power combo (try both volume buttons separately, i forgot which one worked) and hold them through the initial Samsung logo it should put you into download mode, where you can Odin back to stock. I used PureMotive's Unbrick method in the Dev section (I think) and it took all of 20 min. Just make sure to follow the directions carefully.
Sent from my SCH-I535 using xda app-developers app
Is there a difference is button sequence between recovery and download mode? (I thought it was the same thing)
Sent from my SCH-I535 using XDA Premium App
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
yup your bootloader is still locked
check the downloads thread and use version 1.2.
That means your boatloader is locked. You now must Odin back to stock and start over. Droid style has a guide stickied in the development thread. Follow section 6 of it.
Next time use ez unlock version 1.2 to unlock you boatloader.
Sent from my SGS3 running Eclipse 2.1
downloads list
http://forum.xda-developers.com/showthread.php?t=1850506
tekrhino said:
Just a wild guess, but me thinks your bootloader is still locked! But I'm not sure that will even apply because I rooted my device before unlocking the bootloader. But I rooted my device via ODIN first.
You can try EZ-Unlock via the Market. The GUI is still very buggy and will show the status as unknown but the internal workings of the app works good.
You got nothin to loose in trying. Go back to stock and give it another whirl after you've unlocked the bootloader.
Of that fails then I would suggest using the tried and true method..ODIN.
G'luck!
Click to expand...
Click to collapse
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Prophotog said:
Thanks. I can't get past the warning dialogue screen. Pulled the battery, no good. PC can't see the phone with USB.
Click to expand...
Click to collapse
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Thanks to everyone!! Looks to be a long night. :>)
tekrhino said:
Yikes, ok
You have to get into DOWNLOAD MODE.. Power+ Volume Down+ Home key at the same time after a fresh battery pull.
Do a search on the Development forum to set up Odin on your PC.
YOU Must FOLLOW directions EXACTLY our you will have very expensive BRICK!
This forum could help:
http://forum.xda-developers.com/showthread.php?t=1762709
Or even better, this one:
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
I lol'ed at your post. A little dramatic, don't you think? He's not even close to bricked. Just Odin from download mode back to stock, and redo the steps with bootloader unlock.
Here is a gift (working ez-unlock v1.2)
http://dl.dropbox.com/u/42057363/com.mmmeff.ez.unlock_3.apk
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Prophotog said:
Still having issues. I "think" I am in the download mode. Screen says Downloading.... It has Odin in red in top left corner. Device connects with Odin. BUT I am not getting a PASS message when flashing VRALEC bootchain. Last text line in Odin is: <OSM> Leave CS...
I have tried several attempts.
Suggestions?
Click to expand...
Click to collapse
No need to do the boot chains. Just follow section 5 of this guide and I recommend root 66 for the ROM you flash
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SGS3 running Eclipse 2.1
tekrhino said:
@Techsavvy
Yeah, perhaps a tad overdone on the theatricals.
Cut me some slack, I'm taking acting classes..lol
And... I know... I know..don't quit my day job!
Click to expand...
Click to collapse
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Prophotog said:
Just rooted my new SGS3 using New Root Method Released for Verizon’s Galaxy S3, No Odin Required. i did the data & kelvic wipe then install Clean Rom 5.0. All progressed without a hitch. Even backed up with CWM prior to flash.
I rebooted into the new rom and got this: System software not authorized by Verizon Wireless... rebooted several time with same result.
What can I do now? Thanks for your help.
Click to expand...
Click to collapse
And just for future reference, it's Dalvik, not Kelvic
Sent from my SCH-I535 using xda app-developers app
Prophotog said:
I appreciate the theatricals...however, I am having issues with Odin. Can't get the Pass message. I assume the "Downloading..." text means I'm in the download mode. Tried several attempts. I AM glad I'm not close to bricked too! Can't afford $600 or a divorce. Might have to sell a camera instead.
Click to expand...
Click to collapse
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
kintwofan said:
Just a heads up. You can get a real brick with Odin and easy. Follow the guide I linked earlier to a t and you'll be fine
Sent from my SGS3 running Eclipse 2.1
Click to expand...
Click to collapse
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Prophotog said:
You are a scholar and a gentleman!! THANK YOU very much. You can have a portrait session on me any time. Name the time and place.
Click to expand...
Click to collapse
Cool, I take it you're up and running again. Just make sure you use ez unlock 1.2 next time. And the positive is you're an Odin pro now!
Sent from my SGS3 running Eclipse 2.1
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Alex0826 said:
Hi, I have a Verizon S3 flashed to Boost Mobile. I tried to gain root by flashing a stock rooted Rom and messed up the flash. I had to take it back to be flashed again  Now I'm more cautious before hand. I should have backed it up before attempting it, I know I know lol can anyone shed some light on how to update a flashed phone as well as how to root it. I could really use the help 
Also after I messed up the boost flash I paniced and flashed a sprint kernel hoping this would fix the problem. Since then anything that I've tried to view including taking camera shots and web browsing if done in landscape mode will be upside down, any remedy for this problem? I know now... root first, flash later. 
Sent from my SPH-L710 using XDA HD
Click to expand...
Click to collapse
Sprint kernel is causing the inversion. Flash a vzw kernel. Read first flash later.
Sent from my SCH-I535 using xda app-developers app
Who ever did your flash might not done it right cause ya not supposed to lose a flash like that unless he didn't do things right. I can factory reset mine and I wont loose flash
Sent from my SPH-L900 using Tapatalk 2
Sooo....
Been reading, researching and studying for a little more than two weeks now on rooting my S3, flashing roms, kernels, etc. Most of the 2 weeks my S3 has been rooted. I felt brave enough early on to do that, but only worked up the courage to flash my first rom this morning. Using the guide found here...
http://forum.xda-developers.com/showthread.php?t=1762709
...I flashed the newly updated "SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-10-13 r169" and to my delight it worked like a charm! For most of the day today I've been learning the ins and outs of my new rom and loving it!
This evening I decided that due to my success I'd give flashing a kernel a try. I apparently should've quit while I was ahead. I found this kernel : "SGS3-VZW-kernel-jb-cm-u-10312012" I followed the above mentioned guide again and followed all of the instructions up through step 6. I unzipped the kernel, and prior to rebooting I was unexpectedly asked a question about if I wanted to restore the stock recovery (if I remember it correctly). I chose the "go back" option (to see if I could just reboot without worrying about that question) in CWM and my S3 rebooted itself at that point.
Unfortunately the reboot process got through the quick glimpse of "Samsung", then the "Galaxy S3" screen then went black and that was it. I waited a while, removed the battery to be sure it was off and tried starting up again. Same result. I've tried rebooting into recovery (vol down/ home/power) but it just shows me the same two screens and goes black, never going into recovery and never taking me to the download screen.
I decided to plug the S3 into my computer to see if I could see it in Windows Explorer (I couldn't) but I fired up Odin and it is showing that it recognizes the S3 is plugged in in the ID:COM box.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem? Or does it not really matter at this point....is it hard bricked? I survived a soft brick last week so I have the stock rom all ready to go, but I don't want to just try Odin'ing it in without the advice of those more schooled in this than I am.
I'm not a complete idiot. My device is a Verizon Galaxy S3, I535. I've been very careful about choosing the correct roms and kernels for my device....at least I thought I had.
Any suggestions and/or advice? Perhaps I should blow the dust off my Droid X to use until I send the GS3 out for JTAG repair. Heh.
Thanks in advance from a very humbled Noob.
Well did you try to put it in download mode not recovery but download
I don't believe it's hard bricked i think you can get past this of you did put it in download mode and Odin sees it i would push the ROM
Sent from my SAMSUNG-SGH-I577 using xda premium
---------- Post added at 07:48 PM ---------- Previous post was at 07:44 PM ----------
On my phone i have to take the battery out hit the volume down button and power button at the same time then plug into the computer then it goes into download mode. It sounds like you know how to do it..
Sent from my SAMSUNG-SGH-I577 using xda premium
djteague said:
Sooo....
Been reading, researching and studying for a little more than two weeks now on rooting my S3, flashing roms, kernels, etc. Most of the 2 weeks my S3 has been rooted. I felt brave enough early on to do that, but only worked up the courage to flash my first rom this morning. Using the guide found here...
http://forum.xda-developers.com/showthread.php?t=1762709
...I flashed the newly updated "SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-10-13 r169" and to my delight it worked like a charm! For most of the day today I've been learning the ins and outs of my new rom and loving it!
This evening I decided that due to my success I'd give flashing a kernel a try. I apparently should've quit while I was ahead. I found this kernel : "SGS3-VZW-kernel-jb-cm-u-10312012" I followed the above mentioned guide again and followed all of the instructions up through step 6. I unzipped the kernel, and prior to rebooting I was unexpectedly asked a question about if I wanted to restore the stock recovery (if I remember it correctly). I chose the "go back" option (to see if I could just reboot without worrying about that question) in CWM and my S3 rebooted itself at that point.
Unfortunately the reboot process got through the quick glimpse of "Samsung", then the "Galaxy S3" screen then went black and that was it. I waited a while, removed the battery to be sure it was off and tried starting up again. Same result. I've tried rebooting into recovery (vol down/ home/power) but it just shows me the same two screens and goes black, never going into recovery and never taking me to the download screen.
I decided to plug the S3 into my computer to see if I could see it in Windows Explorer (I couldn't) but I fired up Odin and it is showing that it recognizes the S3 is plugged in in the ID:COM box.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem? Or does it not really matter at this point....is it hard bricked? I survived a soft brick last week so I have the stock rom all ready to go, but I don't want to just try Odin'ing it in without the advice of those more schooled in this than I am.
I'm not a complete idiot. My device is a Verizon Galaxy S3, I535. I've been very careful about choosing the correct roms and kernels for my device....at least I thought I had.
Any suggestions and/or advice? Perhaps I should blow the dust off my Droid X to use until I send the GS3 out for JTAG repair. Heh.
Thanks in advance from a very humbled Noob.
Click to expand...
Click to collapse
I think you flashed the kernel for cm, and not for touchwiz.
djteague said:
Sooo....
"SGS3-VZW-kernel-jb-cm-u-10312012"
Click to expand...
Click to collapse
This is an AOSP kernel. You only flash kernels if they match your rom. Synergy is a TouchWiz rom, so you would only flash a kernel if it states it's for TouchWiz. CM =CyanogenMod, an AOSP rom. AOSP = Android Open Source Project. Basically, AOSP is stock Android but on phones that don't ship with stock Android like a Nexus device.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem?
Click to expand...
Click to collapse
Yes, Odin flash a stock image then re-rooted and unlock your bootloader again. Just like what the other folks have said above. "Fool me once..." as the saying goes.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
This is an AOSP kernel. You only flash kernels if they match your rom. Synergy is a TouchWiz rom, so you would only flash a kernel if it states it's for TouchWiz. CM =CyanogenMod, an AOSP rom. AOSP = Android Open Source Project. Basically, AOSP is stock Android but on phones that don't ship with stock Android like a Nexus device.
Yes, Odin flash a stock image then re-rooted and unlock your bootloader again. Just like what the other folks have said above. "Fool me once..." as the saying goes.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Get him SlimSnoop. :laugh:
So reflashing the stock rom will in essence erase the AOSP kernel? It won't still be there to continue to cause problems after I Odin in the stock rom?
I'm getting an education now! Thanks so much for the continued help!
djteague said:
So reflashing the stock rom will in essence erase the AOSP kernel? It won't still be there to continue to cause problems after I Odin in the stock rom?
I'm getting an education now! Thanks so much for the continued help!
Click to expand...
Click to collapse
Odin flash will reset everything to factory settings. You'll just have to reroot and unlock once again.
Edit: Since I re-read your post. Volume down, home, and power will take you to download mode. This still works correct?
SlimSnoop you are turning what was a rather bummer of a night around! One final question before I push the start button in Odin...
I can flash the stock rom even though my S3 doesn't appear to be in dowload mode? (although the ID:COM box shows that Odin sees my phone)
Thanks again!
djteague said:
SlimSnoop you are turning what was a rather bummer of a night around! One final question before I push the start button in Odin...
I can flash the stock rom even though my S3 doesn't appear to be in dowload mode? (although the ID:COM box shows that Odin sees my phone)
Thanks again!
Click to expand...
Click to collapse
What do you mean it "doesn't appear to be in download mode"? When you pull the battery/reinsert then hold volume down, power, and home for like ten seconds, what does it do? Do you get the prompt to to boot into download mode?
SlimSnoopOS said:
What do you mean it "doesn't appear to be in download mode"? When you pull the battery/reinsert then hold volume down, power, and home for like ten seconds, what does it do? Do you get the prompt to to boot into download mode?
Click to expand...
Click to collapse
Don't hit no button if not in download mode.
Nevermind...my bad. Now my noobness is really starting to show. I had tried putting it into download when I first realized there was a problem, but apparently did something wrong. It worked this time, the stock rom is flashed and all is well.
Now, all that remains to be seen is whether or not this little adventure has scared me into being satisfied with my stock GS3 or if I go back to tinkering.
I truly thank you guys for holding my hand and getting me through this! Much obliged!
djteague said:
Nevermind...my bad. Now my noobness is really starting to show. I had tried putting it into download when I first realized there was a problem, but apparently did something wrong. It worked this time, the stock rom is flashed and all is well.
Now, all that remains to be seen is whether or not this little adventure has scared me into being satisfied with my stock GS3 or if I go back to tinkering.
I truly thank you guys for holding my hand and getting me through this! Much obliged!
Click to expand...
Click to collapse
Go back to custom roms and flash Synergy again!
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
drucquerkellan said:
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK thanks I'll try them in a little bit and report back here how it goes!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
You can still mount to USB through recovery and transfer a ROM zip over and then flash it.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
okzygen said:
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
Click to expand...
Click to collapse
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
mcmb03 said:
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
Click to expand...
Click to collapse
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
yeah, either way kies was probably at the bottom of the list for solutions since you were trying to put a different rom on your phone anyways
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Or the easiest of the options that I already mentioned 4 posts up... Don't even need to bother with adb or taking off your back cover. Plug in, mount, click-and-drag file transfer, unmount, flash, done.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I'm just glad you got it taken care of OP. Hopefully this thread will help others who may have a mishap while flashing ROMs.
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
This is incredible. Incredible how badly you almost screwed yourself over with, and incredible that Kies was actually helpful.
I installed Kies to backup contacts, once. After that? Thing crashes on updates, takes 30 minutes to load, hated any music I threw at it, didnt like my wireless transfer setting....
idk I had a pretty bad experience with Kies, i'm glad to hear that program isnt all useless.
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
Yea that part doesn't make sense though. Many times I've seen people try to boot out of recovery with no system and always be able to get right back into recovery. Not that I don't believe you, just saying it's weird. Which leads me to the guy above... he didn't really screw himself that bad, no danger of bricking at all, just needed a reflash.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just FYI on Kies
Am not sure on windows pc, but on my imac adb does not work with Kies. Had to use the Kies uninstaller to get if off imac then use adb. Maybe this isn't an issue on all phones?
Just got s4, and coming from HTC One S. So, if this is old news, sorry--
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
polish_pat said:
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
Click to expand...
Click to collapse
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
okzygen said:
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i do it thru recovery, thats always how it worked for me. You cant do it thru adb since you need root to do that and odin wipes root
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK I installed the AOKP one and it works like a charm. Only thing is NFC doesn't work so once that works it will be pretty Much perfect
Sent from my SGH-I337 using Tapatalk 2
jasbur17 said:
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
Click to expand...
Click to collapse
Yeah me too, was and still am not happy about it. Should gave stuck to CWM. TWRP is a cool recovery, as long as you realize what you hit.
Glad Kies worked! Now that I have an Att phone I can utilize it again. Wouldn't recognize my International SGS3, so Kies was useless.
Sent from GT-I9505 transformed SGH-I337