Methinks I hath killed it.... - Verizon Samsung Galaxy S III

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!

Related

i am new here and i am in big problem for my infuse 4g after install custom rom

i have rooted my infuse 4g using odin using this thread http://forum.xda-developers.com/showthread.php?t=1613523. but after installing this my phone was okay, then after i took backup thru cwm, after that i installed rom of jellybean and after installing it my phone cant start, so i took battery out and again go to recovery mod and try to restore it but i m facing same problem, my phone not starting, even usb mount also not working,
i have format my infuse again and try to do it with odin again but it shows that
E: failed to mount/dbdata(file exist)
E: copy_dbdate_media:cant mount /dbdate
your storage not prepared yet, please use UI menu for format and reboot action.
media files copy failed.
please help me. i m worried about it coz just yesterday i bought it new. so please please help me.
i dont know what is UI menu also.
If you had read the OP, you can't go directly to JB, you have to be on ICS, then flash JB.
Which option did you use from that page? I've used "I997UCLB3-root.rar" many times. But sometimes it gets stuck and I have to pull the usb cable and start over.
So, use I997UCLB3-root.rar, to go back to stock GB. Then flash an ICS rom, reboot. Then flash a JB rom.
Truckerglenn said:
If you had read the OP, you can't go directly to JB, you have to be on ICS, then flash JB.
Which option did you use from that page? I've used "I997UCLB3-root.rar" many times. But sometimes it gets stuck and I have to pull the usb cable and start over.
So, use I997UCLB3-root.rar, to go back to stock GB. Then flash an ICS rom, reboot. Then flash a JB rom.
Click to expand...
Click to collapse
Thank you for your reply but i have tried directly to go to jellybean from GB 2.3.6 and i also tried now to root again using I997UCLB3-root.rat but then also my phone giving same error that E: cant mount and samsung logo come only
huseniezzaz said:
Thank you for your reply but i have tried directly to go to jellybean from GB 2.3.6 and i also tried now to root again using I997UCLB3-root.rat but then also my phone giving same error that E: cant mount and samsung logo come only
Click to expand...
Click to collapse
Flashing JB is a big leap. Some reading, specially when you are new, could have saved you the trouble. But well, now is time to learn the hard way.
Download any uclb3 back to stock pack, either Odin or heimdall. Put your phone in download mode:
1) take out battery and place it back.
2) while holding vol + & - , connect your phone with a usb cable already inserted into the Pc.
Once in download mode, see if your phone is detected by odin or heimdall. If not you may need to install the drivers.
When all is ready, hit start.
*you probably don't have GB bootloaders. That will cause rainbows in your recovery when flashing ics and jb. If you feel you cant live with them, you will need to flash them.*
To flash jellybean, 1st flash any ics rom following directions coming from GB in the OP. Once you have blue recovery, flash JB with the directions in the rom OP.
Sent from my sweet & buttery Infuse
huseniezzaz said:
Thank you for your reply but i have tried directly to go to jellybean from GB 2.3.6 and i also tried now to root again using I997UCLB3-root.rat but then also my phone giving same error that E: cant mount and samsung logo come only
Click to expand...
Click to collapse
read this, should help
http://forum.xda-developers.com/showthread.php?t=1776129
This too
http://forum.xda-developers.com/showthread.php?t=1437548
Thank you thank you thank you
andros11 said:
Flashing JB is a big leap. Some reading, specially when you are new, could have saved you the trouble. But well, now is time to learn the hard way.
Download any uclb3 back to stock pack, either Odin or heimdall. Put your phone in download mode:
1) take out battery and place it back.
2) while holding vol + & - , connect your phone with a usb cable already inserted into the Pc.
Once in download mode, see if your phone is detected by odin or heimdall. If not you may need to install the drivers.
When all is ready, hit start.
*you probably don't have GB bootloaders. That will cause rainbows in your recovery when flashing ics and jb. If you feel you cant live with them, you will need to flash them.*
To flash jellybean, 1st flash any ics rom following directions coming from GB in the OP. Once you have blue recovery, flash JB with the directions in the rom OP.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I got my phone back. its working in 2.3.6 very nicely once again. thank you so much for response. i am very happy to see my phone start and i am smiling after 3 hours. huh. now i rooted it with odin I997UCLB3-CWM-root-deodex-extras.rar. now can you please tell me how can i install JB? i m curiously waiting to JB in my infuse. please make it JB.
huseniezzaz said:
I got my phone back. its working in 2.3.6 very nicely once again. thank you so much for response. i am very happy to see my phone start and i am smiling after 3 hours. huh. now i rooted it with odin I997UCLB3-CWM-root-deodex-extras.rar. now can you please tell me how can i install JB? i m curiously waiting to JB in my infuse. please make it JB.
Click to expand...
Click to collapse
The first link I posted for you will walk you through it. Read all the instructions, re-read, look up anything you don't understand, and then follow the directions.
huseniezzaz said:
I got my phone back. its working in 2.3.6 very nicely once again. thank you so much for response. i am very happy to see my phone start and i am smiling after 3 hours. huh. now i rooted it with odin I997UCLB3-CWM-root-deodex-extras.rar. now can you please tell me how can i install JB? i m curiously waiting to JB in my infuse. please make it JB.
Click to expand...
Click to collapse
As others mentioned, you first need to install an ICS ROM, like CM9 or Uniporn. The first time you flash you will prob get stuck in a boot loop and will need to use the three finger method to get back to recovery. In case you don't know what that means, you hold the volume keys and power button to turn phone on and then release only the power button when the Samsung logo shows. When u get back to recovery, flash the same ROM a second time and then it will boot.
You will now have blue recovery so you can flash the jb ROM of choice by following the method in the OP for that ROM. Remember to pull out the external sdcard if you have one.
Also, as others have mentioned, you may not have GB bootloaders. To get them, go to the "ISET infuse everything thread" which is stickied in the dev section. You will find Odin and Heimdall packages which have the bootloaders there. Be very careful when installing bootloaders (test usb with a kernel or something less dangerous first) bc if it fails while trying to flash the bootloaders, it can hard brick your phone. And then thank bigjoe for putting together the ISET thread so all infuse users can find everything we need in one place.
Sent from my SGH-I997 using xda app-developers app
Thank you thank you thank you
benbos_06 said:
As others mentioned, you first need to install an ICS ROM, like CM9 or Uniporn. The first time you flash you will prob get stuck in a boot loop and will need to use the three finger method to get back to recovery. In case you don't know what that means, you hold the volume keys and power button to turn phone on and then release only the power button when the Samsung logo shows. When u get back to recovery, flash the same ROM a second time and then it will boot.
You will now have blue recovery so you can flash the jb ROM of choice by following the method in the OP for that ROM. Remember to pull out the external sdcard if you have one.
Also, as others have mentioned, you may not have GB bootloaders. To get them, go to the "ISET infuse everything thread" which is stickied in the dev section. You will find Odin and Heimdall packages which have the bootloaders there. Be very careful when installing bootloaders (test usb with a kernel or something less dangerous first) bc if it fails while trying to flash the bootloaders, it can hard brick your phone. And then thank bigjoe for putting together the ISET thread so all infuse users can find everything we need in one place.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Thank you so much, i have flashed JB successfully and GAPPs also. thank you once again. i followed your method and its very easy. first CWM was red i flash JB and after that i pull battery and start CWM at that time it was Blue and i flashed, now its installed.
One more HAPPY INFUSE OWNER.
Is this forum group great, or what!!!!!!
benbos_06 said:
As others mentioned, you first need to install an ICS ROM, like CM9 or Uniporn. The first time you flash you will prob get stuck in a boot loop and will need to use the three finger method to get back to recovery. In case you don't know what that means, you ...
Click to expand...
Click to collapse
I think if you don't know what "that" means...it means you have not read anything you probably need to read on this forum. and probably should not even be thinking about JB let alone trying to flash it.
No slight on you benbos_06, I thought it was funny reading uninformed posts about "rainbow colors" in their their recovery a few months ago...now it's almost kind of sad to see the uninformed trying to go JB...and needing double flash and 3 finger to recovery detailed in step by step instructions. Jeeze!!! That's a little scary.
Sent from a de-FUNKt Infuse
Smokestack360 said:
I think if you don't know what "that" means...it means you have not read anything you probably need to read on this forum. and probably should not even be thinking about JB let alone trying to flash it.
No slight on you benbos_06, I thought it was funny reading uninformed posts about "rainbow colors" in their their recovery a few months ago...now it's almost kind of sad to see the uninformed trying to go JB...and needing double flash and 3 finger to recovery detailed in step by step instructions. Jeeze!!! That's a little scary.
Sent from a de-FUNKt Infuse
Click to expand...
Click to collapse
+ 100... right on, Smoke !!

