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?
Related
Hi all,
Excuse the noobness but trying to get my head straight before I dive into rooting and flashing custom ROMS
I currently have a Telstra Australia S2 on kernel DVKF4. My aim is to root and flash Litening ROM
I think to flash Litening ROM I do not have to Root I can just go ahead and flash it however I would like to take a backup of my current firmware first, if I go ahead an install Litening my original Telstra will be gone and wont be able to back it up now?
If I understand this correctly I first need to root and I need to flash an insecure ROM. Now currently the DVKF4 insecure ROM hasnt been uploaded yet... Can I use any old kernel to get root access?
I know if I do this I will get the yellow warning label but will this even matter since after I gain root I am going to flash litening anyway so that will replace the kernel anyway with the litening one and I will not get the yellow warning. Correct?
Anyhoo I wanted to backup current Telstra firmware in case I need to flash it back for warranty. Also I would have to unroot it. So in order to do this I would firstly restore the backup made which would flash back the original telstra ROM but the phone will still be rooted?
Since I made the backup with the 'any old' kernel to get root does that when I restore I am going to have that kernel still on phone and giving me yellow warning?
OK so I would have to flash back the correct DVKF4 kernel to get rid of it again. So I would have to flash back the original (secure) kernel to get rid of this and user superoneclick to unroot and then its back to its original state? (besides the download counter of unsigned ROMS which can be reset with jig)
Also does the yellow warning come up even if you use an insecure kernel which is the same version your firmware needs?
I thought it's the kernel which gives the root access but it's not is it? It just allows superoneclick to install the superuser files etc?
Thanks!
icanfly77 said:
Hi all,
Excuse the noobness but trying to get my head straight before I dive into rooting and flashing custom ROMS
I currently have a Telstra Australia S2 on kernel DVKF4. My aim is to root and flash Litening ROM
I think to flash Litening ROM I do not have to Root I can just go ahead and flash it however I would like to take a backup of my current firmware first, if I go ahead an install Litening my original Telstra will be gone and wont be able to back it up now?
True but you may find copy on Branded roms post dev section or use vanilla Samsung stock rom .
If I understand this correctly I first need to root and I need to flash an insecure ROM. Now currently the DVKF4 insecure ROM hasnt been uploaded yet... Can I use any old kernel to get root access?
Depends upon what the instructions say but generally as near to possible as your rom .
I know if I do this I will get the yellow warning label but will this even matter since after I gain root I am going to flash litening anyway so that will replace the kernel anyway with the litening one and I will not get the yellow warning. Correct?
Incorrect you will need the USB recovery jig to remove the warning and reset the custom rom counter to zero the easy way .
Anyhoo I wanted to backup current Telstra firmware in case I need to flash it back for warranty. Also I would have to unroot it. So in order to do this I would firstly restore the backup made which would flash back the original telstra ROM but the phone will still be rooted?
A backup via CWM of a phone will restore what you backup .
To restore unrooted you will need to save unrooted in the first instance .
Original rom or branded rom flashed via Odin will remove root .
I thought it's the kernel which gives the root access
Yes if you use the usual method no if you use another method .
Root & CWM kernel.
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Click to expand...
Click to collapse
JJEgan said:
icanfly77 said:
A backup via CWM of a phone will restore what you backup .
To restore unrooted you will need to save unrooted in the first instance .
Click to expand...
Click to collapse
Hey thanks but how do I make a backup of the unrooted current carrier ROM? Don't I first need to gain root access to be able to run CWM and make the backup?
Or is there a way I can go into recovery now with the device currently unrooted and stock carrier ROM and make a backup?
Thanks
Click to expand...
Click to collapse
icanfly77 said:
Hey thanks but how do I make a backup of the unrooted current carrier ROM? Don't I first need to gain root access to be able to run CWM and make the backup?
Click to expand...
Click to collapse
As was pointed out above by JJEgan, either wait for the Telstra carrier branded firmware to hit this thread.
Or you can try the root/unroot method as described here. Good luck
mrxd said:
As was pointed out above by JJEgan, either wait for the Telstra carrier branded firmware to hit this thread.
Or you can try the root/unroot method as described here. Good luck
Click to expand...
Click to collapse
yeah thanks I get that part it's just that he mentioned if I want back a backup of an unrooted rom I need to make the backup while unrooted but I did not think this was possible since you need to root first before being able to backup?
Just after some clarification about that.. Thanks
I have a sgs2 and rooted it with odin oneclick... now i cant upgrade to the latest firmware.. i think it's 2.3.4 (or if there is an even newer version out now) since it's rooted, can anyone help me out how to do this upgrade (to latest firmware) the easy way so i dont loose anything on the phone.
My current kernel is 2.6.35.7-I9100XWKDD-CL161513.........
Build number gingerbread xwke2 if this info helps..
Im would be very happy if someone would be so kind and help me with this, thanks in advance for any help.
Can you not use kies? Should still be able to use it rooted.
Root has nothing to do with KIES upgrades... If KIES says "This is the latest firmware" then it is indeed the latest firmware for your country/code... 2.3.4 is not yet released officially to many countries and country codes yet...
If you flashed somewhat BETA or custom ROM you get error like "You cannot upgrade this" or something similiar to that...
I get a error failure report, and to try using kies or something else. I tried doing the upgrade on the phone directly, checking for updates and downloading and installing, but everytime i get this error failure report
My phone is unlocked, and now i flashed it with original kernel to remove that annoying ! mark in bootup, so now i dont have a unsecure kernel any longer... but even with this original kernel now i couldnt upgrade the firmware using only the phone
Is it a must to use kies ? if so i will try it, cause i have a working kies on one computer. I just thought i could do it directly on the phone under checking for updates, but that way dont work for me.
So it does not matter if my phone is rooted when i want to update my firmware to newer like 2.3.4 or newer ?
You can just grab a stock rom from the thread in original dev and flash it via odin, kg6 is a good 2.3.4 rom, kh1 and 3 are a bit unknown at the moment.
Your best bet is to flash cf root on your phone, take a nandroid backup via it, use titanium backup or equivalent for your user apps and user app data (and some system data, as shown in green in the app) and do a full wipe, flash the new stock, and restore using titanium or equivalent.
The nandroid is a snapshot of your phone at the time, which will allow you to roll back to a known good point at any time.
Sent from my GT-I9100 using XDA Premium App
No rooting wont effect kies. Try Kies first, See if indeed there is a update available to you. Like the previous poster said 2.3.4 is not available in all countries yet...
If your desperate to update you can use odin to upgrade the firmware instead..but that will wipe all data on your phone, so you will have to use Titatium Backup first. But if I were you I'd just use kies, and wait for the official update in your country.
Hmm if you can't update with KIES and you don't want to wipe then your best bet is to flash with ODIN with one of the frankenstien firmwares provided at one of the threads in the original development forum.
It did worked using kies on my computer, but it's still 2.3.3... guess it updated something minor then.
Thanks everyone for your help !
Does anyone know if i can remove the question mark in bootup and still be able to overclock the phone ?
boarne71 said:
It did worked using kies on my computer, but it's still 2.3.3... guess it updated something minor then.
Updates are as and when the provider of the phone updates the firmware .
They do not use all Samsung updates and often push them out much later .
Does anyone know if i can remove the question mark in bootup and still be able to overclock the phone
Yes via the instructions in root thread
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Or by using the USB jig .
jje
Click to expand...
Click to collapse
I know after root i can flash with the original, but that seams to remove the possibility to overclock the device but the root are still there after flashing with original.
boarne71 said:
I know after root i can flash with the original, but that seams to remove the possibility to overclock the device but the root are still there after flashing with original.
Click to expand...
Click to collapse
No you flash root then flash original wipes root .
You would be better to find an overclocking rom and work from the instructions there .
jje
It's flashing the kernel im talking about. When rooting a phone you flash the phone with a unsecure kernel, then after it's rooted you can flash it back to original kernel so the "!" mark wont show in bootup.
Now i wounder how to do that and still keep the overclocking feature, anyone know how to do that ?
boarne71 said:
It's flashing the kernel im talking about. When rooting a phone you flash the phone with a unsecure kernel, then after it's rooted you can flash it back to original kernel so the "!" mark wont show in bootup.
Or ue the USB jig .
Now i wounder how to do that and still keep the overclocking feature, anyone know how to do that
If the overclocking features are part of the kernel then flashing original kernel replaces the kernel that has the overclocking features .
jje
Click to expand...
Click to collapse
Yes that was what o thought Thanks everyone so much for all your help!!
I guess i just have to live with this "!" mark on bootup, no big deal
Look at chainfires post number 2 on this thread to remove triangle and still keep insecure kernal here
I have a i9100 rooted CWM (forgot the kernel name) and MIUI installed. I would like to change to the most currect ICS available for it without using custom roms.
Selling to a friend who wants it more or less reverted to the manufacturer. I live in the US and I seem to need assistance with this as its been a while since I've done it.
I'd like to get the best kernel on there too and root after flashing back to ICS as well as keeping my contacts on my sd card.
Search for a stock ics firmware and flash it with Odin.
Here a post that may help you.
Is it just a matter of installing from the SD card like you normally would when flashing custom roms?
Would it lose the root?
Also, the post you mentioned doesnt have any american versions of the ROM. Would that matter? Im just wanting to make sure it will work with ATT and be in English
Here a thread with more information.
With Odin you must connect the phone to PC in download mode and yes, you will lose root flashing a stock firmware. After you can flash an insecure kernel (Chainfire's for example) and gain root again.
What do you mean by insecure Kernel?
And is it going to matter if I install the rom from a different country?
I think I just might have discovered a (relatively) painless and (relatively) quick method of rooting a stock Sony ROM. The following process was executed on an Xperia Mini with bootloader unlocked via testpoint method.
1. Flash stock .431 Sony ROM (downloadable from here)
2. Reboot and let the initial setup steps complete
3. Hotboot using FlashTool with EXtended Stock Kernel available here
4. You are now partially but not completely rooted as TB will inform you
4. Connect to Google Play and update installed apps.
5 This will also update Superuser (remember, we're hotbooted using the EXtended Stock Kernel so Superuser is installed by default.
6. When you update Superuser, most probably what it does is push the appropriate files and set the correct permissions into the operating system.
7. Reboot normally now (with the standard/regular Sony included kernel) and you'll find yourself rooted as can be verified by TB and rootchecker
Please hit the thanks button if this was at all useful. It would be awesome if somebody could corroborate this by independent testing as well.
everyone knows flashing custom kernel with autoroot will automatically root your phone :/
an0nym0us_ said:
everyone knows flashing custom kernel with autoroot will automatically root your phone :/
Click to expand...
Click to collapse
this wasn't a permanent flash of custom kernel. i temporarily hotbooted the custom kernel, updated superuser then rebooted back into stock kernel and the root was still there
rahimali said:
this wasn't a permanent flash of custom kernel. i temporarily hotbooted the custom kernel, updated superuser then rebooted back into stock kernel and the root was still there
Click to expand...
Click to collapse
Anyway this method is for unlocked bootloaders and why do such long procedure when you can have a rooted device with one simple step?
Sent from my GT-N7000 using xda app-developers app
well, if you want to have a completely stock ROM including stock kernel without flashing a custom stock kernel which you would otherwise have to do if you wanted root
so basically you're retaining everything stock plus you have root as well
naw, if you reflash kernel.sin without wiping data you retain stock kernel without loosing root..
Rudjgaard said:
naw, if you reflash kernel.sin without wiping data you retain stock kernel without loosing root..
Click to expand...
Click to collapse
thats my point, isn't it, you only have to permanently flash the stock ROM including stock kernel just once, that's it.
after that, you just hotboot once with extended stock kernel, update superuser, reboot normally and you're good to go
Every one can root stock ICS with unlocked bootloader! So I found nothing new in your method except pain in the ass process! Isn't easily to flash autorooted kernel and switch back to stock if you want to use it
Sent from my ST15i using xda app-developers app
Actually the extend stock kernel is still stock kernel. The kernel binary is still the same as sony stock kernel, difference is just in ramdisk, added cwm and autoroot. If u already flash it, doesn't make sense to reflash stock kernel again. U got built in cwm without need to reinstall cwm after every rom flash, with the same exact kernel as stock kernel.
One little thought : Many people might want root without unlocking the bootloader, because once you unlock it, there is no turning back. So, that does not sound as "everything stock" And moreover, unlocking bootloader is really a scary process for many. I myself got root first, and unlocked the boot loader months later.
tintin100 said:
One little thought : Many people might want root without unlocking the bootloader, because once you unlock it, there is no turning back. So, that does not sound as "everything stock" And moreover, unlocking bootloader is really a scary process for many. I myself got root first, and unlocked the boot loader months later.
Click to expand...
Click to collapse
same here. other than that, sorry about this thread, maybe the mods could delete it please?
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