Rooting a UK GT-i9305 - Galaxy S III Q&A, Help & Troubleshooting

Is there a safe way to root a GT-i9305 yet? I read a lot of stuff about people loosing their IMEI and bricking their phones. Also I saw somewhere that there's a counter that increments everytime you flash custom firmware (which invalidates your warranty).
Can someone clear up my confusion on the state of rooting a UK GT-i9305 that I got from Orange UK originally but now I've unlocked it using unlock codes I paid for and without rooting.
All I want to do really is be able to do USB Mass Storage, Remove all the bloatware apps, and install custom ones.
Thanks in advance, :fingers-crossed:

I rooted my I9300 using CF auto root here
http://forum.xda-developers.com/showthread.php?t=1957273
It supposed to work with the newer I9305, just make sure you download the file for your model.
I think loosing the IMEI only happens when flashing roms (but could be wrong). There are tools in play store for backing up the EFS folder, also some if not most roms now back this folder up anyway during the flash process.

Related

Rooting S2

How do i root my s2? Can anyone refer me to the proper rooting document and the latest updates? If we do rooting will we loose the warranty from the company? Can we restore to the original kernel/firmware if anything goes wrong with rooting? Will get restored to factory settings? I just brought s2 and i'm new to Andriod OS? Also by rooting the phone can we change the installation path of apps and games to the external memory(I'm takling about the 12 gig internal memory which will be shown as sdcsrd in file manager)?
I recommend Rooting, it will allow you to access system files. The easiest and effective method is Chainfire's, follow this,
http://forum.xda-developers.com/showthread.php?t=1103399
You will need to flash back the Stock kernel to get rid of the Yellow traingle, follow this thread for that,
http://forum.xda-developers.com/showthread.php?t=1075278
Rooting will void your warranty, but if you flash back the Samsung signed kernel and reset the ROM counter with an USB Jig then you will have warranty.
Regards.

[Q] Am i doing this right?

Just got a bell 9100M carrier locked and just want to make sure i have done everything the best way possible. I've owned HTC's since the G1 and this is my first samsung. Phone is locked to bell and i am using it on rogers.
1) I've rooted with zergrush on the stock Bell 2.3.3 Rom (don't remember firmware). Used the galaxys2root.com which worked fantastic and installed CWM
2) Attempted to recover sim unlock code with Chainfire unlock tool. Failed, used Helroz Galaxy_S unlock with success.
3)Backed up rom, wiped and installed the CM9 nightly.
4)Used triangle away to reset the count
Everything seems to be working perfect, nothing seems to be missing. I'm very pleased with the device.
My questions are
1) Does Helroz unlock just modify the baseband? Will the unlock disappear if change basebands? Is there any advantage to changing to a different baseband if all is good?
2)I gather the CFroot method is mostly applicable to stock roms?
3)I can't use rommanager to install CWM. What am i missing here?
4)Download mode and Odin are mostly used to flash kernels, radios, and system files without triggering the yellow triangle?
Thanks for the help. I'm just getting my head around the differences between the way i did things with an HTC Device, i had a g1, magic, nexus one, EVO3d. Thanks for helping a samsung noob.
The first and magar thing now is to take efs backup using this
1.It modifies efs nothing with baseband, so you can flash any baseband
2.Yes CF-root for stock roms, other you flash comes prerooted
3.Yes you can't, just flash CF-root which have cwm recovery build in
4.They increase the triangle if you flash custom kernel or CF-root
So once you install CF-root always use CWM recovery(that won't increase the counter)
sahibunlimited said:
The first and magar thing now is to take efs backup using this
1.It modifies efs nothing with baseband, so you can flash any baseband
Click to expand...
Click to collapse
So now that i have used Helroz unlock tool, my phone is unlocked for good?

[Q] Mobile Odin Flash Procedure for Stock

Hello there,
an acquaintance of mine has bought an SGS3 i9300 (international) from Thailand but wants to use it in Germany.
The Stock Android Version is 4.04 which cannot be updated using OTA, it says none available.
As he would like to use his S3 in German, I offered him to try flashing a Stock Firmware with Region Germany and CSC "DBT".
Since we can see each other only once more and have no access to a computer at that time, I have planned a way to manage this which I would like to know about whether it may or may not work:
1.) Use Chainfire's ExynosAbuse apk to root
2.) Reset Flash Counter with TA (Is this required when using ExynosMem exploit to root?)
3.) Use Mobile Odin to Flash PDA "I9300XXELL4" and wipe Data, Cache and Dalvik
4.) Optionally change CSC to DBT, first testing with *#1234#, then changing with *#272*Device IMEI# or CSC Changer from GPlay
Finally Factory Reset in settings app.
A) Will this device then be completely Stock (expect for the wanted region change) and, in future, able to update with Kies or OTA?
Hence, with System Status Normal, Custom Binary Download No and Flash Counter set to zero?
B) Would you rather recommend not to care about CSCs and the region but choose the newest Firmware XXELLC (from Europe)?
C) Is it OK just to flash the .tar.md5 firmware package from extSDCard or would you rather copy it to the phone's internal SDCard first?
Thanks in advance, :victory:
juicer.
1. Exynosabuse (root)
2. Mobile odin xxellc
3. TA (unroot)
4. Factory reset
I won't worry too much about csc, but you will want to check the csc is one that is corresponding to the firmware to get kies updates. I never had the problem but some people report getting KOR csc when flashing firmwares..
Also check to make sure device status if official.
Sent from my GT-I9300 using xda premium
Thanks!
Why is it better to stick with EverRoot, thus injecting SuperSU and Root while flashing? MobileOdin itself won't trigger the flash counter if it's true what I read.
And I guess due to the fixed ExynosMem Exploit Root will just be gone?
I'm just a little scared we somehow screw it up and have no chance to fix it due to the lack of a PC... Is a brick probable?
And how about the strict update to JellyBean, is the new bootloader flashed that way and if, will it affect something?
Tbh I really can't tell you. Every device is different and as with any unofficial methods, you won't get any help from samsung if things go wrong. As for everroot, I guess you don't need to check it as you don't require root.
But do note TA Might not work without root? I'm not too sure about this. Might wanna check for somebody else's opinion on this.
As for bootloaders, you will probably want to back your apps up in case they get wiped, but you won't be able to restore them without root so I don't know what your options are.
Sent from my GT-I9300 using xda premium
I just wanted to report that everything worked fine, didn't use EverRoot so the device was in wiped and unrooted Stock state after flashing which was the goal — achieved it
Great to know
Sent from my GT-I9300 using xda premium

