Hi,
I have a S3 model GT-I9305 (2GB) for like 7 months. It had 4.3 version installed, and I wanted to downgrade to 4.1.2 or 4.2.2. In the about menu Baseband version was i9305xxuemk1. Phone does not have any recovery software installed, except the default Odin download mode (Home+Down+Power), and I am able to enter it.
Since I am not sure for which country / carrier the phone is made (here people sell everything from everywhere), I do not know the original version of ROM, and there is no official ROM for my country (sammobile / Serbia). I have tried several 4.1.2 ROMs for different zones, and almost all of them failed, except for one - I9305XXALI5_I9305EVRALI5_EVR, which is reported as successful installation in Odin, but after restart it hangs on samsung logo.
Anyone has any ideas?
So, it seems that I can install any 4.3 version, but cannot install any 4.1 version. Some fail on nand, most fail on sboot. Any ideas? Basically what I do is, put the phone into download mode, and load firmware in odin and flash it.
Don't install 4.1 roms.
After you flash in odin boot into recovery and do a factory reset and and wipe cache and delvik cache then reboot
I am not sure what you mean? My goal is to install 4.1.2 version.
I have followed instructions from this link, but it doesn't work. In final step, when I need to go into recovery mode (Up+Home+power), I cannot enter it, it just hangs on samsung logo.
However, this link helped, I was able to downgrade using Odin mobile
Goran_ said:
I am not sure what you mean? My goal is to install 4.1.2 version.
I have followed instructions from this link, but it doesn't work. In final step, when I need to go into recovery mode (Up+Home+power), I cannot enter it, it just hangs on samsung logo.
However, this link helped, I was able to downgrade using Odin mobile
Click to expand...
Click to collapse
Why do you want to downgrade all the way down to a 4.1 rom.
Are you sure you are powering off then entering the combo to start it?
Because I have a major battery drain, which last from 6-10 hours, depending on usage (mostly calls 1-2h, very rarely internet). Hard reset did not help.
As I have learned, it is a known KNOX problem, that I was not aware of (I also have another S3, which does not have KNOX on it).
Goran_ said:
Because I have a major battery drain, which last from 6-10 hours, depending on usage (mostly calls 1-2h, very rarely internet). Hard reset did not help.
As I have learned, it is a known KNOX problem, that I was not aware of (I also have another S3, which does not have KNOX on it).
Click to expand...
Click to collapse
I have just read your topic title again, im sorry but i have no knowledge of knox since the i9300 does not have it, please get a mod to move this to the i9305 section where they can help you
Could you uninstall KNOX rather than going back to 4.1.2? http://www.androidpit.com/how-to-uninstall-knox
Related
ANSWERED - Firmware Install - factory reset in recovery
I made a mess of a rom install rushing through rom Manager and now my phone can't get past the Samsung screen when booting, and I can't find out the version of my kernel to install the correct one without getting my phone on. I can get the phone into download mode and I have tried a number of different kernels but have had no luck. It's a UK phone so I know it's a XW or XX to start, I was wondering is their a kernel that works on any SGS2.
I have been having trouble with getting windows to recognize the phone and have found a number of fixes on this site which have worked and not worked (atm not connecting)
it's a sgs2 GT-i9100
Any advice greatly appreciated
Did you make a Nandroid backup? If so boot into recovery (vol up, power, home buttons) and restore the backup.
Can you get into recovery mode. Vol up plus home plus power. Then do a factory reset. this should get past the Samsung boot screen. Then flash another rom.
Sent from my ThinkPad Tablet using XDA App
Thanks for getting back, no unfortunately not, couldn't see recovery mode since the original failed rom install. That combination gets me to download mode now.
So as far as I can tell I need to get a firmware working properly or do a reset but I don't know which is the right firmware to use
Main thing is you can get to download mode. If you can do that, you can fix your phone 95% of the time.
You can find carrier/country specific firmware here or country-only/non-specific firmware here
owen5y said:
Thanks for getting back, no unfortunately not, couldn't see recovery mode since the original failed rom install. That combination gets me to download mode now.
So as far as I can tell I need to get a firmware working properly or do a reset but I don't know which is the right firmware to use
Click to expand...
Click to collapse
Just flash any CF-root kernel and then you have recovery back. Start flashing from there on.
Lennyz1988 said:
Just flash any CF-root kernel and then you have recovery back. Start flashing from there on.
Click to expand...
Click to collapse
I have tried a number of CF-root kernels and no joy. I tried a few more kernels this morning before work, including cf-root and siyahv2.6.4 and had no luck.
MistahBungle said:
Main thing is you can get to download mode. If you can do that, you can fix your phone 95% of the time.
You can find carrier/country specific firmware here or country-only/non-specific firmware here
Click to expand...
Click to collapse
I actually flashed some of those kernels XWKE1 for example and a few others with no joy.
The problem started when I tried to update the Galent Miui ICS which I see you are running. I (stupidly) didn't read through the statement as I had my NYE hungover and just put the update on my sd and used recovery to update which froze the phone at the boot screen. (I didn't do re-flash and I didn't wipe the data and everything else.) I know it sometimes takes time to boot but I had left it for a half hour to see if it would and no joy. I was no longer able to get to recovery mode so I tried a half dozen kernels with the same problems before putting up a post. I'm not sure would people find it inappropriate to talk about an this problem here, I thought as it's a kernel problem now it would be a better place to find the solution although my own lazy Miui install was the cause.
Flashing just the kernels obviously didn't fix the problem. Have you flashed any of the entire stock firmwares ? Choose the most recent firmware for your carrier/country from the first link I gave you (if there's more than two listed).
owen5y said:
I actually flashed some of those kernels XWKE1 for and a few others with no joy.
The problem started when I tried to update the Galent Miui ICS which I see you are running. I (studidly) didn't read through the statement as I was hungover and just pu the update on my sd and used recovery to update which froze the phone at the boot screen. I know it sometimes takes time to boot but I had left it for a half hour to see if it would and no joy. I was no longer able to get to recovery so I tried a half dozen kernels with the same problems before putting up a post.
Click to expand...
Click to collapse
MistahBungle said:
Flashing just the kernels obviously didn't fix the problem. Have you flashed any of the entire stock firmwares ? Choose the most recent firmware for your carrier/country from the first link I gave you (if there's more than two listed).
Click to expand...
Click to collapse
Yes I will try that. At work currently and so can't play with the phone. I will post the result this evening.
Thanks
NP. Let us know how you get on.
MistahBungle said:
NP. Let us know how you get on.
Click to expand...
Click to collapse
All good, I installed the firmware and was able to get into recovery mode from there. Did a factory reset because I was stuck in a boot loop. Going to give it a go again to upgrade to the new ics build. Any advice on the best process of getting there?
I installed the following firmware prior to the reset
UK
XWKE1:http://www.multiupload.com/15RY5CHHW9
Firmware info: PDA: XWKE1 Phone: NEKD5 CSC:H3GKD4
Yep. Given the problems you've been having, stay away from the currently alpha ICS builds that are floating around.
Frankly, that's a disaster waiting to happen.
Wait until CM (or someone else) releases something that's stable and has most things working in 4-6 weeks or so.
There's a ton of roms/kernels out there, do your research/reading & ask questions if necessary in the respective threads for those & then pick something out & try it.
And no, I don't do recommendations. Because nobody's phone come's out of the factory the same, nobody has the same phone setup & nobody uses the phone the same way.
owen5y said:
All good, I installed the firmware and was able to get into recovery mode from there. Did a factory reset because I was stuck in a boot loop. Going to give it a go again to upgrade to the new ics build. Any advice on the best process of getting there?
I installed the following firmware prior to the reset
UK
XWKE1:http://www.multiupload.com/15RY5CHHW9
Firmware info: PDA: XWKE1 Phone: NEKD5 CSC:H3GKD4
Click to expand...
Click to collapse
OK, I did like the Galnet Miui ICS rom I was running although there was a few bugs with it when it died it was difficult to charge again. That's fair if you don't want to give out recommendations it's shooting in the dark over the interenet I suppose. I will have a good look through the forum and se if I find something that I would think is suiting.
Thanks for your help, and the advice is appreciated
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
9. I have odin 3.07 - is this version appropriate for this procedure?
dimbo33 said:
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
Yes. If you have the sane/safe chip no need to worry.
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
Doesn't matter whether it is on or off. It's just for debugging. I usually keep it on since you don't know when it might be useful. There is no harm in keeping it ticked.
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
No need to remove sim card.
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
After flashing, your phone will restart. If it doesn't go past the samsung logo, you'll need to pull out the battery, reinsert it, boot into recovery and perform a factory reset. Wiping cache and dalvik isn't necessary. However, if you do boot into recovery (which most certainly you'll have to, to do the data wipe), it takes less than 15 seconds to wipe the cache and dalvik.
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
I believe it's designed to be that way. However, I am not sure about this one. Sorry.
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
No need for the .pit files. Better avoid them at all costs.
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
Don't worry. You'll know when to worry ... Taking upto 5 minutes is perhaps normal. After that, update here if you think there is a problem.
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
Yes, and yes.
9. I have odin 3.07 - is this version appropriate for this procedure?
Better use v1.83 or v1.85. I've read a complaint against the latest one. Old is gold in some cases
Click to expand...
Click to collapse
I've replied under every question. Didn't want to quote the whole thing then write my answers, or scroll up and down continuously. Good luck and don't worry
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
I've replied under every question. Didn't want to quote the whole thing then write my answers, or scroll up and down continuously. Good luck and don't worry
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your answers. I appreciate it. I've done this kind of thing loads of times on other types of device, but I'm always nervous as hell when it's the first time and don't want any holes in my understanding of the process.
dimbo33 said:
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
9. I have odin 3.07 - is this version appropriate for this procedure?
Click to expand...
Click to collapse
Firstly,
Idk exactly about USB debugging but what i do know is that...
"USB Debugging is intended for development purposes only. It can be used to copy data between your computer and your device, install applications on your device without notification, and read log data." A few apps use it, like the aforementioned PdaNet app. USB Debugging can also be used with ADB when issuing commands from a command line on your computer to your Android handset or tablet. One-Click root apps often require USB Debugging to be enabled to deliver the exploit that roots your device.
SIM card wouldn't affect anything, so it doesn't matter if you leave it in the phone..
After Flashing the JB, first check whether the phone goes into boot loop or anything like that....if you experience any problems then do the factory reset, wipe cache...though its usually recommended to factory reset anyways..
I don't think we need to flash the "emmc_EXT4_16GB.pit" or the other pit file..
The reboot process shouldn't take more than 5-10 minutes max..
Well i have gone from custom ROM 4.1.2 XXLSJ back to the stock 4.0.4 using the usual flashing steps of ODIN....I didn't experience any problems..
If its anything above Odin3v1.85 it shouldn't be a problem...
Press thanx if i helped..
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
I guess that when I flashed jb leak I had all those questions, and maybe a couple of more.
Then I read about Mobile Odin, flashed & rooted my device in half a smoke (3 mins). All I had to do was select the 3 tar files.
The flash did network lock my device. Galaxysim Unlock solved it for me.
good luck and happy flashing.
dimbo33 said:
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
Click to expand...
Click to collapse
Only once. Either before flashing the ROM, or after. Order doesn't matter.
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
Only once. Either before flashing the ROM, or after. Order doesn't matter.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
dimbo33 said:
I would imagine then it's better to do it prior to flashing so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
Click to expand...
Click to collapse
No, I don't think so. Come to think of it, I've never tried that A battery pull works though
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
No, I don't think so. Come to think of it, I've never tried that A battery pull works though
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean it's not better to factory reset before flashing or the long press doesn't turn off the phone from recovery (in which case best to pull the battery out)?
dimbo33 said:
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
Click to expand...
Click to collapse
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.
So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off
TheATHEiST said:
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.
So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off
Click to expand...
Click to collapse
Sane chip, he's already off.
gastonw said:
Sane chip, he's already off.
Click to expand...
Click to collapse
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
TheATHEiST said:
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
Click to expand...
Click to collapse
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
gastonw said:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
Click to expand...
Click to collapse
:laugh:
gastonw said:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
Click to expand...
Click to collapse
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.
Probably a bit melodramatic I know.
It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.
What do you think?
dimbo33 said:
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.
Probably a bit melodramatic I know.
It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.
What do you think?
Click to expand...
Click to collapse
Well...the beauty of flashing is that you can do both Stock & Custom. You can also Dual Boot if you want.
My advice is this:
1) Always Back up EFS folder (HC-ktool is a good app for that).
2) Get Titanium Back up Pro.
3) Flash CMW or Flash siyah, it can't never hurt (well, if you go JB leak, might wanna try usin stock kernel first and the flash a custom kernel)
4) Get mobile odin Pro (so you can flash as many stock ROMs as you like, with the chance of getting bricked or soft bricked close to none + you'll always be rooted)
5) Read about ROMs features. You are the only person in the world that knows what ROM will fit your needs.
6) Start flashing.
7) If you are scared about bricks, read the bricked device's threads. That way you will know what NOT to do.
In my experience, I went jb and never came back.
Now, you really dream about IMEI, lol, that's something
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.
I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.
I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.
Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
dimbo33 said:
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.
I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.
I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.
Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
Click to expand...
Click to collapse
Well, you read 10 problems while flashing, right now we got 50.000 users going thru these threads, here, at XDA.
Jb is buggy, it's a leak, but too buggy? don't think so.
As for the bugs, we got plenty of people coming up with work arounds & fixes every day. In my case, I only have the lockscreen issue (let's face it, it doesn't always happens, like maybe 1 time a day and it's only for 3 seconds till the capacitive buttons light up. If you lock the screen and re unlock it with the power button, you're off. For me, it's not even an issue). I don't even remember when was the last time I had this issue, maybe 3 days ago now that I think about it.
Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.
BTW: we are getting the lime pie update, SII Plus was released just now
gastonw said:
Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.
Click to expand...
Click to collapse
I have had a look at mobile Odin Pro and I like the look of it. Thanks for the tip. To use it I need to root the S2.
I have seen this guide http://forum.xda-developers.com/showthread.php?t=1501719 - this seems simple. I could also flash the Siyah kernel via Odin. Which root method would you recommend? The first method seems to avoid the triangle issue - although this is not a big deal.
With a routed device I can backup efs etc before flashing anything else. Does the efs folder contain the simlock status?
Also, as you know I have been looking at the leaked jb, but perhaps it might be worth looking at neatrom 4.1.2 (or similar) instead?
I seem to get the impression that mobile Odin Pro is a safe method. Is it safer than using PC Odin?
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:
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
catheapp said:
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
Click to expand...
Click to collapse
Are you sure that you have the right bootloader installed for the lollipop rom? Did you factory reset before installing custom rom? Try to wipe davlik after installation completes before restarting device. Also follow the instructions given by the rom thread op.
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 ?