Develop Bugs

Please Help! SII Stuck On Firmware Upgrade encountered an issue screen

Basically My galaxy S2 was rooted and do not remember the root name etc... everything was working great until I installed a new font, the phone rebooted and was on start up screen for more than 3 hours.
After looking for solution and fielding with it, I ended up in worst place now!!
Cannot enter recovery mode anymore (volume up + Home + power)
The screen is Stuck on "firmware upgrade encountered an issue"
Cannot connect with Kies
However I can enter the Download mode and connect with ODIN
Tried to install many firmwares but ODIN fails!!

barzi3 said:
Basically My galaxy S2 was rooted and do not remember the root name etc... everything was working great until I installed a new font, the phone rebooted and was on start up screen for more than 3 hours.
Tried to install many firmwares but ODIN fails!!
Click to expand...
Click to collapse
Post in Galaxy S2 threads I'm sure there is the answer..
also provide more details i.e. Odin log/output

I did the same exact thing. Went to s2 forum and it shows u how to reset your phone to factory. Then all you need is to re root and voila. Back on game mode!!!::good:

[Q] Help! Note 2 bootloop, no recovery

Hey, so my note 2 (sgh-i317m variant) running 4.3 is stuck on the samsung screen and I cannot boot into recovery (it just stays at the samsung screen). What I believe caused this is the fact that I originally had it rooted, but flashed back to stock via odin to update to 4.3. Then I proceeded to re root it via odin and the cf auto root, however I forgot to factory reset before doing this. Now its stuck on the samsung screen and I cannot even get it into recovery mode. I can get it into download mode but whenever I try reflashing the stock rom (I have two different ones) neither of them work and Odin just displays "fail". I really dont know what else to do, hoping someone will know, thanks in advance.

Friend, try Google for KIES3. After installation under the Menu bar..look into something recoveries..
There you'll need to enter your model and serial no.
Boot your hp to DOWNLOAD MODE and plug to your usb. Then let KIES do its work.
Hope it helps

53N53L355 said:
Friend, try Google for KIES3. After installation under the Menu bar..look into something recoveries..
There you'll need to enter your model and serial no.
Boot your hp to DOWNLOAD MODE and plug to your usb. Then let KIES do its work.
Hope it helps
Click to expand...
Click to collapse
That didnt work

Mbrar15 said:
Hey, so my note 2 (sgh-i317m variant) running 4.3 is stuck on the samsung screen and I cannot boot into recovery (it just stays at the samsung screen). What I believe caused this is the fact that I originally had it rooted, but flashed back to stock via odin to update to 4.3. Then I proceeded to re root it via odin and the cf auto root, however I forgot to factory reset before doing this. Now its stuck on the samsung screen and I cannot even get it into recovery mode. I can get it into download mode but whenever I try reflashing the stock rom (I have two different ones) neither of them work and Odin just displays "fail". I really dont know what else to do, hoping someone will know, thanks in advance.
Click to expand...
Click to collapse
POST the complete ODIN log here.

...
Mbrar15 said:
Hey, so my note 2 (sgh-i317m variant) running 4.3 is stuck on the samsung screen and I cannot boot into recovery (it just stays at the samsung screen). What I believe caused this is the fact that I originally had it rooted, but flashed back to stock via odin to update to 4.3. Then I proceeded to re root it via odin and the cf auto root, however I forgot to factory reset before doing this. Now its stuck on the samsung screen and I cannot even get it into recovery mode. I can get it into download mode but whenever I try reflashing the stock rom (I have two different ones) neither of them work and Odin just displays "fail". I really dont know what else to do, hoping someone will know, thanks in advance.
Click to expand...
Click to collapse
Did you end up figuring it out?

Stuck at Boot - After years of use (HELP!)

Hey guys..
My phone is stuck at the "Samsung Galaxy S4" screen" where it shows just the letters.
The last thing I remember doing was using taskiller and phone's memory killer to kill memory because it was slow... and when I tried to open up text messages, it wouldn't open.
So I restarted the phone and now it's stuck at the "Samsung Galaxy S4" Screen.
( I also removed some apps days before.. but I had rebooted and phone it was working just fine).
- I haven't tried to reinstall a radio.. I woudn't know which one.
- I can access odin just fine by clicking the 3 keys.
- I Can't access TWRP Recovery. I held the 3 keys, and it shows the message on the left corner like it's going to go, but then just reboots and gets stuck on samsung screen.
Tried to reinstall it, but didn't seem to work I guess.. since it still shows the left corner message, but doesnt go to twrp.
Details about my phone:
SGS4 Rooted.
Rom, Custom Stock Rom.. Jedi S4X http://forum.xda-developers.com/showthread.php?t=2331942 (url of ROM)
What Can I do?
I dont care what I have to install/remove, but I have very important things on the phone that I CANT have deleted!
HELP ME ??