[Q] Clockworkmod Recovery updated, can't enter recovery mode

Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
VyCariously said:
Hi, I've searched and can't find an answer. I've managed to root my Infuse and got Infinitum rom installed. It was working great until just this evening when Clockworkmod updated (sorry, I can't find the version number). It went into a boot loop. It took me a bit, but I managed to get it out of the boot loop and back to stock, now it's rooted again with Infinitum running again.
I'm trying to get back to a recovery point that I do have on the phone, but I can't get the phone to boot to recovery no matter what I do. When I try using the vol and power buttons combination or from ROM manager I get the same thing. It goes past the stock Samsung logo into the Galaxy S/Cyanogen(mod) logo, but freezes there.
I can, of course, take the loss of my setup and redo everything manually. I would really prefer to be able to get that backup back. I'm also concerned should I ever need to get into recovery mode for any other reason. My guess is that I need to downgrade the CWM version, but I haven't been able to find how to do it.
Can anyone give me any help? Please let me know if there's info that I can give that would be useful...I'm noobie, I know!
Click to expand...
Click to collapse
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
qkster said:
There are many layers to your questions.
You may need to read a bit more to get a better understanding.
Here is two points I can offer that may be helpful.
1. Don't use ROM Manager for the Infuse.
2. To downgrade a cwm version, you will need to flash a GB or FROYO kernel in download mode via heimdall or odin. You can also use any one of the return to stock that is flashed in download mode also.
If you think you lost recovery, try flashing the kernel for the rom you were running in cwm, if you can get back into cwm again.
Click to expand...
Click to collapse
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
VyCariously said:
I believe you about the ROM Manager. Too late, unfortunately. I'll take it off.
I had the phone back to stock with Odin. I went through all of the steps that I went through to first root it and install Infinitum. I had red cwm at the time. I just can't seem to get into it now. I don't think I lost it, I'm just unsure of how to get to it, since it freezes at the cm startup. I can just power off from there after I give up waiting, and it will boot to ICS normally when I power it on normally. I have Titanium Backup Pro, and it can access the nandroid backup that I have to get the apps and data. I was just hoping to recover the whole setup. I had an issue last weekend (oops to me) when I tried to install a JB rom where it went into a boot loop. I recovered everything after backtracking like I did tonight, and was hoping to be able to do the same. Is there any hope, do you think, if I go back and return to stock and start over from the beginning again? If not, I'll just suffer and redo the whole thing.
By the way, I really appreciate you answering. I've been lurking for a few weeks, and realize that you know a LOT about these phones.
Click to expand...
Click to collapse
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
That does remove root access. However, root isn't really necessary, at least for the stock ROM, if you have no intentions of staying stock. The ROM .zips you'll subsequently flash are pre-rooted. After you Heimdall back to stock, and flash it again with "flash bootloaders" selected, then use Heimdall to flash this kernel:
http://d-h.st/6KA
That'll flash both a new kernel and CWM Red recovery. It'll take a few minutes to boot up the first time, as it's installing the lagfix. Once it boots up, just shut it down and boot back up in recovery. From there, you can do whatever you need to do.
VyCariously said:
Okay, so next question. I've been reading and searching and reading some more. I can get the phone back to stock and work up again, but I still reach a point where it will freeze on the Samsung/CM startup screen. In reading the Infinitum Project thread, I found this (yes, it's pretty easy to find):
"Recovery/CWM messed up?
Here is how to fix it...
1) Download uclb3 heimdal by qkster
2) open the program
3) put phone in download mode
4) click flash (leave program open when finished DO NOT CLOSE)
5) after it finishes and your phone reboots, put the phone back in download mode and reconnect to PC
6) click flash bootloader on the heimdal program you left running
7) flash, let reboot and your recovery problems should be gone"
I used that to get back to stock before...doesn't that remove the root? Do I have to go through all that, then the bootloaders, and then go back and root all over again to get back to a working CWM? I'm sorry to ask so many questions, but it seems that I've done most of this already, though I admit to not doing the flash for the bootloader. I'm just unclear since it says "your recovery problems should be gone" at the end of that, like I have to do nothing more.
Click to expand...
Click to collapse
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
qkster said:
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Thanks guys
It's been a crazy busy week and I just didn't have time to deal with the phone. I've been dealing with stock gingerbread. It's getting kind of annoying, though, it seems less stable than the custom ICS that I had on it before. Not sure when I'm going to have time to play with it again and try to get it to where I want it. I think I'm going to try to totally wipe all of the old stuff out of the memory before I do it again, though. There's something that wasn't allowing me to do what you guys are telling me to do successfully. I'm also thinking of finding a GS2 and just selling the Infuse, not because of my confusion, but because the GS2 was what I was originally looking for anyway.
I'll try to get this one set up first, though, as it's just a matter of me being obsessive about it.
qkster, I'll look into the JB, too, lol.
qkster said:
As Apex pointed out, each time we bring the phone back to stock, we lose root access and all the previous setup. It's a fact of flashing.
No big deal though, rooting is easy and is not really needed. What is needed is the insecure kernel with cwm. The link Apex gave you is the same as the posted kernel in post #2 of the thread. That kernel will give you the cwm. Review that thread if you haven't yet.
Flash the heimdall uclb3 repartition package. Immediately after it successfully boot your phone, don't close the program. check the bootloader box and put the phone back into dl mode and flash it again to get your gb bootloaders...
then flash the kernel.
review my how to thread if you need to.
Andros11 also made a how to for JB if you want to live vicariously.
gl
Click to expand...
Click to collapse
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
XperiaNeoVNoob said:
Hey I am not the Infuse user... But I faced similar problem in my xperia some days back after updating the recovery.
I was also not able to enter recovery at boot time using my usual volume down way...
What the change was the new recovery checks for tap on the screen (repeatetive) instead of volume down button...
Not sure if it will work or not for you... But you can give a try...
Hit thanks if it works
Sent from my MT11i using xda app-developers app
Click to expand...
Click to collapse
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
VyCariously said:
I didn't get a chance to try it, sorry! I ended up wiping my phone totally back to stock Gingerbread with nothing on the sd card, either, and starting all over again. It seems to be working really well this time (fingers crossed). RemICS-UX is pretty much awesome
Click to expand...
Click to collapse
No probs...
:thumbup:
Sent from my MT11i using xda app-developers app