[Q] Backing up and rooting/unlocking bootloader question.

Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
I see its been a few days and no one has replied so I will do my best to share what knowledge I have. I've been heavily flashing custom ROMs on my ASUS tablet now for the better part of a year and just got my Verizon GS4, so I have alot of the same questions as you.
1) I'm going to answer this in two parts.
​Nandroid, in my experience, refers to the type of backup, not necessarily the process by which to backup. Most common recoveries, including ClockworkMod and TWRP have a feature to create a 'nandroid backup'. This can take some time and files can be quite large, as they copy pretty much every single file on your device; almost like creating a snapshot of your device in that moment in time.
​To answer the later part of this question, (typically speaking) once you unlock a bootloader you cannot re-lock it, but that could be different for phones (my knowledge in phones is limited). And yes, using a nandroid backup will back up your device with root access, but using a tool such as Rom Toolbox, you can easily un-root (the program features a 'permanent unroot option'). For one, I would imagine that flashing the stock kernel would overwrite the root, as like you said earlier in the post the current root exploit works by flashing a pre-release kernel, applying root to the device, then re-flashing the current stock kernel. Another way to lose root is to get an over-the-air (OTA) update. You will see programs like OTA Rootkeeper that work to circumvent this, but in your case that may be a valid way to cover your arse in case you need to return it under VZW warranty (it is for this reason that I always buy Best Buy protection plans, because they could care less about the software state about your device [Disclaimer: I worked for Geek Squad so I have /somewhat/ intimate knowledge in this matter])
2) I just rooted my GS4 a few days ago, and nothing I read indicated that the all-in-one tool would unlock the bootloader. If you read the documentation about Loki, he explains this fact. I just found a good video (although it uses TWRP and GooManager instead of ROMManager and CWM) explaining that there isn't a bootloader "unlock" just yet; rather its a workaround to the bootloader that allows us to get custom ROMs on our devices (video is here)
3) "Bricking" a device means rendering the device useless; it won't operate to any fashion that it is useful to you, so its no better than a brick or a paper weight, etc. I would imagine you can re-flash a stock verizon ROM/kernel to restore any screw-ups, but keep in mind this device was released less than three months ago and any development is relatively new. Yes, we have had other Galaxy S series phones, but the S4 has this whole KNOX nonsense that is specifically designed to prevent the kinds of activities we do here on this forum
I really hope that helps. If I said anything that is incorrect, please please feel free to correct it so that at least we can all learn the proper information.
Thanks,
Opethfan89
goodmedic said:
Hey all, I'm looking to eventually install CyanogenMod 10.1 on my verizon galaxy S4. However, being a complete novice on this type of thing makes me a bit nervous about bricking my expensive phone.
So, I thought it would be good to try and understand the process of rooting and installing the custom rom. Could you guys help me out? I'll list what I know.
First thing I want to do is backup the Android stock rom that came with the phone. I have read that rooting or installing a custom rom (like CM) will void my warranty, so that's not good. But re-flashing the stock android that came with the phone will remedy this. To do this, I found this guide on using Nandroid. I don't think the CWM way will work for Verizon galaxy S4 (read that somewhere, but correct me if that's wrong).
However, it says that I am required to have a rooted phone first before running Nandroid.
Because Verizon's Galaxy S4 comes with a locked bootloader, and an unrooted phone, I need a way to root my phone. I found this nifty all-in-one tool by bhp090808.
The way that tool works is it exploits something in verizon's pre-release kernel of the S4, so it flashes the phone with the pre-release kernel, gets root privileges, then reflashes the stock kernel. Once this is done, my phone will be rooted and I assume I can use Nandroid to backup the stock android on the phone.
This is where I'm stuck. I have a few questions regarding various parts from here on:
1) Since the phone is rooted and I run Nandroid to back up the stock android rom, wouldn't Nandroid back up the stock android rom with the root access? If I needed to return my phone to Verizon under warranty, re-flashing this stock rom would still void my warranty because it still has root access? Is there a way to completely revert to stock android with verizon's unrooted and locked bootloader status (and whatever else)?
2) Does the all-in-one tool unlock bootloader? I found a tool called loki which will unlock the bootloader so that I can install custom roms like CyanogenMod. I looked in the all-in-one tool's zip folder, and it contains a file called "loki_flash", but I am unsure if this is unlocking the bootloader or not.
3) Can I re-flash a stock android if I brick my phone? What exactly does 'bricking' the phone mean?
Click to expand...
Click to collapse
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
DarkMenace said:
The S4 link in my signature has a few stock images to pick from. It will restore it to the original stock Verizon software that came with your phone.
Click to expand...
Click to collapse
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
opethfan89 said:
Does the 'Ad-Free' APK I see available on that website work better than jRummy's AdBlocker? I installed it and it detects ads (like in ASTRO, Zedge, and a few others) but doesn't block them even though I have all the settings turned ON and have rebooted when requested.
That said, thanks for the link. I've bookmarked it for future reference and its good to know there are backups available in case anything goes bad.
Are you able to elaborate on how these are flashed? Via ODIN, or can you flash it via CWM/TWRP?
Thanks,
Opethfan89
Click to expand...
Click to collapse
I'm not n sure. It's the only one I ever used for banner blocking. You use the files with Odin as well after they are extracted.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium

