Hello,
I have an i9300 s3 from Vodafone UK. I first rooted it by following instructions on team android .com (can't post the link due to being a new user).
That worked fine for a few months.
Later I wanted to test out Cyanogenmod so I installed that using the new installer.
I then needed to return the phone to complete stock (I have to return the phone to Vodafone so I need it to be absolutely stock).
I downloaded the most recent Vodafone UK firmware from Sam Mobile (I9300XXELLA):
[again can't post the link]
I then used Odin v1.85 to flash that onto the device.
All seemed to go ok but when the device rebooted it got stuck at the SAMSUNG logo screen. The logo animation completes and then starts again.
I am really new to this. The description above contains my complete experience of rooting and flashing ROMs. Any help would be massively appreciated. Please let me know if I've left out any crucial information. Is it possible to get the phone working again?
Like so many posts before you, factory reset. You may have further problems as you've flashed such an old rom, efs may not mount.
Please search and READ, before posting new threads. Sticky guides in general have all you needed to know.
Sent from my GT-I9300 using Tapatalk
fixed
Hello,
Thanks for the tip.
The factory reset has fixed it.
Sorry for not reading / searching. It's one of those things where you get so scared that you've bust the phone that you freeze up and don't think clearly. Needed another's guidance to unfreeze.
Thanks.
Related
Hey!
I just upgraded my unrooted Bell GT-I9100M to Ice Cream Sandwich 4.0.3 using Kies and I would now like to root my phone. I haven't found a definitive instruction on how to do this so I wonder if it has or hasn't been figured out yet.
Thanks!
Bump. My cousin has the Virgin Mobile version, which I believe is the exact same thing as the Bell version? He upgraded to ICS and is looking to root but after a half hour of Google and XDA searching there is no info related to our situation.
http://www.google.com/search?q=xda+i9100+root
WARNING
I followed ctomgee's search suggestion (as if I hadn't done a simple Google search myself already) and found a Youtube instructional video here: http://www.youtube.com/watch?v=Vw_za0mQorw
When I flashed XWKDD_insecure.tar as instructed my phone turned into a brick stuck at the splash screen with a yellow warning symbol.
Then I read the comments LOL
I recovered by downloading both the stock Bell kernel and firmware (UGKG2) from here: http://forum.xda-developers.com/showthread.php?t=1113928 and reinstalled the kernel first and then the firmware using Odin. This restored me to stock gingerbread and I was then able to update once again to ICS 4.0.3 using Kies.
In my original post I was looking for guidance from someone that had already successfully rooted their Bell, ICS upgraded SGS2. I know that this has been done many times with other S2's but obviously it isn't universally understood as to how to get this done.
At least I figured out how to recover. The next attempt won't be so scary!
Cheers!
myamigo said:
WARNING
I followed ctomgee's search suggestion (as if I hadn't done a simple Google search myself already) and found a Youtube instructional video here: http://www.youtube.com/watch?v=Vw_za0mQorw
When I flashed XWKDD_insecure.tar as instructed my phone turned into a brick stuck at the splash screen with a yellow warning symbol.
Then I read the comments LOL
I recovered by downloading both the stock Bell kernel and firmware (UGKG2) from here: http://forum.xda-developers.com/showthread.php?t=1113928 and reinstalled the kernel first and then the firmware using Odin. This restored me to stock gingerbread and I was then able to update once again to ICS 4.0.3 using Kies.
In my original post I was looking for guidance from someone that had already successfully rooted their Bell, ICS upgraded SGS2. I know that this has been done many times with other S2's but obviously it isn't universally understood as to how to get this done.
At least I figured out how to recover. The next attempt won't be so scary!
Cheers!
Click to expand...
Click to collapse
Reading posts in full is helpful too.
That video you reference is quite old, but aside from that, the dude even says "if you're not on xwkdd, watch through to the end blah blah"... and it links to this - which says right at the top:
THIS THREAD HAS BEEN SUPERCEDED BY THE CF-ROOT THREAD: http://forum.xda-developers.com/showthread.php?t=1103399
Click to expand...
Click to collapse
THAT link has full instructions and is much more up to date than the video you chose.
But in any case, I guess you need a bit more help... so if you're still on ICS, then try this, which doesn't involve flashing anything with Odin, so it's safer that way.
It was ALSO the fourth result in that search I linked you to.
Thanks for the hand holding
I get a different result from my search and the ROOT/UNROOT link didn't bubble to the top for me.
I had to revert to gingerbread so I could restore data that I backed up using Kies and just upgraded to ICS once again. I'm getting good at that!
The ROOT/UNROOT guide worked perfectly. I'm now rooted and I created a backup of my phone so I'm good to go!
Thanks again!
myamigo said:
Thanks for the hand holding
I get a different result from my search and the ROOT/UNROOT link didn't bubble to the top for me.
I had to revert to gingerbread so I could restore data that I backed up using Kies and just upgraded to ICS once again. I'm getting good at that!
The ROOT/UNROOT guide worked perfectly. I'm now rooted and I created a backup of my phone so I'm good to go!
Thanks again!
Click to expand...
Click to collapse
Hmm. Strange your results from XDA are different than mine.
But in any case, I find Google to be a better tool to search XDA, than the built-in XDA search engine. Just click on that link at the bottom of the subsection of links that says "More results from forum.xda-developers.com >>". That will show you all the results Google found JUST on the XDA forums.
ctomgee said:
But in any case, I guess you need a bit more help... so if you're still on ICS, then try this, which doesn't involve flashing anything with Odin, so it's safer that way.
It was ALSO the fourth result in that search I linked you to.
Click to expand...
Click to collapse
Confirms to work for the Virgin Canada version (GT-I9100M). Thanks! I wasn't aware i9100 root methods would work on the i9100m, now i know.
I think I'm in trouble!
I booted into CWM to restore from a backup I generated yesterday and the restore seemed to work fine. I was returned to the CMW menu and selected the reboot option but the phone has not shown any signs of life since.
I've tried to boot into download and recovery modes with no luck. I also tried a soft and hard reset (suggested here http://androidforums.com/3240969-post170.html) but still nothing.
Is there anything else that I can try? What might have happened?
myamigo said:
I think I'm in trouble!
I booted into CWM to restore from a backup I generated yesterday and the restore seemed to work fine. I was returned to the CMW menu and selected the reboot option but the phone has not shown any signs of life since.
I've tried to boot into download and recovery modes with no luck. I also tried a soft and hard reset (suggested here http://androidforums.com/3240969-post170.html) but still nothing.
Is there anything else that I can try? What might have happened?
Click to expand...
Click to collapse
Hmm. Maybe this? Did you happen to do a bunch of wipes, in addition to the restore and reboot?
ctomgee said:
Hmm. Maybe this? Did you happen to do a bunch of wipes, in addition to the restore and reboot?
Click to expand...
Click to collapse
No I went straight to the restore and into the toilette from there. I've tried building a USB jig and the micro USB cable I hacked up left pin #4 (ID) disconnected internally (not brought out to a pad) so I can't get a wire on it.
I found a way to get the 300k resistor directly across pins #4 & #5 of the phone but this didn't wake it up so she's firmly bricked.
It's still under warranty so I'll take it in to see if I can get it repaired that way. If the only way to repair it is through JTAG since downloading over the USB port isn't an option it may simply be more trouble than it is worth to Samsung to find out what really happened. All they'll hear from me is that I upgraded to ICS using Kies and that toasted it.
clozecall said:
Confirms to work for the Virgin Canada version (GT-I9100M). Thanks! I wasn't aware i9100 root methods would work on the i9100m, now i know.
Click to expand...
Click to collapse
hi, thanks for letting us know your experience.
i am planning to purchase a Galaxy SII GT-I9100M, from VirginMobile (CAN) - it is a little bit outdated, but the 4.3 screen, the form factor and coming with ICS are good points. by the way, youf galaxy from virgin mobile, did come with ics as well? (asking to be sure that the one is sale presently are the same serie as your mobile).
are there recents roms available for this model? like newest jellybean or cm10?
did you have problems to unlock the phone?
in general, are the roms for the model Galaxy SII I9100 compatible with this VirginMobile model GT-I9100M?
thanks.
Where to start? Well we can start by saying that I am a fool. I won from my uncle his Galaxy S2 (GT-i9100), but wanted to upgrade to version 4.2. It is a phone bought in Latin America branded by Claro. He had UHKI4 Kernel and system android 2.3.4 (if I remember correctly). So I rooted the device using the method of Odin3 v1.85 with CF-Root-Kernel-v4.1-SGS2_UH_MUL_KG7 CWM4. The root was ok!
I went into recovery mode and tried to follow the steps of this video /watch?v=ezuW5qFS8-w. I used the I9100VJMS4_I9100ZTAMS4_ZTA rom. But something went wrong and my phone is stuck in recovery mode CWC. Cant boot, I dont know how to flash anyhing...I need help, I wonder if it is possible to recover the phone yet and if possible put the kernel back and remove the root ... summarizing back to the original.
I appreciate if any help was as detailed as possible. And thank since now everyone who read the topic. Sorry for english errors
Well I am hopeless :crying:
Well I managed to restore a backup :fingers-crossed:, I'm actually pretty dumb . I downloaded a firmware instead of a ROM (you can laugh now) . :laugh:
But I still doubt. Let's think in two hypothetical situations below:
1 - I would like to upgrade from version 2.3.4 to 4.0 or 4.2. And put a custom ROM or Stock
2 - I would go back to the original kernel and unroot.
How to proceed in each case?
Glad you got it working again. Now that you have it working and not in such a panic, you should do some reading. Someone telling you how to do things like that will never work out, you'll always be relying on others to do whatever modifications you are currently attempting. By reading and learning about it, you'll be able to do it all for yourself. So how to proceed in each case? Research & learn about each one. Both are legitimate things to do, and there are plentiful threads/guides on each.
Sent from my GT-I9100: Powered by Dorimanx, running RootBox
1.use a pc
2.use cwm
Lol
Well, I could do what I wanted. Thanks for the reply Hopper8. After I calmed down I could organize ideas. And thanks for the detailed answer theunderling lol
No problem....any time
-------------------------------------------
maybe your an iphone expert
------------------------------------------
Hi all
Recently I upgraded from Samsungs stock 4.1.2 firmware to CyanogenMod 10.2 Stable (based on 4.3.1) using their installer program. Since upgrading the Wifi has been unusable and I have not managed to get the problem resolved through their forums so I have decided to go back to the stock rom.
Now that Samsung have re-released 4.3 for the S3 in the UK (after the one from last month which was pulled for problems) I would like to use this one as it fixes a bluetooth streaming issue I have endured for a long time. I can't find this new firmware for download anywhere so wondered if it is feasible to download say the stock rom 4.1.2 and then upgrade somehow? I have a red line on the bootup screen which shows it has been modified (which triangle away won't remove due to custom rom/bootloader or something like that) so I believe this means I will be blocked from then upgrading from 4.3 OTA but able to do so with Kies?
Being a novice at this I am obviously worried about breaking my phone and I am not sure if having i9300XXEMG4 as a baseband version is an issue among other things after reading the forums. As much as I have read about EFS and the downgrading modem problems, none of it is making sense to me at the moment, even after reading all the documents. Brain freeze maybe!
The cyanogenMod also changed recovery and unlocked the bootloader going by what I have read, is this an issue I need to worry about?
Any advice that can take away some worries and get me on the right path would be muchly appreciated!
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
JJEgan said:
You are posting in the wrong forum .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Downgrade and network problems .
http://forum.xda-developers.com/showthread.php?t=2531221
Click to expand...
Click to collapse
Thank you for your post. I did follow a link in the !!ALL QUESTIONS GO IN THE Q&A FORUM!! OR THEY MAY BE DELETED!! sticky thread which took me to the Q&A forum where I thought I was posting. It is possible a confusion happened during the sign up process.
After reading those threads, two of which I had already read before posting, I have more understanding than I did before. Somehow I missed about the S3 not having a locked bootlader to begin with. I have backup up the EFS using Ktool but also understand it would have been more useful to do before flashing CM 10.2 as I now only have a EFS v2 backup rather than a version 1. What I am unsure of is what is my best action to take at the moment, going by the information I have. I can it is best not to go downgrade to earlier firmwares unless I wanted an added headache of the modem workarounds but do not see the best way to get back to a stock 4.3 firmware still.
I am on Three mobile (H3G) in the UK but don't think my phone is actually locked to them and don't know if that means the BTU is the option I should be choosing. Even so, when I check the firmwares on http://www.sammobile.com/firmwares/2/ I can only see a firmware added last month which I have to assume is the bad 4.3 update that hit the UK and was pulled after the problems it caused. If it was my best option for flashing, even with the problems it caused, how would I then go about getting the extra update that Samsung pushed out to fix the problem?
I saw the Korean factory flash in one of the threads too, not sure if this is too extreme (and potentially more dangerous) than the other options which may be available to me.
Obviously I would like to do this right the first time, rather than stumble backwards fixing all the mistakes I make at the time. So sorry if I am asking what may be simple to some. My knowledge of phones sucks and I wish I hadn't been tempted by the easy looking Cyanogenmod installer now!
Noticed after a few cache and devlik cleans and reboots that the wifi started working on the CM 10.2 mod but only for the main browser and hit and miss with google play. Every over app didn't work on wifi though, but did on cell. I googled all over to see many with similar problems, which suggested manually setting the time and date and static ip settings, clean davlik and updating play apps after deleting their cache.
None of them worked. So to potentially getting away from flashing, does anyone know any other ideas to resolve this? Wifi connects, stock google browser works, Play works flakey. Other installed browsers wont load any pages or connect to the net, such as speed testing app. The only unusual app that also works in a twitter app. Installed an app to see if there was a hidden proxy setting, but it found nothing, Really strange. All the apps work on cell.
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
boomboomer said:
Follow the guide in general forum, stickies, to flash back to stock BTU. Network lock is irrelevant to rom.
Choose either 4.1.2 or 4.3 but your baseband must be EMG or later as you now have efs v2.
Don't flash things you don't fully understand, any non Samsung rom has drawbacks you'll have to live with.
In the stickies is a world of information supposed to help you.
Click to expand...
Click to collapse
Appreciate you giving me a direction to go. It seems the problem I had finding firmwares the last few days were due to Hotfile going offline and Sammobile rebuilding their index of firmwares. I found through the forums 4.3 BTU I9300XXUGMJ9_I9300OXAGMJ9_BTU.zip which contained a 1.5GB file called I9300XXUGMJ9_I9300OXAGMJ9_I9300XXUGMJ9_HOME.tar.md5 which I think is the correct one which I will try and flash later using the guides. It's not the new fixed 4.3, it's the older broken one but I guess in time I can apply the fix that Samsung are pushing out. This was part of my original question and now i have seen from other posts in the last few days that there is no full copy of the 4.3 anywhere.
The timing of me doing this appears to have been bad for a few of the above reasons, making working it out more difficult to work out for someone who has not done this before.
I can see from your signature and also your post that you think questions such as mine are easily answered in the various threads and through search. Personally I did try all those options first but either my lack of understanding or the overwhelming amount of information meant I was unsure as to what I should actually be doing, let alone which guide to follow. Even googling for BTU or searching xda to try and find what it means was fruitless so trying to put the pieces together is not easy if you have no experience with phones. I have programmed a Pi to do many tasks, built mainframe>SAS gateways and various technical challenges but I still struggle with all the phone flashing info
Many thanks again. Even a few words have been helpful
If you flash the kernel from the Chinese ZCUBMK it will fix all the broken parts of the current uk rom, until the latest ota emerges on xda.
I don't mind helping people who have made a genuine attempt to help themselves, my signature is aimed at the those who flash anything they find then demand someone give them an instant fix.
Your only mistake seems to have been the depth of research before you started, which could have been fatal to your phone -many first time flashes end up with a new motherboard required.
Sent from my GT-I9300 using Tapatalk
If the ota doesn't work in the next few day's I will try that kernel, thanks for that info!
I managed to flash the older official 4.3 firmware just now, so progress has been made A quick check shows me that the power on/lock screen lag problem is present so I assume the other issues will be there too. The red line showing the flash counter has gone and I got no modified phone error when attempting an ota update, as well as device status saying official, so I assume I should be able to upgrade that way when they allow more upgrades on the rollout server.
In case anyone else needs to do the same, this is what I did:
1) Downloaded https://mega.co.nz/#!DVxVgZZb!LIxKGA2Q_KbBH9APo_slOCdZNGJgfn1O6fxOF4C OkHA which I found via a thread titled [Official Firmwares] I9300XXUGMJ9 (Android 4.3) - Ireland (VDI) [04-11-13]
2) Followed the flashing instructions on this page
3) After flashing I got stuck at the Samsung boot screen with the blue light on, even after reseting a few times. So I powered off, held down the home button, volume up and then the power button which took me to the recovery screen where I chose the factory default option. All worked fine after that.
Thanks once again for your help with this boomboomer. A bit of direction was enough to give me the confidence to try it. It's nice to be back to a familiar interface (although it has changed from the 4.1.2 I had before) but the initial setup reminded me of all the bloatware installed. It's a fair bit slower than CyanogenMod was but it all seems to work ok. Once I get the ota update i'll root and freeze some apps to sort that out. Now to install TSF shell
Ok So, I am fairly familiar with rooting and unlocking android devices. But this one has me stumped!
I have a s3 on i535 running 4.4.2. From what I have read its a pain to unlock. I did manage to root it using towelroot and tried to flash the cwm via Rom Manager app. Didn't work. Now basically since I rooted i have noticed a significant drain of the battery. and When I try to do a factory reset I am stuck with "System software not authorized by verizon wireless...." Message. I can get it to boot after entering download mode. I just want it back to stock but I am having a bit of trouble. I am using a mac! My phone does work and at this point it is just that one little feature mentioned above that is driving me insane! I have spent hours trying to find information but at this point I am in need of some one who knows a bit more than myself! Or can direct me to the correct instructions. I am most certainly lost.
Thanks Guys!
-Chris
Report your own post and ask a moderator to move it for you, this forum is for the i9300 only.
Long story short, bootloader is stuck. -- Phone is stuck in a boot-loop of sorts ... it keeps showing the very first screen that shows the Galaxy name and some other info and then flashes that screen over and over again. It is not a boot-loop that loads the OS and keeps loading that continuously. From what I know about phones/programming, which is limited, the bootloader either doesn't exist anymore or the code is not executing properly.
I know there are guides that are similar to my issue, but none of them seem to answer my questions specifically. And when I have attempted some other fixes, nothing happens. I am hoping for a direct answer if anyone has one.
Here's what led to this:
1. I wanted to install the new Android Revolution rom which suggested I have the MJ5 bootloader. I have not attempted to install this rom yet, my issue occurred when I tried to flash the new bootloader.
2. Followed a thread that explained bootloaders and how to install mj5 on note 2 via Odin. --> then got this boot-loop. MD5 and all that jazz was fine. Downloaded from reputable source too.
3. I was/am running a custom rom (JellyBeans build 26 I think) with TWRP recovery. I was previously running CWM recovery, but switched to TWRP because the guide suggested TWRP or Philz recovery for MJ5. Switch between recoveries went just fine. Also, I don't remember what bootloader was installed before I broke it.
I am not a developer (obviously), but I am fairly computer savvy. I can do most things if explained properly. Although I am prone to being an idiot so if someone is feeling a little helpful a step-by-step guide may be best.
I am hoping that someone could (1) provide me with a how-to fix this issue, (2) provide me with a link to the right bootloader that I need to flash in ODIN in order to fix this issue.
PLEASE HELP! I am waiting for some job interview calls this upcoming week and I will be F***ed without my phone. I know it's my fault that the phone is stuck, but I know one of you geniuses here will be able to provide me with some information.
In Summary:
Bootloader is stuck
Phone can get into Download mode, but that's it.
Odin will connect and phone shows up on COM port.
I am an idiot.
I am fine going back to stock recovery/build if necessary to fix this issue.
Thank you all in advance.
P.S. Soul is available upon resolution of the issue; shipping and handling extra ; ) If you don't want my soul I will send you a holiday card with my dogs on it.
You flashed a bootloader for a different phone. Mj5 is for the n7100. The Verizon Note 2 is i605. You have 2 options to get your phone back to 100%. Either use kobols unbrick method found in the general section or send it off to mobiletechvideos and pay them to get it working.
Here is a link to kobol's method: http://forum.xda-developers.com/showthread.php?t=2615587
BluGuy said:
You flashed a bootloader for a different phone. Mj5 is for the n7100. The Verizon Note 2 is i605. You have 2 options to get your phone back to 100%. Either use kobols unbrick method found in the general section or send it off to mobiletechvideos and pay them to get it working.
Here is a link to kobol's method: http://forum.xda-developers.com/showthread.php?t=2615587
Click to expand...
Click to collapse
Thank you for the reply, I will try this now. I saw this thread but was hoping I wouldn't have to do this because of its requirements (screwing with the hardware and such).
Like I said, I'm an idiot.
Thank you for the tip though, it is much appreciated.
axpaxp said:
Thank you for the reply, I will try this now. I saw this thread but was hoping I wouldn't have to do this because of its requirements (screwing with the hardware and such).
Like I said, I'm an idiot.
Thank you for the tip though, it is much appreciated.
Click to expand...
Click to collapse
axpaxp,
You may try the method in this thread: How To: Unbrick A Hard Bricked i605 [n7100 Bootloader Flash] NO Resistor , as an alternative to Kobol's method.