[Q] Flashing Problem? - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I looked around but could not find my problem - I sincerely apologize if it has been asked elsewhere.
Yesterday I attempted to install the newest root66 (4.3) on my telus GS3 using odin. Everything seemed to go ok, but the phone was sitting at the samsung logo for a long while (and vibrating every 5 or 10 seconds as well). The phone went through the normal boot process after the flash, including updating the apps, but then rebooted and just sat there. Thinking something was wrong I attempted to flash the root again and had the same problem. After that I used odin to flash the stock image and waited all night and day for it and it was still on the samsung logo. Tonight I went into the stock recovery and cleared the cache and attempted to flash the root66 again. The phone seemed to go through the normal upgrade boot again (after odin said pass) with the android upgrade spinning chest thing and all that.
I can still access download mode and the stock recovery, so I don't think I am in too bad of shape - part of me thinks it is just a matter of patience, which is fine if it is, but if not, I'd like to keep working on it. Any ideas?
In summery - in case that was confusing
1) flashed root66 4.3, odin indicated success, boot after upgrade was similar to what I have seen before
2) Waited for a couple hours
3) tried root66 again, and waited
4) flashed stock, odin indicated success and waited many hours
5) cleared cache, flashed root66, currently waiting again
6) maintain access to stock recovery and download mode
I'd like to not lose everything on the phone if possible, but if I have to so be it.
Any thoughts?

odin to stock 4.3 then root your phone using CF Autoroot by Chainfire... check always the model of ur phone and the file you are downloading if it is for your phone..

Flashing stock with odin just leaves me stuck at the same Samsung screen. Pulsing Samsung and whatnot

jaybeeee said:
Flashing stock with odin just leaves me stuck at the same Samsung screen. Pulsing Samsung and whatnot
Click to expand...
Click to collapse
Reboot into stock recovery and factory reset.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Related

Phone bricked..Help

I think I bricked my Rogers S3.
I had JB running on it. Today I decided to root it again ( I rooted it couple of months ago and then went back to stock). I did the same procedure as last time i.e. using toolkit, however, when I had to choose which file to choose in odin to be flashed in insecure boot, I chose "boot-insecure-spr-l710palen.tar" instead of choosing "boot-insecure-canada-rogers-i747mvale8.tar".
Now after odin finished doing ALLINONE "insecured boot, CWM, root phone + install busybox", my phone restarted and I could hear the samsung logo voice but the screen was totally blank.
I went back to odin and chose ALLINONE "insecured boot, CWM, root phone + install busybox" and this time chose the right file but still the same thing.
So now I decided to unroot the phone by flashing the custom rogers version back on, so I flashed the custom rom using ODIN but still my phone keeps on getting stuck at the samsung logo at the start up. It doesn't go any further.
Is it bricked? How can I solve this problem? Thanks
Note: If i press volume up+home+power, I can get into the mode where it gives me the options to reboot, wipe etc.
Should I try to root it again and try to get into recovery mode to see what can be done to fix it?
Bumped!!!!!!!!!
It's a soft brick, so you're okay.
Just download Odin and flash a restore image on your phone with it.
Search the "development" subforum for "Odin" and you'll find everything you need.
CZ Eddie said:
It's a soft brick, so you're okay.
Just download Odin and flash a restore image on your phone with it.
Search the "development" subforum for "Odin" and you'll find everything you need.
Click to expand...
Click to collapse
No no...do a factory reset
sent from outside ur window
twanskys204 said:
No no...do a factory reset
sent from outside ur window
Click to expand...
Click to collapse
Yup. It worked. I just performed a factory reset along with cache wipe and phone started working again. Thanks guys.

Bricked? or Soft Brick...