[Q] Phone will not turn on

My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
dontsayeta said:
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
Click to expand...
Click to collapse
The battery was at ~60% when I was flashing.
ALSO: I can't get into ODIN mode as the device doesn't respond to any type of button combination.
Deleted.
dontsayeta said:
Ok. I don't know what steps you have taken so far, but do a battery pull and then try to get into Odin mode.
Click to expand...
Click to collapse
I don't know if you read the OP or not but I did in fact already do what you stated. It does not work. I have: Battery pull+attach to USB, Battery pull+battery back in. Neither work to get back into ODIN mode.
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
dontsayeta said:
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
Click to expand...
Click to collapse
I understand, I have the same restriction. However, I think that the device is simply bricked and cannot be recovered. If no solution is posted then I will be heading to the VZW store tomorrow I suppose.
x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
Your phone is hard bricked. I'm gonna guess you were flashing a non Verizon ROM, probably an international.
The only fix at this point is a JTAG service. Also, unfortunately you would not have been able to restore before leaving recovery anyways. I'll try to find the popular website people use for that service.
Sent from my SGS3 running Eclipse 2.1 build 4
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Zalithian said:
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Click to expand...
Click to collapse
Thanks I couldn't remember the site.
Sent from my SGS3 running Eclipse 2.1 build 4
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Probably just google about flashing roms, find a youtube video and follow instructions. Wonder if a lot of videos don't have a warning, or if people ignore it.
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
I'm just an idiot, and jumped the gun on this flash.
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Well, back in the days before quadcore... the roms that were made for the international HTC Desire HD also worked on the us version the HTC Inspire 4G. . . I fell right into the pitfall after getting used to that.

