I've searched relentlessly for a solution to this, but I haven't come up with anything, so it's time to ask for help.
I just used mskip's Galaxy S3 QCOM Toolkit v2.3 (http://forum.xda-developers.com/showthread.php?t=1746682) to flash CWM and root my GSIII. The recovery flashed successfully, using "recovery-cwm-lte-sgs3-v5.tar" included with the toolkit.
CWM recovery works. However, when I tried to boot the phone, I got the first Samsung splash screen, then the screen turned black, a second later the boot tune played (with no splash screen showing), and then... nothing. The blue notification light blinks infinitely, and the phone is unresponsive except for holding the power button down for 10 seconds, which restarts it, and the same thing happens again.
I can boot into CWM recovery, as well as download mode. I tried wiping the cache and doing a factory reset, which changed nothing. However, when I tried to flash a stock ROM (again using the toolkit), I got an "unsupport dev_type" error. I presume that USB debugging has been defaulted to disabled now from this, but maybe I'm wrong. In any case, I'm not sure where to go from here. I don't want to claim that I've bricked it yet, when I have both recovery and download, but I don't know what to do now.
Help?
EDIT: I'm sorry, I forgot basic information : I'm using a SGH-T999 (T-Mobile GSIII).
I would defiantly boot in to cwr and do a clean install on a diferent rom. Not a back up u made with cwr but a .zip rom... n u sgould b ok.. I would try jb smooth
Sent from my SGH-T999 using xda app-developers app
See if you can flash CM10, if you don't have to have stock.
kipster3001 said:
I would defiantly boot in to cwr and do a clean install on a diferent rom. Not a back up u made with cwr but a .zip rom... n u sgould b ok.. I would try jb smooth
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Looks like the toolkit installed an older version of CWM. I flashed 6.0.1.2 via ODIN (http://forum.xda-developers.com/showthread.php?p=30806933) and then flashed CyanogenMod 10.0.0. Works great.
Thanks so much!
Jacooni said:
Looks like the toolkit installed an older version of CWM. I flashed 6.0.1.2 via ODIN (http://forum.xda-developers.com/showthread.php?p=30806933) and then flashed CyanogenMod 10.0.0. Works great.
Thanks so much!
Click to expand...
Click to collapse
Glad you had it resolved. Another method would have been ODIN back to stock.
Sent from my SGH-T999 using xda app-developers app
Related
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
marcusabu said:
I decided to install Cyanogen Mod on my Nexus. I already rooted it and downloaded rom manager + titanium back-up. I watched a tutorial on how to download and install roms using rom manager and everything seemed to go as planned and Cyanogen 9 was installed. The phone automatically rebooted and the boot animation the Cyanogen started. But after a half hour I realized it was stuck. So I tried to go into recovery mode to restore my backup (of the stock) but when I went there, the phone automatically turn off. It's not when I click, it's just after a certain period. It even turned off while restoring. To make things worse, when I turn it on now, it's stuck on the Google logo with the unlocked slot at the bottom. I hope you guys can help me because I'm starting to freak out.
Addidional info:
Additional info
I did not delete evreything when I flashed
GSM version
rom was downloaded from rom manager
I backed up my stock rom
I did google but everything leads to bootloader which is broken
Yes I'm a noob
Click to expand...
Click to collapse
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
jv2543 said:
Is your battery charged? Have you tried reflashing recovery? if not I'd try reflashing recovery, not sure what it might be hope this helps
Click to expand...
Click to collapse
Where can I find this option and what does it do exactly? I have the Nexus Toolkit too, should I do anything there?
1.Don't panic
2. Try to go on bootloader then reset factory or fastboot then from pc flash recovery
3. Try to get back recovery then factory reset and flash backup
Sent from my HTC One V using Tapatalk 2
OP, here. Learn before you do some damage with tools you don't understand.
I mean, it's the easiest thing to fix damnit if you cared to learn in the first place...
Beamed from Maguro
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Odin back to stock
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I wouldn't recommend Odin to beginners. OP is better off with the fastboot guide mentioned by bk201doesntexist.
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
When I was a noob, Odin was the thing that save my life... a while back of course
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
was it a nexus? maybe/probably not, but if it was, you should have used fastboot. it's officially supported by GOOGLE. if you want to flash a factory image, they tell you to use fastboot. why would we use anything else? a leak? that the community barely really knows anything about?
i'd rather use Heimdall!! (not sure i9250 is supported though.)
Sent from my i9250
Rooted Att Note 2. I changed my fonts using Rom Tools and now my phone just sits at the Samsung splash screen. I did factory reset in recovery, still no dice. The recovery install only let's my flash updates and no I don't have a Nandroid. Kinda ran outta of ideas.
when you say the recovery install only lets you flash updates do you mean your still using stock revocery or have you flashed custom recovery and just dont have a ROM?
If you have custom recovery Id try to flash this :http://forum.xda-developers.com/showthread.php?t=1984546 Its been tested and works on our system. Its not stock but should at least get ya up and running again until a true stock is posted and you can flash that.
search in forums for an Odin tar file to reload the stock ROM. GL & do a nandroid before doing anything next time.
RMXO said:
search in forums for an Odin tar file to reload the stock ROM. GL & do a nandroid before doing anything next time.
Click to expand...
Click to collapse
I always do, didnt think much of fonts
cjsspape said:
when you say the recovery install only lets you flash updates do you mean your still using stock revocery or have you flashed custom recovery and just dont have a ROM?
If you have custom recovery Id try to flash this :http://forum.xda-developers.com/showthread.php?t=1984546 Its been tested and works on our system. Its not stock but should at least get ya up and running again until a true stock is posted and you can flash that.
Click to expand...
Click to collapse
not custom, thats the problem. I flashed twrp thru odin but it didnt take, even though it went thru
Try to flash cwm then and see if that takes. You'll need the Odin version of this file at the bottom of the OP http://forum.xda-developers.com/showthread.php?p=33955697
Sent from my SAMSUNG-SGH-I317 using xda premium
Sloved
the cmw tar worked. flash the rom in the general section
Good stuff. Glad it worked out for ya!
Sent from my SAMSUNG-SGH-I317 using xda premium
esincho said:
Rooted Att Note 2. I changed my fonts using Rom Tools and now my phone just sits at the Samsung splash screen. I did factory reset in recovery, still no dice. The recovery install only let's my flash updates and no I don't have a Nandroid. Kinda ran outta of ideas.
Click to expand...
Click to collapse
I had the same problem with Sprint note 2 and i just went to download screen and then flashed the cwm tar file and then all was good. Whew!!! Thought I bricked it! I made the mistake of using a quick boot app to reboot in to recovery. DON'T DO IT!
chidochuck said:
I had the same problem with Sprint note 2 and i just went to download screen and then flashed the cwm tar file and then all was good. Whew!!! Thought I bricked it! I made the mistake of using a quick boot app to reboot in to recovery. DON'T DO IT!
Click to expand...
Click to collapse
Just bought a ATT GN2... coming from SkyRocket... on the SR, I used to always use "Quick Boot" app to reboot, or reboot into CWM Recovery. When you reference "quick boot app", are you referring to this? When my GN2 arrives, want to be sure I avoid using "Quick Boot" app if it doesn't play well on the GN2 and JB. Thx.
DoctorQMM said:
Just bought a ATT GN2... coming from SkyRocket... on the SR, I used to always use "Quick Boot" app to reboot, or reboot into CWM Recovery. When you reference "quick boot app", are you referring to this? When my GN2 arrives, want to be sure I avoid using "Quick Boot" app if it doesn't play well on the GN2 and JB. Thx.
Click to expand...
Click to collapse
Most of the custom ROMs here use the built in 4 way Rebooter so ya really shouldn't need a quick boot program
Sent from my SGH-I317 using xda premium
I've had rom tools boot loop the phone after a font change. Moral of the story-nandroid.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
That's the one I used. Wish I knew why it happened.
Sent from my SPH-L900 using xda app-developers app
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
mrneilix said:
So this is kind of a unique issue i'm having. I have the I-747 on AT&T and flashed AOKP rom (it was taking too long to get JB). It worked for about 3 days and then got stuck in the android boot screen (used the rom feature to get rid of the pink unicorns). after that, I booted into recovery and reset my phone, and it worked again for a few more days, then it wouldnt boot again (I dont believe I changed any settings between the boots). After this time, it wouldnt let me boot into recovery and would only boot to the android start screen and stop. I used odin to flash the stock rom, which only took me to the 2nd samsung boot screen and stopped (after the AT&T splash shows up). I looked online and saw someone say try CF-root using odin, tried that and it didnt help. Then tried using a custom kernel siyah s3, and now it will only show the initial samsung splash screen before turning off again. Any suggestions here? I figured I'd stop researching since i dont want to really mess up my phone worse than it already is
Click to expand...
Click to collapse
I have a similar issue, someone please help
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
As DeathSdoor said...flash stock.
Sent from my SAMSUNG-SGH-I747
d3athsd00r said:
Your main issue now is that you flashed siyah. We don't have one. If you can get to download mode, you will want to flash back to stock.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Thanks guys! So I used odin to flash the stock boot loader and stock rom, but it is still hanging up on the 2nd samsung screen like it initially did (the one after the AT&T boot animation). Any other ideas on what could be the cause?
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
How long is the hang? Sure is just not the 1st initial boot of the new rom?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
The first boot can take as long as 5 minutes sometimes. So, if you haven't waited that long, then try out some patience. Otherwise, try booting into recovery (stock now) and factory reset.
Sent from my SGH-I747 using xda premium
bump!
I have this same issue. I have restored to stock rom and it does the Samsung boot, then AT&T, then it goes to Samsung pulsating with a blue pulsating LED.
I have left it in that mode for at least 15 minutes and it never boots.
I can still get into download mode.
Thanks in advance for any help!
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
I let it run for 2 hours (left the house came back and i was still on. And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
I dont know if this is relevant, but while the phone is off and plugged in, i can still see the battery meter and the Green LED (so i'm guessing it's still working, it just wont boot)
mrneilix said:
And phone wont boot into recovery at all ( i tried many times, but it just boots normally and skips recovery until it gets to the 2nd samsung screen, then stops there).
Click to expand...
Click to collapse
Same here!!!
jethro650 said:
Has anyone tried booting into recovery after flashing the stock ROM and wiping caches then rebooting?
Click to expand...
Click to collapse
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
As Jethro said clean everything and factory format in recovery. Your just not doing the buttons right to get in to recovery
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I went into recovery many times before, I'm definitely hitting the buttons right but it still wont go into recovery, it just tries booting like normal. I can go into download mode easily, but that's it.
jbizz, did you start getting this error after flashing AOKP rom also? trying to figure out what could have caused the issue in the first place
I'm not really skilled on these things, but I once had a similar issue with my phone not booting and had to end up using Kies to emergency restore it. Odin wouldn't recognize my phone but kies would.
Although I think my issue with odin may be stemming from my computers usb ports...
Sent from my SGH-I747 using XDA Premium HD app
I actually flashed a bad kernel and the phone wouldn't boot after that.
What is the proper way to boot into Stock Recovery?
Sent from my SAMSUNG-SGH-I777 using xda premium
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
mrneilix said:
Fixed it! What I did was go into Kies software and did a firmware upgrade instead of trying to flash from odin, then put it in download mode instead of recovery, but it still worked. Thanks for all the help, guys! guess it's time to move to a CM based rom?
Click to expand...
Click to collapse
Thats bad badassness! I will try that when I get home!
Sent from my SAMSUNG-SGH-I777 using xda premium
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
jbizz said:
mrneilix:
Please give me step by step what you did! Kies is being a bastard!
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Sure, I'm doing this largely from memory since I mostly figured it out by throwing stuff at the wall to see what sticks.
Open Kies->tools->firmware upgrade and initialization->enter model name then serial number (they're behind the battery) -> put the phone in download mode and plug it in. it should take care of the rest.
Fair warning, this will fully wipe your phone, i lost all my pics (thank you google+'s instant upload or i'd be PISSED) and titanium backup (there goes my 3 stars on every level in angry birds and great scores in temple run), but at least you get a phone that can function as more than a paper weight, right?
mrneilix:
You're my new best friend and I don't even know you!!!
Thanks for the help, you're a legend!
Sent from my SAMSUNG-SGH-I747 using xda premium
So, I have a brand new international Galaxy Note II. I thought I'd root the device, and so I powered up Odin, and downloaded the necessary files, and rooted the device.
The phone reboots into the OS just fine, and the phone has been rooted, but now when I try to access the recovery, the screen flips out for a bit, and everything goes black. I've tried different recoveries since then (TWRP, CWM Touch) but nothing seems to work, and all I get is a black screen.
Now as you can imagine, this is a bit difficult if I am interested in loading custom ROMs into the device, so... anyone have any clue what's going on? CWM loads fine, I know that though. Pressing the home button reboots the device (first option in CWM after all)
Re: N7100 Recovery Black Screen
hamsteyr said:
So, I have a brand new international Galaxy Note II. I thought I'd root the device, and so I powered up Odin, and downloaded the necessary files, and rooted the device.
The phone reboots into the OS just fine, and the phone has been rooted, but now when I try to access the recovery, the screen flips out for a bit, and everything goes black. I've tried different recoveries since then (TWRP, CWM Touch) but nothing seems to work, and all I get is a black screen.
Now as you can imagine, this is a bit difficult if I am interested in loading custom ROMs into the device, so... anyone have any clue what's going on? CWM loads fine, I know that though. Pressing the home button reboots the device (first option in CWM after all)
Click to expand...
Click to collapse
If cwm works fine then whats the problem ?
Sent from my GT-N7100 using xda app-developers app
The whole screen is black and I can't see what I am doing. It's like its there, but not showing up.
Re: N7100 Recovery Black Screen
Hmm if you have tried different recoveries then it is a different issue because there is no reason for it to not work.
Did you rename recovery restore files ?
Sent from my GT-N7100 using xda app-developers app
Well, I don't. I flash them as they are via Odin, and in the case of TWRP, I use their GooManager to install it.
No idea? I have owned and flashed countless devices, this is a first for me.
Re: N7100 Recovery Black Screen
Rename the /system/recovery-from-boot.p to recovery-from-boot.p-bak via a root explorer.
Sent from my GT-N7100 using xda app-developers app
File in question doesnt seem to exist on my device, using es file explorer with root permissions.
Re: N7100 Recovery Black Screen
Try flashing recovery again with mobile odin.
Sent from my GT-N7100 using xda app-developers app
Just tried, no luck at all. Same thing. The screen bugs out like an old television, then goes black.
Btw, if it helps, see attachment.
I'd just like to chip in and say... SOLVED!
I have no idea why, but when I tried PhilZ Touch Recovery, that worked PERFECTLY. (Tried TWRP, normal CWM, Touch CWM).
Now I can see the recovery menu, and all is GUT. Thanks for the help :3
hamsteyr said:
I'd just like to chip in and say... SOLVED!
I have no idea why, but when I tried PhilZ Touch Recovery, that worked PERFECTLY. (Tried TWRP, normal CWM, Touch CWM).
Now I can see the recovery menu, and all is GUT. Thanks for the help :3
Click to expand...
Click to collapse
Have the exact same story as you and i also succeeded to install PhilZ Touch Recovery, but every time i install a rom a get "The screen bugs out like an old television, then goes black"
huh. That's odd. my first rom I tried was [email protected], and it works just fine.
I'll mention that I reflashed via odin the stock ROM/Recovery/Kernel before all of this :\
Same problem, see thread here;
http://forum.xda-developers.com/showthread.php?t=2163421
I can flash stock and TW based roms no worries, but PA roms do the bug out thing every time. Checked MD5s, wiped everything, no fix.
UPDATE: Neak kernel on PA roms fixed the screen issue, but now Wi-Fi won't connect
hamsteyr said:
huh. That's odd. my first rom I tried was [email protected], and it works just fine.
I'll mention that I reflashed via odin the stock ROM/Recovery/Kernel before all of this :\
Click to expand...
Click to collapse
Thanks for info, I will try to install the stock ROM/Recovery/Kernel. Just a bit afraid because everything seems to fail on this device.
I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k
Wolfgar2k said:
I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k
Click to expand...
Click to collapse
did you check auto reboot in odin? if you do, just try to flash cwm again w/o checking auto reboot. it happens to my tab coz i've check auto reboot.
Just tried that. Same results. Everything looks good when flashing, but when I boot into recovery it's the stock recovery.
Sent from my Galaxy Nexus using xda app-developers app
Wolfgar2k said:
I'm trying to flash CWM on my non-rooted, fully updated T210R. I'm following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2433853.
Odin says it flashed successfully, and the tab reboots fine, but when I power off and boot into recovery, I'm getting the stock recovery. I've tried both the touch and non-touch versions, without success.
It's probably something small that I'm missing, but I can't for the life of me find it.
Any help would be appreciated.
Thank you,
Wolfgar2k
Click to expand...
Click to collapse
1.Dont check the autoreboot. Ketut.kumajaya said something about the system is restoring recovery when rebooting
2. Try to redownload the cwm recovery.
3. If that didnt work, What odin are u using? Try 3.07 ..
4. You can also try twrp. I am using twrp and it is working great
Sent from my SM-T210R using xda app-developers app
I've been using Odin 3.07 the whole time. I tried twrp as you suggested and that worked. Not sure why cwm didn't work, but at least now I'm rooted. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
I will recreate an autoroot package for you in my spare time. Samsung Android boot image has a known feature to patch the boot image and use it to overwrite the recovery image on every boot. This feature disabled in blackhawk kernel, some recovery has a capability to disable this feature as well.
ketut.kumajaya said:
I will recreate an autoroot package for you in my spare time. Samsung Android boot image has a known feature to patch the boot image and use it to overwrite the recovery image on every boot. This feature disabled in blackhawk kernel, some recovery has a capability to disable this feature as well.
Click to expand...
Click to collapse
Can I flash your kernel on the stock rom while having cwm recovery or do I need Infamous 1.1?
I would like to stay at german on my tablet but also want to use USB OTG
Wolfgar2k said:
I've been using Odin 3.07 the whole time. I tried twrp as you suggested and that worked. Not sure why cwm didn't work, but at least now I'm rooted. Thanks.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Got to hear that u have twrp. Im happy 4 u
Sent from my SM-T210R using xda app-developers app
Jediritter said:
Can I flash your kernel on the stock rom while having cwm recovery or do I need Infamous 1.1?
I would like to stay at german on my tablet but also want to use USB OTG
Click to expand...
Click to collapse
Yes, you can flash it on stock rom (with CWM), but OTG isn't functioning yet.