Related
Hey I've been reading conflicting information about this, a lot of which was posted more than a year ago, so I wanted to make a new post just to see if there are any ways that are the most popular/easier now...
I'm currently rooted and running CyanogenMod M2. My phone has been having lots of issues no matter what ROM or Kernal I'm running (just battery life issues and just general slowness).
So I bought a new higher capacity battery and looking to just start my phone over fresh, completely wiping the phone's "SD" card. My goal is to completely wipe the phone, install the newest CyanogenMod and a new kernel.
I've heard two more popular ways, one would be to just relock then unlock the bootloader again which would completely wipe it (I'm confused exactly where that would leave me after I unlocked the bootloader again.. what ROM would it be currently running and would I be rooted, etc).
the other is to just completely wipe it using the option in Clockwork Mod Recovery, but I'm not sure how to install a new OS after I just wiped it since the .zip for the new CM would have been wiped when I did that.
Just reflash factory images through the provided scripts by Google - as you may know, they're available for Linux and Windows, then reflash a custom recovery, reboot. Let it boot once, don't setup Google account now; copy your ROM of choice + gapps if needed (refer to instructions on first post of the ROM thread), custom kernel, whatever. reboot to recovery, factory reset, format /system, flash ROM, kernel, gapps, reboot. Wait for it... Done. This is a clean flash. Setup your device.
Sent from my Nexus
Hey Guys,
I just got a new Samsung Galaxy S3 SGH-I747 in the mail and I immediately started to install Cyanogenmod. I have installed it on two S3's in the past, but this time I had no idea about the new bootloader problems after Android 4.3 (I think?). I got CWM touch installed with no problems via Odin, but when I tried to use the Unified Android Toolkit thing to root and stuff I got stuck in a boot loop. The phone would not boot past the Samsung logo, not the animated one with the purple light, but the one that shows the phone model.
I have tried everything I could think of and all that I tried to google for the past couple hours to no avail. I stupidly did not make a backup of my stock ROM, and I couldn't find a stock 4.4.2 ROM except this one that says it is stock but with root. I flashed that ROM and then it booted past the Samsung logo and the animated one, but is now stuck on the AT&T logo. I looked up that problem and couldn't find any real information on that problem except one thread where it said I should install Kies and let it do the Firmware Upgrade and Initialisation option. That failed and then my phone would only turn on straight to download mode.
I reflashed CWM and that worked so I thought that if I tried to install Cyanogenmod 11 it might work because that ROM is 4.4.1 or higher (Again, I think?). Now it's back into the loop where it makes it past the samsung stuff but then gets stuck on the AT&T logo. Is there anything I can do?
Thanks,
Jemimacakes
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
audit13 said:
Did you try wiping cache, data, and Dalvik in CWM?
Did you try installing CM10.2 from CWM?
Click to expand...
Click to collapse
Yes, I have tried clearing stuff in both CWM and stock recovery. Im not sure about the Dalvik one though, unless that is cleared when you do factory reset and clear cache I didnt do it. I can try flashing CM10.2 ( which I would prefer to have over 11), but my understanding is that my boot loader will not let me install anything that uses any lower versions of android, but I'll give it a shot and let you know.
Ok guys,
I tried to install Cyanogenmod 10.2 and when I put it on my sd card and tried to install it with CWM It threw and ton of errors that look like this.
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG3" || etc etc.
Im not super experienced with programming, but im guessing that CM10.2 can find any bootloader it can use? Im not sure what my bootloader is if that is the case, but I can boot into recovery so I must have something, right?
Anything I can do?
Thanks
Jemimacakes
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Hey,
I did have the latest version of CWM, but I tried it on TWRP and got the same errors
audit13 said:
You should try flashing cm10.2 just to see if you can get your phone to boot. By booting the phone, you can determine your bootloader and modem.
Edit: okay, cm10.2 doesn't work. Are you running the latest version of cwm? Maybe try twrp?
Click to expand...
Click to collapse
Hey,
I have now tried both custom recoveries and gotten the same errors on both, and I made sure I had the latest version of each. Can I flash the firmware from 4.3 and then install CM10.2? Will that work? I really don't want to hard brick my phone.
EDIT: I installed ADB to find out what my bootloader was, and it returned that I had the NE4 version. Is there a way to get the MJB version safely so I can install 10.2?
At this point I just want it to boot up to anything, so if that is easier to do than get CM to work then im completely open.
You cannot go back to MJB from NE4.
How did you try to install CM the first time? Did you use the install manager or a custom recovery?
The last time I installed CM on a i747 was back when the phone was on 4.1.1. The second phone I installed it on was the international version of the phone, also on 4.1.1. I used a custom recovery both times. I bet if I would have used the new installer on this phone it would have worked, but I was trying some other stuff because I was curious and ended up breaking it.
IT BOOTED!
I reflashed the stock firmware + root, reinstalled stock recovery and wiped everything I got it to boot into its stock ROM. From this point, where do I go? Will the CM installer work or will it just brick it again?
Thanks
Jemimacakes
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
audit13 said:
I would copy a custom rom such as cm11 to the internal and external sd card.
I would then download the latest version of philz touch for the d2lte. Get Odin 3.07. Put the phone in download mode, open Odin, uncheck all options except f reset time. Flash philz, when you see reset in the status window, remove USB cable, remove battery, insert battery, boot into recovery, create a nandroid of your current rom, flash cm11, wipe cache, wipe data, wipe dalvik, reboot.
Click to expand...
Click to collapse
Which version of CM11 should I get. On the site I see that the last version of CM11 for the I747 (d2att) was released on feburary 16, is this one based on 4.4.2?
EDIT: Also, I should copy CM11 to both the internal and external storage? Why is this?
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
audit13 said:
You should be using roms made for the d2lte.
I suggest both because cwm or twrp may see one but not the other. This doesn't usually happen but I am always paranoid about something going wrong as flashing always involves risk and I like to minimize risks and be prepared for disaster.
Click to expand...
Click to collapse
Alright, but I have the at&t version of the phone. Are they both compatible with one another?
EDIT: OK, correct me if im wrong, but my new understanding is that CM now has releases for general versions of phones, so the most recent update of CM for my phone is the d2lte, not d2att?
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
audit13 said:
Before unified builds for the msm8960 were started, the i747 was known as the d2att and the i747m was known as the d2can.
Click to expand...
Click to collapse
Hello again,
Thanks a ton Audit, my phone is up and running with the latest cyanogen nightly! A recap for anyone who might come across with a similar problem.
1. I installed a ROM using an older version of android onto a phone with the new bootloader (NE4), softbricking it.
2. I installed the stock ROM + root from this link using Clockworkmod
https://www.androidfilehost.com/?fid=23501681358550126
3. Installed the stock Recovery from this link and did wiped my data and both caches
https://www.androidfilehost.com/?fid=23681161096070493
4. I rebooted the phone and waited at the AT&T logo for a while, and it booted up normally!
5. I installed the most recent version of Philz Touch Recovery for the d2lte, made a nandroid for safety, and then install the latest nightly of CM11 for the d2lte.
6. It works!
Thanks again to Audit for helping me out!
Jemimacakes
I'm glad it all worked and I was able to help in some way.
It's great that you posted your solution in case it helps other people in a similar situation.
I think i'm in a similar place - a few questions. You used cwm to install the stock ROM? I thought you needed to use odin. Also, why did you need to install the stock recovery (and did you just flash the .zip in cwm)? Also, that stock rom you linked to is 4.4, right? Would that work if I was on 4.3?
Before flashing anything, I suggest you confirm your bootloader and modem. Flashing the wrong combination of modem and bootloader could hard brick your phone.
If your phone does not boot, try flashing Philz Touch for the d2lte and flash the latest cm11. Hoepfully, this will get your phone running so you can confirm the bootloader and modem. CM11 does not flash a modem or bootloader.
Wow, what a ride I had with this phone.
Starting with the fact that the model of the phone was SGH-I747 with AT&T branding I then tried to flash a custom ROM for this model, of course everything went bad, we'll not everything, but I couldn't make any calls, see IMEI nubmer and so on.
Thanks to a very helping member of SGH-I747 board, audit13, I found out that my phone is in fact T-Mobile's SHG-T999. I was lucky enough and was able to restore stock ROM of this model.
Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
And I just wanted to make sure that I don't miss anything important.
Phone Data
Model: SGH-T999
Bootloader version: T999UVUENC2
Android Version: 4.3
I've rooted the phone using this guide - http://forum.xda-developers.com/showthread.php?t=1771687 and using March 2014 - 4.3 JellyBean.
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
You could follow this thread to backup your efs folder: http://forum.xda-developers.com/showthread.php?t=1804117
I suggest flashing CWM directly from Odin in download mode. I would not install it using an App from the play store. This is just my personal preference.
All of the other steps look fine.
viltnieks said:
....Now everything works, but since I'm located in Europe I would like to flash stock ROM without all the T-Mobile useless (since I don't have this carrier in my country) apps.
I found this ROM, which seems to be the one best used to get as close to stock android as possible - http://forum.xda-developers.com/showthread.php?t=2501303
....
Could someone please explain difference between -StockMOD Custom ROM- and -StockMOD ROM-? I understand that -StockMOD ROM- is completely based on Stock ROM, little to no changes. But how little are these changes, will I have all the T-Mobile apps?
Click to expand...
Click to collapse
StockMOD Custom has much (if not all) of the carrier branding removed. It has added some customization tweaks to the ROM; mainly XPosed App and Wanam XPosed Module. It also has a few other custom apps and features from newer Galaxy devices replacing the stock apps. It is themed to look like a Galaxy S5 instead of an S3.
The StockMOD ROM has very little removed; KNOX, Syscope, CarrierIQ, and maybe something else. Other than that it will look almost identical to what you now have, including all of the T-Mobile stuff. This one would match the filename in the thread title. It was created first and the StockMOD Custom was added to the thread afterwards, is my guess.
Steps I'm planning to make
1. Backing up efs folder by copying it with Root Browser to SD card and then on my PC.
2. Installing Clockwork MOD and Flashing ClockworkMod Recovery option
3. Creating backup of current ROM with ClockworkMod
4. Downloading StockMOD Custom ROM 4.3 RLS2.1.zip from the thread mentioned above (I'm a bit worried that file name in the thread is different - StockMOD Custom ROM T999 4.3 RLS2.1.zip)
5. Unfortunately I don't see link to T999UVUEMJC modem anywhere.
6. Copying of ROM file and Modem file to SD card (Is it ok if my SD card is only 2GB? ROM is a bit over 1GB).
7. Rebooting into recovery from ClockworkMod
8. Selecting Wipe data/factory reset
9. Selecting Wipe Cache partition
10. Going to advanced and selecting Wipe davlink cache
11. Selecting Mounts and Storage and format /system
12. Installing modem zip (If I can find it)
13. Installing StockMOD Custom ROM 4.3 RLS2.1.zip (is it ok to have spaces in file name?)
14. Praying to God everythings works
Click to expand...
Click to collapse
I would also suggest this post for backing up imei and other nvdata. Specifically the reboot nvbackup instructions.
Since you are on NC2 bootloader and modem(baseband) do not mess with changing your modem to MJC (step 12). You can confirm that it will work on NC2 in the second line of the changelog of StockMOD Custom thread (post #2)
Another thing: I see StockMOD Custom has an Aroma Installer. I have not used a ROM with this option. Aroma Installer will give you choices during the ROM installation, I can only guess what they are without installing the ROM. The choices probably entail choosing between the stock apps and the later Galaxy device apps; Note 3, S4, and S5.
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
viltnieks said:
Thank you, I'm feeling a lot more confident now.
I will definitely check those links on backing up efs folders/IMEI.
Click to expand...
Click to collapse
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
dawgdoc said:
You're most welcome. I personally have used several of these methods, redundancy causes no harm.
Click to expand...
Click to collapse
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
viltnieks said:
I had hoped that everything would go smoothly from this point, it is nothing serious, but I have encountered a small problem.
I followed instruction in the link you provided Part B, point 4, I booted into recovery mode in order to install Synergy Backup. Installation starts, then I get this:
Preparing device...
Setting up 7z
Backing up EFS if unlocked
***Not unclocked Skipping Backup***
Install from sdcard complete.
What is really strange is that after going back and selecting reboot system I get this option in CWM:
Root access possibly lost. Fix?
-No
-Yes - Fix Root (/system/xbin/su)
I verified with titanium backup and root checker that I have root access.
Click to expand...
Click to collapse
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
dawgdoc said:
Good news is that it caused no harm.
Confusing news is that that message was not caused by Part B, Point 4. I have seen that message before on my SGS3 but not my Captivate. On the SGS3 my custom recovery is TWRP not CWM. Also, I only did Part A, Point 2 on both devices. (The Captivate does have CWM as its recovery.) Fact is I have seen the message more than once, most of the time I selected the option to Fix. On the last time I selected No. I retained root on all occasions. I have seen others report seeing that message and I think it was from some action other than nvbackup. All this leaves me with no idea why it is happening.
Click to expand...
Click to collapse
Coould it be related to the fact that I have data_1, data_2, data_3 folder in my root?
Also when I enter /storage/ I have a lot of folders like:
emulate
extSdCard
sdcard0
UsbDruveA
UsbDruveB
UsbDruveC
UsbDruveD
UsbDruveE
UsbDruveF
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
viltnieks said:
I guess this just isn't my lucky week.
I followed the steps mentioned above and install was successful, but I get no OS installed error.
Glad I made those backups...
EDIT:
For some reason the problem was with first file I downloaded in #2nd post StockMOD ROM named StockMOD Custom ROM T999 4.3 RLS2.1.zip
I then downloaded file from #3rd post StockMOD ROM named StockMOD ROM T999 4.3 v4.zip and was able to finish installation successfully. But as you said there is almost no change over the ROM I had before.
Click to expand...
Click to collapse
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
dawgdoc said:
It's possible you had a bad download of the StockMOD Custom ROM. Did you verify the checksum after the download, assuming one was provided in post #2 or the download site? You could always download it again, without verifying, and see if it works correctly the second time.
I just checked my file system and /storage has all of the folders you named with an additional folder, /container. All of the /UsbDrive folders and /container are empty folders on my device. I do not have any idea where they came from.
Click to expand...
Click to collapse
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
viltnieks said:
As it turns out I needed to install StockMOD ROM T999 4.3 v4.zip which is the custom ROM and then update it with StockMOD Custom ROM T999 4.3 RLS2.1.zip
At least that's what I did, now everything works.
Thank you very much for sticking with me during this
There is one last thing that bothers me, during these last few days, I have installed, uninstalled apps, flashed roms, created backups, etc. There probably is a lot of "junk" on the phone at the moment. Is there a way to erase everything and just flash that custom ROM? Like when you reinstall Windows, you format disk and just install a fresh version of windows.
Click to expand...
Click to collapse
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
dawgdoc said:
Glad to hear you have been able to get the ROM you want loaded.
The way to clear out all of the detritus would be accomplished while in your custom recovery. In addition to wiping /cache and /dalvik-cache you would also format /data and /system before flashing the ROM. Before doing that, make sure you save anything you wish to reuse to your computer, or at least to an external micro SDcard. Stuff to be saved off the internal SDcard would include your backups, rom zips, and any app apks you may have a hard time finding again; not just music and pictures.
Click to expand...
Click to collapse
Thank you very much!
CyanogenMod is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system.
Code:
/* Your warranty is now void.
/* I am not responsible for bricked devices, dead SD cards,
/* or you getting fired because the alarm app failed.
/* If you have any concerns about features
/* included in this ROM, ask before flashing it!
Information
I present you with Android 6.0.1/CM13 for the Sprint Galaxy SIII. This is a WIP, I try to work on it when ever I get a bit of free time.
I will try to post a new weekly build once a week or sooner.
The newest build will be at the top of the downloads list.
Prior to Installation
1) I recommend using and/or upgrading to TWRP 3.0.0 (Install version via 2.8.4 zip, then flash 3.0.0 img to upgrade)
2) Make a complete full backup! I cannot stress this enough! Boot, System, Data, Cache, everything. If for some reason this build doesn't work out for you, no biggie go restore.
3) You must be on the NDC modem or it may not detect your sim.
4) Full wipe of the system is required (Dalvik/ART Cache, System, Data, Internal Storage, Cache). CM13 is based off android 6.0.1 and is a completely new version requiring a complete new install.
5) Download and have ready in the device's sim card Gapps Version "Arm, 6.0, Pico". (Other variants may work, I have not tested them all)
6) Download and have ready in the device's sim card the new d2spr CM13 Rom (download below).
Installation
After wipe is fully properly completed...
Reboot in to recovery and go to "Install".
Search for the new Rom where you stored it in the sim and select, DO NOT "Swipe to confirm Flash" at this time, we have to install Gapps first.
BEFORE you swipe, select "Add more Zips" and search for your GappsVersion "Arm, 6.0, Pico" and select.
If you flash the Gapps after the CM install, you will have an error loop so flash during initial install is a necessity.
Now proceed to "Swipe to confirm Flash" and Reboot.
First boot takes some time, but shouldn't take more then 10-15 mins total and progess shouldn't be stalled at any point past 5 mins.
Downloads
cm-13.0-20160322-UNOFFICIAL-d2spr.zip
cm-13.0-20160322-UNOFFICIAL-d2spr.zip.md5sum
cm-13.0-20160311-UNOFFICIAL-d2spr.zip
cm-13.0-20160311-UNOFFICIAL-d2spr.zip.md5sum
cm-13.0-20160305-UNOFFICIAL-d2spr.zip
cm-13.0-20160305-UNOFFICIAL-d2spr.zip.md5sum
Version Information
ROM OS Version: 6.0.1 Marshmallow
ROM Kernel: Linux 3.4.x
Status: Beta
ROM Firmware Required: NDC
Android Security Patch Level : March 1, 2016
XDA:DevDB Information
CM13 d2spr, ROM for the Sprint Samsung Galaxy SIII
Contributors
Novus (aka ThomasJoseph315)
lj50036
Source Code: https://github.com/CyanogenMod
Build Notes
I've noticed that the APN settings are hard to modify. This may change at a later date, but for now it is what it is. If you use an MVNO like do, you will need to flash the APN settings during the rom flash process just like Gapps. I personally have boost mobile and Moped_Ryder has made a very well Boost Mobile zip, though I had to modify slightly with the settings to get LTE working consistently. If you need a zip for your carrier, download the Boost Mobile Zip Ver-2.2 and use notepad++ to edit it to suit your needs.
Possible bug with Gapps. On my first boot, I installed Gapps Mini and was getting download errors from the play market. I re-flashed with Pico, seems to be working.
Very cool to see an unofficial build. Thank you very much. Support for this phone is much appreciated.
Nice work
New build up.
how will i get the NDC modem please?
how can i get the NDC modem or how can i install it?
So installing this ROM, I discovered that the galaxy s3 I have is not 16 gb is 12gb I wiped everything and still is 12 gb, is this normal for this phone SPH-L710?
how you update PRL and profile i can't find it in settings
soulz said:
how you update PRL and profile i can't find it in settings
Click to expand...
Click to collapse
AFAIK u need to flash back to stock TouchWiz to update PRL .... At least that's the only way I was able to get it done recently. (Although there used to be other alternatives I believe)
Hi XDAians,
I'm extremely lost after reading up about rooting, flashing, ROMS, radios/modems etc.
Just need some guidance and clarification regarding my current situation so as to give me a better understanding.
Definitely not seeking to be spoon-fed.
Currently using this as a spare phone after upgrading. Would love to give a new lease of life to my Note 2.
Plans:
1. Change from i317 AT&T (Currently) to N7105 Intl variation
2. To root device ( After changing to N7105)
3. Flash CM/stock touchwiz with latest possible updated Android version+features+UI
- Update to latest version of Android, say 5.X (Lollipop) /ROMs that gives newer features like DN4 which I came across in the forum.
- Play around with different ROMs after more understanding.
4. How to return to stock ( N7105 )
Questions:
1. Do I root then flash ROMs first or the other way round?
2. How do I root? ( Please help me by pointing to me a simple/newbie friendly one)
3. How do I flash? ( Please help me by pointing to me a simple/newbie friendly one)
4. How do I check if my device is unlocked?
5. Is recovery necessary even after i factory reset my phone?
6. What else do I have to know? ( Please help me by pointing to me somewhere I can read up myself)
7. ROMs recommendation.
8. Tips & tricks/experiences in flashing or rooting
9. Checklist before rooting/flashing
10. What is Odin
Thanks in advance!
Are you replacing the i317 with an n7100 or just changing the motherboard to an n7100 motherboard?
audit13 said:
Are you replacing the i317 with an n7100 or just changing the motherboard to an n7100 motherboard?
Click to expand...
Click to collapse
I'm replacing the i317 with a N7105.
1. Do I root then flash ROMs first or the other way round?
There is no need to root if you intend to install a custom ROM. If you want to install a custom ROM, the easiest way in my opinion would be to flash TWRP for the n7100 using Odin.
2. How do I root? ( Please help me by pointing to me a simple/newbie friendly one)
If you want to root a stock Samsung ROM, install TWRP via Odin and then flash supersu from TWRP.
3. How do I flash? ( Please help me by pointing to me a simple/newbie friendly one)
Copy the custom ROM you want to a micro SD card and place it in the phone or copy the ROM to the phone's internal memory. Boot into TWRP, wipe the system, data, cache, and flash the custom ROM.
4. How do I check if my device is unlocked?
The phone does not have a locked bootloader; however, it may be sim locked.
5. Is recovery necessary even after i factory reset my phone?
You need recovery to factory reset the phone. A recovery program should always be present on the phone.
6. What else do I have to know? ( Please help me by pointing to me somewhere I can read up myself)
7. ROMs recommendation.
Search the Android development thread and try out a few ROMs to see what you like.
8. Tips & tricks/experiences in flashing or rooting
Read, read, and read. Also, be ready for potential problems. I highly recommend having a USB jig on hand.
9. Checklist before rooting/flashing
Make sure you are flashing files that are meant for your phone.
I only root phones using supersu and TWRP.
10. What is Odin
Odin is used to flash stock Samsung ROMs to a Samsung phone. Odin is not used to flash anything other than a Samsung.
audit13 said:
1. Do I root then flash ROMs first or the other way round?
There is no need to root if you intend to install a custom ROM. If you want to install a custom ROM, the easiest way in my opinion would be to flash TWRP for the n7100 using Odin.
2. How do I root? ( Please help me by pointing to me a simple/newbie friendly one)
If you want to root a stock Samsung ROM, install TWRP via Odin and then flash supersu from TWRP.
3. How do I flash? ( Please help me by pointing to me a simple/newbie friendly one)
Copy the custom ROM you want to a micro SD card and place it in the phone or copy the ROM to the phone's internal memory. Boot into TWRP, wipe the system, data, cache, and flash the custom ROM.
4. How do I check if my device is unlocked?
The phone does not have a locked bootloader; however, it may be sim locked.
5. Is recovery necessary even after i factory reset my phone?
You need recovery to factory reset the phone. A recovery program should always be present on the phone.
6. What else do I have to know? ( Please help me by pointing to me somewhere I can read up myself)
7. ROMs recommendation.
Search the Android development thread and try out a few ROMs to see what you like.
8. Tips & tricks/experiences in flashing or rooting
Read, read, and read. Also, be ready for potential problems. I highly recommend having a USB jig on hand.
9. Checklist before rooting/flashing
Make sure you are flashing files that are meant for your phone.
I only root phones using supersu and TWRP.
10. What is Odin
Odin is used to flash stock Samsung ROMs to a Samsung phone. Odin is not used to flash anything other than a Samsung.
Click to expand...
Click to collapse
1. So just be downloading Odin from this website ( "odindownload. com" is this tie official website? My chrome extension shows it as malware though ) and flashing TWRP, I can installl ROM?
2. So basically TWRP is an interface which I can flash ROM, root etc.?
3. Alright, in TWRP I can do all these -> "wipe the system, data, cache, and flash the custom ROM" ?
4. I can use my local SIM card though. It shows up 4G, I can make calls and send messages.
5. I see, and this recovery is included in TWRP or is it a separate thing I have to do?
8. What's a USB jig?
I have always used Odin 3.07 for my phones (s2, s3, s4, Note 2, Note 3): http://forum.xda-developers.com/attachment.php?attachmentid=1168421
TWRP is custom recovery. It replaces the stock recovery.
TWRP can wipe the system, data, cache, and flash a custom ROM.
Yes, you can still use your sim card. Some custom ROMs, by their nature, may contain small bugs and one of these bugs may affect your ability to get 4g/LTE.
A USB jog is used to force a Samsung phone into download mode: http://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/
froztheart said:
1. So just be downloading Odin from this website ( "odindownload. com" is this tie official website? My chrome extension shows it as malware though ) and flashing TWRP, I can installl ROM?
2. So basically TWRP is an interface which I can flash ROM, root etc.?
3. Alright, in TWRP I can do all these -> "wipe the system, data, cache, and flash the custom ROM" ?
4. I can use my local SIM card though. It shows up 4G, I can make calls and send messages.
5. I see, and this recovery is included in TWRP or is it a separate thing I have to do?
8. What's a USB jig?
Click to expand...
Click to collapse
It calls Odin "malware" because Odin is a tool that can be used to push things to the device regardless of any security measures other than the stock anti-flashing protocols of the device itself.
It calls it malware and virus because it has the power to alter system, "crack" it basically.
Droidriven said:
It calls Odin "malware" because Odin is a tool that can be used to push things to the device regardless of any security measures other than the stock anti-flashing protocols of the device itself.
It calls it malware and virus because it has the power to alter system, "crack" it basically.
Click to expand...
Click to collapse
I see, thank you so much for the clarification!
audit13 said:
I have always used Odin 3.07 for my phones (s2, s3, s4, Note 2, Note 3): http://forum.xda-developers.com/attachment.php?attachmentid=1168421
TWRP is custom recovery. It replaces the stock recovery.
TWRP can wipe the system, data, cache, and flash a custom ROM.
Yes, you can still use your sim card. Some custom ROMs, by their nature, may contain small bugs and one of these bugs may affect your ability to get 4g/LTE.
A USB jog is used to force a Samsung phone into download mode: http://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/
Click to expand...
Click to collapse
I see, alright! Will give it a go~
..
Why the ... ??
Did ya get it flashed ???
Sent from my GT-N7105 using XDA-Developers mobile app