Hi guys,
Was trying to install a ROM last night in CWM Recovery, then I was having some difficulty, after each ROM swipe I was doing the Factory Wipe/Dalvik Cache Wipe/Cache Wipe.
Anyways, I ended up having to try and flash the pre-rooted Stock ROM, I used Odin 3.07 to flash it and in Odin it appeared to work fine, the phone was rebooting and Odin was in "Pass" mode, but the phone never gets beyond the Samsung boot screen.
I then tried to see if I could flash CWM Recovery in Odin and try and get into Recovery mode, it flashed fine in Odin and the device rebooted but still stuck in Samsung boot screen.... but I cannot get into Recovery mode manually, I even tried getting in via the Q3 Toolbox kit, and it says it cannot locate the device :/
So today, last desperate option, I tried flashing the un-rooted stock image for my carrier (Rogers), it seemed to work fine in Odin but it STILL just will not boot back up, still stuck in the Samsung boot screen.
Is this what a brick is? Beyond continually trying to re-flash the stock carrier MD5 via Odin, what can I do? Oddly enough the phone does recognize in the Q3 Toolbox for the Root options, just not for the Reboot into Recovery option. Is there something I can try in the Q3 Toolbox?
/Scared / really concerned
Please help, any help is appreciated.
Once again, I CANNOT get into CWM Recovery.
Sianspheric said:
Hi guys,
Was trying to install a ROM last night in CWM Recovery, then I was having some difficulty, after each ROM swipe I was doing the Factory Wipe/Dalvik Cache Wipe/Cache Wipe.
Anyways, I ended up having to try and flash the pre-rooted Stock ROM, I used Odin 3.07 to flash it and in Odin it appeared to work fine, the phone was rebooting and Odin was in "Pass" mode, but the phone never gets beyond the Samsung boot screen.
I then tried to see if I could flash CWM Recovery in Odin and try and get into Recovery mode, it flashed fine in Odin and the device rebooted but still stuck in Samsung boot screen.... but I cannot get into Recovery mode manually, I even tried getting in via the Q3 Toolbox kit, and it says it cannot locate the device :/
So today, last desperate option, I tried flashing the un-rooted stock image for my carrier (Rogers), it seemed to work fine in Odin but it STILL just will not boot back up, still stuck in the Samsung boot screen.
Is this what a brick is? Beyond continually trying to re-flash the stock carrier MD5 via Odin, what can I do? Oddly enough the phone does recognize in the Q3 Toolbox for the Root options, just not for the Reboot into Recovery option. Is there something I can try in the Q3 Toolbox?
/Scared / really concerned
Please help, any help is appreciated.
Once again, I CANNOT get into CWM Recovery.
Click to expand...
Click to collapse
You're soft bricked, don't panic just yet. A hard brick is when the device is completely unresponsive. So far this sounds fixable.
To get into recovery, are you holding down the volume up + home key for long enough after the Samsung logo appears?
I'd try that again, but if not: Try to Odin CWM again but uncheck "Auto-Reboot" in Odin. After it's done flashing, pull the battery out, put it back in, and use the key combos to get into recovery. Hopefully you have a nandroid backup saved or another rom saved on your sd that you can restore at this point. (Please note that using this method may increase your flash counter, but that can easily be fixed with Triangle Away).
Hope this helps.
If its just hanging at the samsung logo..pull the battery, put it back in, boot into stock recovery ( vol up+home+power) wipe data/factory reset then reboot.
After that just download one f the one click rooted stock rogers roms. Odin it, Then use the S3 toolkit to flash a recovery only.
Should be goo to go from there
I am flashing the pre-rooted stock ROM's via Odin again, and then will try and flash CMW Recovery again but without the Auto-Reboot selected.
I was pretty certain I was holding the keys long enough previously to try and get back into Recovery but it never would actually go into CWM Recovery.
Will let you guys know how it goes, thanks for replying.
skrambled said:
You're soft bricked, don't panic just yet. A hard brick is when the device is completely unresponsive. So far this sounds fixable.
To get into recovery, are you holding down the volume up + home key for long enough after the Samsung logo appears?
I'd try that again, but if not: Try to Odin CWM again but uncheck "Auto-Reboot" in Odin. After it's done flashing, pull the battery out, put it back in, and use the key combos to get into recovery. Hopefully you have a nandroid backup saved or another rom saved on your sd that you can restore at this point. (Please note that using this method may increase your flash counter, but that can easily be fixed with Triangle Away).
Hope this helps.
Click to expand...
Click to collapse
Just tried this.
Flashed the pre-rooted stock ROM, it went to Pass in in Odin, device never booted past the boot screen. Pulled out battery, re-inserted and then flashed CWM Recovery in Odin with Auto-Reboot turned off, that went fine to Pass, pulled battery and did the key combo to enter Recovery. I got the "Booting Recovery" in top left corner in blue for a second, held onto the key combo and nothing, just went back into the same Samsung boot screen and it's stuck there.
Sianspheric said:
Just tried this.
Flashed the pre-rooted stock ROM, it went to Pass in in Odin, device never booted past the boot screen. Pulled out battery, re-inserted and then flashed CWM Recovery in Odin with Auto-Reboot turned off, that went fine to Pass, pulled battery and did the key combo to enter Recovery. I got the "Booting Recovery" in top left corner in blue for a second, held onto the key combo and nothing, just went back into the same Samsung boot screen and it's stuck there.
Click to expand...
Click to collapse
Hmmmm...one more thing to try. Re-download the stock firmware image in the unlikely event that you got a bad/corrupted download (also may want to try the version that doesn't have root injected). Then try again.
I'd say to try a different USB port on your pc, but since Odin is saying Pass that doesn't seem likely. Worth a shot though if the above fails (and also worth trying to Odin from a different computer).
Hang in there, you aren't hard-bricked yet! :fingers-crossed:
It has to rebuild cache everytime you flash, if you are clearing things correctly. This can take up to 10 minutes. Also, when the first samsung logo appears take finger off power button and hold the home and appropriate volume button.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
The Q3 Toolbox kit saved me.
I couldn't flash into Recovery (not CWM Recovery, stock Recovery) no matter how long I held the key combo
But I eventually managed to get into Stock Recovery using the Q3 Toolbox.
Thanks for the advice people.
Holy shiiit that was nerve wracking for a while.

[Q] Sprint Note 2 hosed after flashing stuff

Note 2 Hangs at "SAMSUNG NOTE II" part of boot process.
- 1 year ago installed clockwork and rooted.
- a few days ago accepted OTA to 4.3 Android, lost root.
- Accidentally ODINed this ROM onto phone tonight root66_SPR_L900VPALJ1.tar.md5
- Hung on reboot at purple SAMSUNG boot screen
- Rebooted to clockwork tried "reset something (something like that)"
- It then booted and came up fine with Android 4.1.1. Everything seemed fine but of course I didn't want to be stuck at 4.1.1 and was pondering my next step when suddenly...
- Note 2 asked to apply OTA update (I think the 4.3 OTA was being tried again) I accepted thinking it might fix everything.
- After that it came up and hung at SAMSUNG NOTE II
- Tried rebooting to Clockwork, doesn't work at all now.
- I can ODIN various things including Clockwork, ODIN passes but nothing actually seems to work.
Stuck now.
I am wife of OP
wallywallywally said:
Note 2 Hangs at "SAMSUNG NOTE II" part of boot process.
Stuck now.
Click to expand...
Click to collapse
I am wife of OP, and usually get the fun of flashing the phones but I was working on my own at the time the above occurred. The only thing I can think of to fix the borked phone would be to get a decent stock rom image that can be flashed with ODIN. We can still put it in upload mode, but not into the bootloader menu. Anyone have a working link to an image that may work?
Try this.
Download stock mc2 with counter reset from development section and place on your external sdcard
1. Put phone in download/odin mode
2. Flash custom recovery but make sure the reboot option is not checked
3. After successful flash disconnect from pc and pull battery.
4. Reinstall battery while pressing vol+, menu, power. Should go into your recovery
5. Wipe everything (system, cache, data, internal storage)
6. Flash mc2 stock with counter reset
7. Reboot and you will be back on stock mc2 with stock recovery and firmware
8. Power off and boot into download/odin and flash your recovery
Now you can boot into recovery and flash whatever you want. If you want stock 4.3 dont use ota try one of the ones here on xda. If you want note 3 features use synergy r3 if you want plain stock use lorjays.
Sent from my SPH-L900 using XDA Premium 4 mobile app
MK4 (4.3) http://www.mediafire.com/download/7viivd985s7cp8l/L900VPUBMK4_L900SPTBMK4_HOME.tar.zip
Sent from my SPH-L900 using xda app-developers app

screen glitches after 4.3 update

Hi all I'm am new to this but i need much help here. After updating my Note 2 t889 to new firmware 4.3 OTA, my screen starts up and i can see the Galaxy Not 2 logo but then it glitches and goes to black. I can no longer see anything after but can still hear my phone boot up, light up eveything else. I have downloaded the official 4.3 from samobile and use odin to reinstall, everything went fine but still the screen does the samething. The only screen that im able to see fine is the download screen, recovery screen is black. Please Help!
i dont know if this information matter but i did replace the digitizer with a N7100. The screen worked for 2 months with 4.1.2 until this update. Is it possible that the update made the N7100 digitizer not compatible any more? any help would be really appreciatied.
My Note 2 t889 flickers when I attempt to update android as well. Its rooted and I think it has something to do with the cwm recovery used to root. But not 100%.
I have tried to update it numerous times, to no avail.
I think I need to un root, and start from scratch, then root again when updated to get rid of the flicker.
It flickers and rolls when trying to reboot after updating.
Have to enter recovery, wipe cache abd restart to get it to just boot.
Any ideas?
Be well.
Sent from my SGH-T889 using xda app-developers app
Are either you using a non stock kernel?
Hastily spouted for your befuddlement
well i might've screwed up now, try downgrading from 4.3 to 4.1.2 using this method i found;
So I did this a couple times now first by accident, then on purpose. If you want to go back to 4.1.2 from 4.3 all you have to do is use Odin. Flash stock 4.1.2 onto 4.3 you get an error "unsupported firmware" then put your phone back into download mode (volume down+home button+power) next flash CF-auto root. After that you can boot into recovery (volume up+home+power) in recovery format everything factory reset, format cache. Last reboot your phone it should reboot into 4.1.2 I think that is how I did it if I remember all the steps right. Feel free to ask questions I don't always explain myself very well.
i was thinking that this might work because my phone was fine on 4.1.2 so why not try. now on the download screen it says void:1, to make matters worst, it still doing the same thing. bad motherboard?
NbisYaj001 said:
well i might've screwed up now, try downgrading from 4.3 to 4.1.2 using this method i found;
So I did this a couple times now first by accident, then on purpose. If you want to go back to 4.1.2 from 4.3 all you have to do is use Odin. Flash stock 4.1.2 onto 4.3 you get an error "unsupported firmware" then put your phone back into download mode (volume down+home button+power) next flash CF-auto root. After that you can boot into recovery (volume up+home+power) in recovery format everything factory reset, format cache. Last reboot your phone it should reboot into 4.1.2 I think that is how I did it if I remember all the steps right. Feel free to ask questions I don't always explain myself very well.
i was thinking that this might work because my phone was fine on 4.1.2 so why not try. now on the download screen it says void:1, to make matters worst, it still doing the same thing. bad motherboard?
Click to expand...
Click to collapse
Hi, I got the same problem. My screen flickers at the galaxy note 2 logo after I flash the cf-autoroot after waiting the phone reboot itself and its okay, no flickering. So I tried to reflash the stock rom to see if it's fix, but it's not, I just wait again to boot my phone. Any idea how to fix it?

[q] phone wont boot help

HEY GUYS,
So I am upgrading to the note 4 next week. Sending my sister my note 2 and decided to leave the wonderful Community Rom and restore it back to stock for her to receive updates and not worry about root issues. I rebooted into my philz recovery. Flashed my old MC2_STOCK_with_COUNT_RESET-20130511 zip I had on my SD card which had always worked in the past, and succeeded. Then it rebooted to the Samsung Galaxy Note 2 splash screen and sat there for over 15 minutes never booting up.
Went to PC, opened Odin 1.85, and flashed several L900 Kies firmware and they failed. Finally, found one that flashed successfully, KIES_HOME_L900VPALJ1_L900SPTALJ1_265523_REV04_user_low_ship.tar. After successful flash, it auto reboots from download mode and has been stuck on the splash screen again for over 15 minutes. What do I do now? I have never had it hang up like this for this long, and had issues like these reverting to stock when I have wanted to in the past. Only thing that is different, is I have been on the 4.4.2 rom and these are probably 4.1.2 or 4.3 versions I am flashing.
Please help, I only have a limited time to fix this before I have to ship it off. Thanks guys
Dedline said:
HEY GUYS,
So I am upgrading to the note 4 next week. Sending my sister my note 2 and decided to leave the wonderful Community Rom and restore it back to stock for her to receive updates and not worry about root issues. I rebooted into my philz recovery. Flashed my old MC2_STOCK_with_COUNT_RESET-20130511 zip I had on my SD card which had always worked in the past, and succeeded. Then it rebooted to the Samsung Galaxy Note 2 splash screen and sat there for over 15 minutes never booting up.
Went to PC, opened Odin 1.85, and flashed several L900 Kies firmware and they failed. Finally, found one that flashed successfully, KIES_HOME_L900VPALJ1_L900SPTALJ1_265523_REV04_user_low_ship.tar. After successful flash, it auto reboots from download mode and has been stuck on the splash screen again for over 15 minutes. What do I do now? I have never had it hang up like this for this long, and had issues like these reverting to stock when I have wanted to in the past. Only thing that is different, is I have been on the 4.4.2 rom and these are probably 4.1.2 or 4.3 versions I am flashing.
Please help, I only have a limited time to fix this before I have to ship it off. Thanks guys
Click to expand...
Click to collapse
Have you tried to boot into recovery and wipe data and cache?
mr_wrong_0 said:
Have you tried to boot into recovery and wipe data and cache?
Click to expand...
Click to collapse
It does not boot into recovery. Only a splash screen of Samsung. Recovery does not seem to exist at this point.
I'd say start there.
Flash a custom recovery with Odin and then flash a stock rooted rom like Rwilco's mostly stock
Working after this flash
Thanks for your help, I went to this link - http://forum.xda-developers.com/showthread.php?t=2780984
Downloaded [LINK][ROM][ODIN][TAR]SPH-L900 NE2 (NE2 Modem/Kernel/ROM - Stock) and flashed it in Odin 1.85 and it booted and is updated and everything. Finally! Thanks

Categories

Resources