What model of phone u have?

tmobile m919

xologist said:
tmobile m919
Click to expand...
Click to collapse
1. You can flash other custom recovery through ODIN and wipe all (If you have important things in the phone better go to step 2 directly)
2. Flash the latest firmware through ODIN for ur phone: HERE

[Q] ATT SGH-I313 Note 2 bricked/soft brick issues

So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!

titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Download the latest kies from the samsung website.. and then open tools and then firmware update and initialization.. pull out the battery and type the model number and serial number kies asks.. follow the instructions.. your phone will be fine..
Sent from my GT-N7100

titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Try flashing a recovery for ur device with Odin, not a ROM, just flash twrp recovery with Odin, after u flash the recovery u will be able to access recovery and flash a stock ROM through twrp. I think what happened to u is when u flashed the update it tried to right over the unlocked bootloader which caused the soft brick, try flashing the recovery for ur device and if that doesn't work try the above posters way...
Sent from my Nexus 5 using XDA Premium 4 mobile app

[Q] Bricked but is it hard or soft bricked?

I turned on my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected. This occurred after using Odin for something I downloaded from http://forum.xda-developers.com/showthread.php?t=1739426.

asodiu said:
I was messing around with my rooted Virgin Mobile Galaxy S 3 when it got stuck on the Samsung logo. The logo is animated but the phone will not progress past it. The phone is unable to boot into recovery or download mode; when I try to do so, the phone behaves as if I tried to simply turn it on normally. Samsung Kies is unable to connect to my phone but it does notice when I connect the phone to my computer. Odin also knows when the phone is connected.
Click to expand...
Click to collapse
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.

Larry2999 said:
You are actually at the forum for the i747M/U variants of the SG3. To see if we can help you, however, you would need to provide more info ... You said you were doing stuff with your phone? Were you trying to flash a firmware or something? If so, what were you flashing and at what stage did your phone get stuck in the bootloop?
It's not a hard brick if your phone still makes some attempt at starting.
Click to expand...
Click to collapse
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.

After flashing, did you boot to recovery and wipe data and cache?

audit13 said:
After flashing, did you boot to recovery and wipe data and cache?
Click to expand...
Click to collapse
As I have said, I am unable to boot to recovery or boot to download mode. I did not wipe data and cache.

Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.

asodiu said:
Actually, after removing my battery for approximately forty minutes, I was able to boot into download mode. When I attempted to boot into recovery mode after turning on the phone normally (which resulted in the phone being unable to progress past the Samsung logo), I was once again only able to turn on the phone normally and get stuck on the logo.
Click to expand...
Click to collapse
I recommend getting your hands on the Android SDK and using adb to boot into download and recovery modes. I got a water damaged d2att from friend a few months ago and the old volume down key doesn't work and using the command prompt and adb, you can get it to boot to whichever mode you want.
Sent from my SPH-L710 using Tapatalk

asodiu said:
I was flashing a download found in the link I have given (the newest Bell one). My phone had progressed past the first sign of the Samsung logo, past the screen saying "Samsung GALAXY S III" and past the animation with the sound before getting stuck on the next Samsung logo.
Click to expand...
Click to collapse
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.

Larry2999 said:
Virgin Mobile is a 'virtual' mobile network operator but ports mainly on the Sprint CDMA network. Unless your phone specifically had Bell firmware or was porting on Bell, flashing the Bell version would be wrong and could, nay would, cause a brick. Thankfully, though it appears to be only a soft brick and may be recoverable by re-flashing compatible firmware. Unlike Sprint and Virgin which are CDMA networks, Bell is GSM so I'd very much doubt that the firmware you were trying to flash was compatible with your phone. The fact that your phone is still trying to boot suggests that the bootloader is still intact but the system itself has been compromised. Can you remember what Android version your phone was on the last time it functioned normally? If so, I would suggest you visit Sammobile.com or androidfilehost.com and find the same version (or higher) for your phone and then flash to return to stock or near stock. You can always re-root afterwards or flash a custom ROM when your phone is back to working normally.
Since you can get into download mode, you can flash custom recovery in case the stock file you find is a zip file to be flashed via recovery. You should be able to get into recovery mode if you try the button combo again after you have flashed custom recovery via Odin. Otherwise, if it's a *.tar file, just flash directly with Odin.
Click to expand...
Click to collapse
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.

asodiu said:
I have successfully managed to flash stock filmware on my phone and now it is working fine. The post which I got the file that I attempted to flash stated that the Bell version would work with the Virgin Mobile phones. My Galaxy S 3 was running Android 4.3.
Click to expand...
Click to collapse
Glad to know it's working fine now. Unless the firmware for the 2 phone models have identical build numbers, I'd be surprised the post suggested that cross-flashing may be OK.