how to root i9205 on UCNA2 firmware?

hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
there are a lots of guide but everyone say a different method. OK I AM A NOOB OF MODDING.
but is quite difficult to understand guides that are different in this way:
1) some indicates to just use an apk autorooting the device
2) some do require to change thekernel + manually install the superuser apk
3)not permanent root....
4) others......
so, please be patient......:angel: i only want to find a "normal" root method.......and IF POSSIBLE a root that could allow me to easily UNroot the device to be able to update my firmware OTA in the moment samsung will update our great device to kitkat
If you are a noob at modding don't even bother with rooting. Its dangerous and BTW I think your firmware has KNOX which the GMega doesn't have a workaround.
Sent from my GT-I9200 using Tapatalk
realista87 said:
hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
Click to expand...
Click to collapse
If you are brave enough you can try it using this tutorial
http://forum.xda-developers.com/showthread.php?t=2574953
But read it thoroughly and if you do not understand one thing though - do not attempt to try.
Read forums and learn till you can understand what you are doing lest you have quite expensive paperweight... I am not responsible for what you do with your phone!
my previous phone was rooter, the optimus 3d and the ascend mate.
i don't need toor for extreme modding but just to install a custom recovery for a nandroid backup and for use SOME APP THAT REQUIRE root to work properly.
i never installed a recovery but i read everywhere that it is a lot usefull in case of some errors, to restore the previous backup made 1:1 (nandroid)
Every modding attempt must start from root and (optionally) custom recovery. In fact - rooting itself is modding and quite heavy from system point of view. If you want to change ONE THING in system, you have to root your phone. Doing this you are tripping 'warranty flag' and from now on your warranty is void.
If you have firmware with KNOX and new bootloader - tripping this flag is irreversible. But as long as you do not attempt to flash older firmware (before KNOX) it does not affect the operation of the system. Trying to flash older firmware makes your phone softbrick because of tripping security mechanism in new bootloader.
If you already rooted your phone it is resonable to flash custom recovery and by this have wide possiblity making backups of your whole system (nandroid backup) or flashing custom ROMs

Categories

Resources