Hi there!
I just got my brand new Samsung Galaxy S III, international version.
I should have known that you shouldn't mess with your phone when you haven't slept the night before (I have a baby )
The facts:
It was a branded Spanish Vodafone phone. I rooted it using the Toolkit and used Voodoo to unlock it.
Then I flashed, using Odin, this firmware to unbrand it (I9300XXBLFB_I9300OXABLFB_BTU).
I used Titanium backup to restore All application and Data (I think this was a mistake). Then, when I saw Rom Manager, thought: "How nice, let's see if it works". It asked what phone I had, and one of the three options was the S III. I chose that and it tried to download and installa a custom recovery. But failed and Android told me that it didn't respond.
Meanwhile, Titanium was doing its thing and I started to see several "android.core" errors.
I tried to restart the phone, but it get's stuck in the Samsung logo. Just after making the boot sound. It slowly blinks blue and white.
I can get in Download mode, but I've tried to flash everything I have been able to think of, with no result.
Could anybody help me?
Thanks in advance
reycat said:
Hi there!
I just got my brand new Samsung Galaxy S III, international version.
I should have known that you shouldn't mess with your phone when you haven't slept the night before (I have a baby )
The facts:
It was a branded Spanish Vodafone phone. I rooted it using the Toolkit and used Voodoo to unlock it.
Then I flashed, using Odin, this firmware to unbrand it (I9300XXBLFB_I9300OXABLFB_BTU).
I used Titanium backup to restore All application and Data (I think this was a mistake). Then, when I saw Rom Manager, thought: "How nice, let's see if it works". It asked what phone I had, and one of the three options was the S III. I chose that and it tried to download and installa a custom recovery. But failed and Android told me that it didn't respond.
Meanwhile, Titanium was doing its thing and I started to see several "android.core" errors.
I tried to restart the phone, but it get's stuck in the Samsung logo. Just after making the boot sound. It slowly blinks blue and white.
I can get in Download mode, but I've tried to flash everything I have been able to think of, with no result.
Could anybody help me?
Thanks in advance
Click to expand...
Click to collapse
try flashing some custom rom coz now u have a rooted phone
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
Thanks.
I followed this tutorial and everything is OK
http://rootgalaxys3iii.com/galaxy-s3-stuck-at-boot
I think it's more or less what you said, JJEgan, but detailed step by step.
Related
Hello!
My Samsung Galaxy S3 (GT-I9300) was rebooting itself for the past few days, randomly. Last night, it did it again, but didn't boot back up. Instead, it is now stuck on an infinite boot loop - it gets as far as the splash screen (Galaxy SIII logo), then reboots, on a loop.
I've never tried to flash or root the device, I only used the official OTA updates from Samsung.
The first thing I tried was to remove the battery, SIM card and MicroSD card for 5 minutes. I then wiped the Cache Partition through the Android Recovery Mode. I then flashed using the Samsung Kies recovery procedure. This didn't help. I then tried a Factory Reset through the Android Recovery Mode, multiple times. This also didn't help. The last thing I tried was to flash the ROM using Odin3. I used the firmware version appropriate for my region and carrier. Everything was successful, but I'm still having the same problem.
I tried to view the boot logs with adb, but of course, the phone won't stay on for long enough to establish a USB connection. I'm not sure what else to try.
Any help would be greatly appreciated. Many thanks for looking!
I just managed to un-brick the phone by using Odin to install a stock Gingerbread firmware. Initially, I had tried it with Jelly Bean. I'm now hoping I had Auto Backup enabled in my Samsung Account...but at least I have my phone back. If anyone has any troubleshooting tips for me, now that I'm less limited, that'd be great.
Thanks!
http://www.hotfile.com/dl/190272724/372f3fa/I9300XXEMA1_I9300ITVEMA1_ITV.zip.html doownload this 4.1.2 firmware and flash it using odin (i'm assuming you know how to)
If you don't know how to, you can use my guide - http://forum.xda-developers.com/showthread.php?p=39045064#post39045064
Reboot looping,
facing the looping issue. Pls help.
Same problem
Having the same problem, but have much more limited data limits and have no idea how to root/flash..
jul_m said:
The first thing I tried was to remove the battery, SIM card and MicroSD card for 5 minutes. I then wiped the Cache Partition through the Android Recovery Mode. I then flashed using the Samsung Kies recovery procedure. This didn't help. I then tried a Factory Reset through the Android Recovery Mode, multiple times. This also didn't help.
Click to expand...
Click to collapse
Have done exactly the same with no success. My cellphone isn't rooted, its the international version and it already had the last update 4.1.2. So I don't know what might be the problem and how I can fix it. Any ideas? thanks
techmasta said:
http://www.hotfile.com/dl/190272724/372f3fa/i9300xxema1_i9300itvema1_itv.zip.html doownload this 4.1.2 firmware and flash it using odin (i'm assuming you know how to)
if you don't know how to, you can use my guide - http://forum.xda-developers.com/showthread.php?p=39045064#post39045064
Click to expand...
Click to collapse
how am i supposed to enable usb debugging if my phone is in a boot loop... :/
A little but terrible idea
Ok so here is the thing
Try flashing it with its own stock firmware
It might be the solution
Im trying it right noiw but first u gotta download a large file like 1 gigabyte or lower but it
is sure to be worth it. Donty know maybe it might work but just try.
Here is a website full of stock firmware . Make sure to choose the correct one for ur phone
h t t p :// www .mrcrab .net /android -firmware. html
Thats the link for lots of stock firmware for some devices.
And also here is the link for Odin
odindownload .com
Hope it helps
A thanks would be appreciated:laugh::laugh::laugh::laugh:
I just added spaces for you just erasee them i hope i helped
Good Luck!!!
Just reply if u need some help
Im online 3 times a week but ill check it weekly:good::good::good::good::good::good::good::good::good::good::good::good:
Hi,
i recently installed CM on my samsung s3 using the installer. All went all. Until after about 2 weeks, the phone was not charging correctly. So i went into the settings and performed a factory reset. No i had not installed or used clockworks to back up my phone. This left my phone in an unusaul state, where there was no home screen, i could not access my apps, although i could access the quick settings tab. Moving on....i followed a guide to try and restore my phones orginal rom using odin. According to odin all was successful, however my phone was stuck in a boot loop and so would not continue into phone. i read up and saw if i installed clockwork i could wipe cache and this might help the phone. so i installed clockwork using odin again. however when i try and access clockwork through the recovery mode, it only loads into odin mode? so i am unable to load clockwork as well i think. I am very new and this and i know i have probably made many mistakes but we learn through our mistakes. So my question is: Could someone please help me get my phone back to its orginal state!? Thankyou very much for anyone that can offer their time and help,
Nick
This May Help You
nick140795 said:
Hi,
i recently installed CM on my samsung s3 using the installer. All went all. Until after about 2 weeks, the phone was not charging correctly. So i went into the settings and performed a factory reset. No i had not installed or used clockworks to back up my phone. This left my phone in an unusaul state, where there was no home screen, i could not access my apps, although i could access the quick settings tab. Moving on....i followed a guide to try and restore my phones orginal rom using odin. According to odin all was successful, however my phone was stuck in a boot loop and so would not continue into phone. i read up and saw if i installed clockwork i could wipe cache and this might help the phone. so i installed clockwork using odin again. however when i try and access clockwork through the recovery mode, it only loads into odin mode? so i am unable to load clockwork as well i think. I am very new and this and i know i have probably made many mistakes but we learn through our mistakes. So my question is: Could someone please help me get my phone back to its orginal state!? Thankyou very much for anyone that can offer their time and help,
Nick
Click to expand...
Click to collapse
This link may help you. fix-s3-to-factory-unroot-stock-recovery-t2323847. Do it at your on risk.
Hi,
I got a new phone last month, a HTC One (M8). Since I didn't need my S2 anymore, I decided to experiment a little bit with it, witch mean, I decided to try and root it. Man, i should never have done that.
First, I followed a guide on wikihow on how to root it. I downloaded Odin and the jeboo kernel they recommended in the guide. A couple minutes later, when everything was done, I tried to reboot my phone without much success. It was stuck on "Samsung Galaxy SII" with the yellow exclamation mark. Did I say that I got my phone from Virgin Mobile in Canada? Anyway, I tried to find a way to make my phone functional again and a couple of hours later, I found a stock Kernel that I immediately flash on my phone using Odin.
Everything worked fine again but I didn't want that outdated Android 2.2 so I installed Kies and plugged my phone in my computer to install the latest update from Samsung. Once again, I couldn't boot my phone, it would loop the Samsung animation over and over. So I re-install Gingerbread using Odin. Everything worked fine again!
But as I am stubborn, I didn't want it! So I search the web again for a solution. I red that cyanogen mod was great and I immediately wanted to try it. So I install everything and since it had an auto installer, I thought it would be very easy and in no time I would be able to play with it. Never have I been so wrong. For a reason that I don't know, the installer wasn't able to speak with my phone even thought I tried everything they said to do in this case.
Now, I can't boot my phone but I can boot in download and recovery mode. The only problem is, my computer doesn't install the drivers when I connect my phone, so I can't re-install 2.2 using Odin.
Anyone have any idea what I should do to solve this issue?
Please, help me 'cause I ****ed up
(Sorry for the mistakes, english is not my native language)
You did not screw anything.
If you can go to recovery, just boot into it, download any ROM you want and flash it through recovery(wipe data/cache/dalvik before you flash) and you'll be fine.
Second thing, once you root your phone, you void your warranty, and you CAN NOT update your phone from official samsung updates.You can do that if you unroot, but you won't need any updates.
Any way, as long as you can get into recovery, you're fine.
Also, what specific model; sticker on phone chassis under the battery ?
Nightshadow931 said:
You did not screw anything.
If you can go to recovery, just boot into it, download any ROM you want and flash it through recovery(wipe data/cache/dalvik before you flash) and you'll be fine.
Second thing, once you root your phone, you void your warranty, and you CAN NOT update your phone from official samsung updates.You can do that if you unroot, but you won't need any updates.
Any way, as long as you can get into recovery, you're fine.
Click to expand...
Click to collapse
Thanks mate, I will try this as soon as I can!
MistahBungle said:
Also, what specific model; sticker on phone chassis under the battery ?
Click to expand...
Click to collapse
It is a GT-I9100M.
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
firstrival said:
I'm trying to get the user files off a phone with corrupted cache. When booted normally, it gets stuck on the white T-Mobile splash screen. When booting into recovery, I get an error about the cache and the phone restarts without loading into recovery. Screenshots attached.
I can get into download mode fine.
Using Odin to flash a custom recovery gives me the PASS message, but when I restart the phone, the stock recovery is still there with the same error message. I've tried TWRP and CWM.
I am hesitant to try flashing a custom ROM because I don't want to lose the data. The phone is not important, but the data is.
Click to expand...
Click to collapse
Dont try flashing a custom ROM on to the phone. Try flash the stock ROM through the lastest odin with the lastest drivers and let me know how that works out for ya. Unless that wipes the phone ( havent used it in quite some time) then I have no idea man.
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
firstrival said:
I tried flashing the T399UVUAMJ4 ROM throught Odin. It went through the entire process and rebooted, but nothing changed. Does this mean the bootloader is locked?
Click to expand...
Click to collapse
I'm not sure maybe want to ask someone else I'm not as experienced as some people on here. Sorry man goodluck
I hope someone can help you out. I would say your cache partition somehow got renamed but I'm not sure if thats possible and if so how to fix it. Maybe someone with ADB knowledge can help?
Also what TWRP were you trying to install? I've had problems when I tried to flash older versions
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
kireflow90 said:
okay so here is a site with the original firmware for the phone. It has both the t399 and the t399n for odin. It has them labeled so its not too confusing lol. http://forum.gsmhosting.com/vbb/f200/samsung-t399n-metro-pcs-firmware-here-1899016/
find the one for the t399, flash it with odin. this will fully restore your phone. HOPEFULLY it will be able to save the data. I know you said you did this before but I'm not sure if it was just system or everything like here.
Click to expand...
Click to collapse
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
firstrival said:
So I tried the T399 files. Flashed with no errors, but when it reboots everything is still the same. I've even tried flashing from another computer. Mind boggling!
Click to expand...
Click to collapse
Thanks for the quick reply. Its a shame to hear that it didn't work
How did you come to this? as to me it seems the partions have be modified hence why giving those errors I seen similar errors to when users change cache sizes which tends to brick device or from using incorrect pit files.
You never be able to recover data from flashing Odin may be slim chance by custom Rom thru recovery if was a bkup of original system and not selecting data your old data may conflict causing either bootloop or basically stuck on splash screen.
If you was ever able to best way to pull data from device would be thru adb may have a chance.
This phone belongs to a friend of a friend. They said they brought it to T-Mo because it hung up during boot. The store worked on it for a few minutes, but couldn't get it to boot up either. When I tried to go into recovery, they said the store already went into that screen too. They have since bought a new phone, but would like to get the photos off it if possible. They never had an SD card so it's still on the device.
At the moment, I can just go into download mode. I was hoping to flash a custom recovery so I might possibly be able to ADB from there since it won't load the stock recovery.
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
fulgorevinnie said:
I have a very similar issue but without "cache error messages". The phone (Samsung Galaxy Light with stock ROM and TWRP) just reboots no matter what I try to flash into it.
It does it while "drawing" the Samsung Logo animation (blue ring that gets created revealing the word samsung), so after the white wrintings of the phone name.
My attempts so far:
1. Flashed newer version of TWRP
2. Flashed CWM
3. Flashed two different versions of stock ROM (the original one and the one that T-Mobile released when upgraded to latest jelly Bean)
4. Flashed a custom ROM (Light ROM found here which is based on the stock one).
EVERY TIME the outcome was the same:
Phone reboots right after the phone name (written in white) while the Samsung animation starts. It just stops while the blue oval begins to appear. If I try to boot into recovery (via home/power/volume up combo) it shows the TWRP splash screen but it reboots right after and this happened even after I flashed (successfully according to Odin) CWM.
It really looks like I did nothing so far but I can assure it's not the first time I use Odin (4 different versions) to flash a custom recovery or a ROM. I did it successfully on other 4 different phones (all samsung).
On this same phone I did it the first time when flashed TWRP in order to root it via recovery.
I have no idea what to do next. I was thinking about using adb in order to wipe all the caches (dalvik included) but it looks like the phone can't be recognized unless I boot it into recovery mode (adb get-state returns "unknown") and I don't think I can do anything in Download mode which is the only mode I can enter apparently.
I was hoping someone here can help me to spare some money buying a new phone for my wife and tossing this one which is the best for its small size imho.
Thank you in advance to anyone interested in at least shading some light on what could have happened. This started to happen out of the blue and the last time I actively modified something (updating the recovery) was almost one year ago... It always worked like a charm until 4 days ago...
EDIT: To clarify: the reason why I posted here is because this looked like a problem the most similar to mine (boot loop or stuck at boot and can't enter either regular or recovery mode). I cannot create new posts due to my low "rank" yet... Please feel free to move this if you think it belongs to a separate thread.
Click to expand...
Click to collapse
ok so i read all that you have done which is basically everything i would of suggested to you other then could it be the battery may be faulty just random thought noticed you never mentioned trying kies you may have a chance with it beening detected as i see you can enter download mode so that help with odin also kies also have you tried firmware from here sam mobile here T399 or T399N OH2 lastest for tmo and OH3 for metro.
Try to only flash that thru odin i use 3.07 or 3.09 only difference is the pda button changes to AP .works perfect for me so i suggest it then returning back to stock recovery/firmware if it boots then awesome. then return to TWRP 2.8.4.0 beening lastest for this device also needed for CM12 also my projects for device current and future.
when using odin make sure that only “Auto Reboot” and “F. Reset Time” options are selected.
also just note when going into twrp release buttons as soon as you see logo otherwise it will continue to boot thru well happens to me when daydreaming lol.
also if your seeing this adb get-state returns "unknown" i believe installing kies may install the drivers for detection im not postive on that but im sure it something to do with missing the adb driver for device maybe another dev can confirm this ?
hopefully this may be of some help i keep on thread to see how the outcome goes
Thanks for the reply DJBoxer!
Regarding the battery it's a new one and I can confirm it's not a battery problem considering that the phone can stay in download mode and unplugged from any power source for very long times without turning off/rebooting and it never failed to keep the charge so far. I also tried with the old battery and the phone behaves exactly the same way.
I used 3 different versions of Odin (1.87, 3.07 and 3.09) with only “Auto Reboot” and “F. Reset Time” options selected and every time I got the PASS message even though the phone keeps rebooting after the first reboot once the procedure is terminated.
To clarify one thing : when I said "it shows the TWRP splash screen but it reboots right after and this happened even after I flashed CWM" I meant to point out that it looks odd to see the TWRP splash screen (even for just a few seconds) after I just flashed CWM and that makes me think that I'm really not flashing anything here...
Thank you very much for taking the time of posting the links and I actually didn't try with that latest OH2 version.
I am downloading it right now (it takes a while from sammobile) and I will keep you posted on the outcome.
I will try to flash it via Odin and I'll also try the latest version mentioned on sammobile (Odin3_v3.10.7).
Regarding Kies I wasn't able to have it recognize the phone. I may be missing something but I tried updating drivers and going through all the guided procedures with no luck... If you say it should recognize the phone right away while in download mode then something is amiss.
Could you please confirm that I should also be able to use adb commands with the phone connected via USB in download mode? Cause that doesn't look like the case either...
Thank you again and I'll give updates here about my last attempts.
Sorry for the late reply...
Nothing changed by the way...
I am about to send the phone back to the seller who told me they'll try to fix it. Let's see how it goes.
Hey,
My friend was running a flawless custom rom on his s3. Suddenly, it turns off by itself and the phone is then stuck on boot logo.
1. I tried to factory reset with no luck.
2. I tried to install stock 4.3 with no luck.
3. I tried to install 4.1.2. The phone booted but with no recovery. Then i noticed that imei changed to *0049 and i'm not registered on network (even though it was working well on the custom rom).
4. I tried to upgrade to 4.3, i got succeeded but recovery didnt install.
5. I tried to install the custom rom again but no luck.
6. I tried all patches of modems and kernels and ariza. All Failed.
7. I also tried EFS backup/restore and Failed.
My only concern is to know what made this issue appear all by itself ?? Because i guess we should take it to a mobile repair shop.
One last thing to say is that every time i try to install a software, available space gets low, and even if i delete some files from internal storage the storage wont free up.
Thank you !
get stock 4.3 fom and flash it via Odin (wipe everything before flash). Then flash recovery via odin. then backup efs. then flash custom roms.
downgrade from 4.3 to 4.1.x causes efs to become corrupted
Seems like a corrupt nand. Was it rooted previously when it died the first time?.
Going from 4.3 to 4.1.2 will cause the imei to be lost as the efs encryption changed at 4.3. You cannot go back.
If the phone has a custom rom on it try an official cwm recovery, if not or it doesn't work then proceed to the following:
If you can get the phone into download mode try flashing the stock firmware twice or thrice with a factory reset in between each flash. Do not allow the phone to boot into the os!!. If it attempts to boot to OS after the blue pass in odin then pull the battery out immediately and boot to recovery or download mode respective of what you are doing at the time, resetting or flashing.
If that fails you can then call it a dead phone.
Beamed in by telepathy.
Wow these are new solutions to me..
I really thank you guys and i'll look forward into trying them in any upcoming problems.
Thank you so much for sharing your knowledge
And just to mention, yes the phone was rooted when it went bricked suddenly.
I'd try to flash an official cwm and if it takes then flash back to stock twice with a reset, reroot and leave it as that. Custom roms aren't worth the paper they're written on.
In addition to downgrading from 4.3 to an earlier version, but forgot at the time of writing, you can downgrade but you need an efs backup from the time it was at 4.1.2, which has to be restored but I'm not sure of the process. I couldn't tell you if it has to be restored before flashing, after or both.
Not a lot of people have an efs backup from 4.1.2. I do, but then my phone hasn't acted wierd yet. Sods law.
Kies 2 (not kies 3) can restore the phone but only if it was in original condition. You can try the emergency recovery routine but don't hold your breath.
Beamed in by telepathy.
You're right.. Efs is the only part most of us miss !!
I wrote all of the steps you said in order.. So that if any problem occur ill deal with it based on your info.
Btw do you suggest using KK TW 4.4.4 by back-to-n00t ? Or this wont be considered as a kind of official firmware ?