[Q] Houston, boy do I have a problem!

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

[Q] unbrick blaze

Hello,
I'm truly hoping someone can help me. I spent all night installing new roms on my phone. Ok let me back up. This is bout the tenth phone I've rooted. I rooted my blaze about 2 months ago using a one step(I think can't remember.) I never really installed a custom Rom until last night. The first Rom I installed was cm10, which I liked. Only problem was I couldn't mount my sd card because I am no where near a computer. So I decided to install the baked Rom. I was ecstatic to find that everything worked. However, the cm10 Rom seemed to be running at the same time. I found that very weird. So I tried to figure out a way to get the cm10 off my phone. For hours I tried wiping and reformatting different things from recovery. My problem is the last time I rebooted my blaze out wouldn't go past the Samsung screen. I've tried all combos of the volume up down and power key and it never goes past Samsung. I'm assuming I've bricked my. It will show the battery charging screen. 1st it'll show the stock screen then the baked screen for charging. Please help me. I've searched xda for help and can't find anything to help.
Ps. I'm not at a computer now but please list help for when I'm able to get to one. And yes I've only gotten about 3hrs of sleep in the last 20hrs from messing with my phone.
Sorry for posting in development first meant to post here.
Odin to stock uvlh5. From sammobile.com/firmware
Edited... because I speak without thinking
^ what he means is download the stock ICS ulvh5 firmware from sammobile.com/firmware for the blaze/sgh-t769 and flash it on Odin.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Thats why I have the sammobile firmware and odin on a backed up. I've tried to learn from my mistakes well that's what I have learned a lot here hahahaha
Oh i remember reading you are not around a PC a lot... you need a PC for ODIN sounds like you can't get into recovery so PC only other way I know of. If I helped push thanks
how do you flash it exactly
myssdion said:
how do you flash it exactly
Click to expand...
Click to collapse
Dude just Google your quote plus a few more words and follow instructions.
Or this http://forum.xda-developers.com/showthread.php?t=1591601 . If your soft bricked you need to go back to gingerbread. Than upgrade accordingly ICS than jelly whatever. Hope works out for you
jbats said:
Dude just Google your quote plus a few more words and follow instructions.
Or this http://forum.xda-developers.com/showthread.php?t=1591601 . If your soft bricked you need to go back to gingerbread. Than upgrade accordingly ICS than jelly whatever. Hope works out for you
Click to expand...
Click to collapse
Yeah, I thought about that right after I asked. Thanks for the help. Got my phone back to working with a custom rom I'm too happy
myssdion said:
Yeah, I thought about that right after I asked. Thanks for the help. Got my phone back to working with a custom rom I'm too happy
Click to expand...
Click to collapse
Glad to hear that

Categories

Resources