Related
Note from rootsu:
XDA staff have transferred ownership of this thread to me so that I can update the rooting methods. The reason for this is because the rooting method contained within is outdated and since identified as unsafe.
I have PM'd the original OP @Stormlister to update the thread but unfortunately have received no response.
I aim to keep the structure of the thread in tact. I am only here to edit out / replace outdated and unsafe methods contained within this thread. The work below is not my own.
Disclaimer:
This guide is for total noobs (I am one myself). Until the information here can be confirmed by an experienced person please don't bet on the fact that this information is 100% accurate. I studied and put together bits and pieces of information that I found everywhere, tried it and it worked. I will mention the sources. Even though its probably not a good idea for a noob to write any sort of guide, these were taken from working sources, I have tried it myself and all works flawlessly.
About me:
I write open source software and also write documentation.
Why:
I wrote this tutorial as I found the scattered information all over kinda confusing on the subject of flashing, wiping and ROMS.
Who's it for?
You already know what you want to do, but don't know where to start.
THIS IS A WORK IN PROGRESS.
--------------------------------------------------------------------------------------------
Getting Started - Rooting
--------------------------------------------------------------------------------------------
Root means you are opening the operating system to allow a user or application full read and write access. This is needed by some special applications to change operating system files. For example the "Adfree" application changes system files to block certain domains which completely stops ads from showing up on your phone. Unlike other systems like in the iOS, all the root applications are available in the Google Play store, I think Google is great for allowing this.
The main thing I root first even though it is not needed to flash a rom is the fact that you ALWAYS need to make a backup, if something goes wrong you have a something to fall back on and the friendly xda community can help us get things running again.
The easiest way I found to quickly and safely root was by using the following software:
ODIN (Desktop software) (Incorrect usage may make your phone unusable.)
Before you start using Odin, make sure all the Kies* services on your desktop is stopped. (On Windows, you can press Ctrl+Alt+Delete, go to task manager, services and stop it from there). Infact you should consider uninstalling Kies altogether as it is really not needed if you are going to root. There are more than enough backup software that does not add the bloatware.
This piece of genius is a tool to flash among other things a new ROM to your phone.
We will be using this piece of software twice, first to root it, and then to flash your S3 with a new ROM.
------------------------------------------------------------------------------
<rootsu insert>
Recommended methods to "root" depending on your requirements...
1) You want root only. No custom ROMs, kernels etc. Just root, just to use root apps.
CF Auto Root Via Odin
Why? Tried and tested method, simple to use. No need to choose what exploit you want to use as it's tailored for your device.
What does it do? It gives you a stock recovery (so can't flash things) and roots the Android OS
The Steps:
1) Download the Latest Odin
2) Download CF-Auto-Root for your model
3) Follow These steps to root
2) You want to flash custom ROMs / Kernels
If you want root on your existing Android ROM, you can do 1) first. Then flash a recovery of your choice (CWM, Philz, TWRP) via Odin
However, if you immediately plan on flashing a ROM, there's no need to root your existing ROM. Simply skip straight to installing a recovery. Backup then flash what you like.
The Steps:
1) Download the Latest Odin
2) Download recovery of your choice CWM, Philz, TWRP
3) Follow The steps to Flash Philz recovery (But for the recovery of your choice)
These steps can also be followed to update recovery to newer versions
</rootsu insert>
------------------------------------------------------------------------------
Difficulty: Easy
After you have completed the tutorial your phone should be rooted and ready to go to the next step.
--------------------------------------------------------------------------------------------
Backing up
--------------------------------------------------------------------------------------------
The next thing we will need to do is backup our current apps, settings and even ROM. Now that the phone is rooted we can install a few applications to help with this process. Lets do this now.
In Google Play Store, search and install:
Titanium Backup (Google Play)
With this tool, you will be able to backup application and settings of your current installation.
To do so;
Open Titanium Backup
At some point it will ask for root access, you will need to allow it root access.
Click on Backup/Restore.
It will show you a list of software.
Click the ok tick top right.
It will now show a list of actions you can take.
You will now [ RUN ] Backup all user apps+ system data.
It will flip to a new screen, click top right ok tick again.
The backup process will take a few minutes.
After the backup completes, we will need to copy it to a safe place, just in case something else goes wrong.
With above explained, there are more optimized Titanium Backup methods, this is a must read:
http://checkrom.com/threads/titanium-backup-explained.433/
You could also backup your whole system from the boot menu of ClockWorkMod / custom recovery - which you will already have if you used the rooting method above. Have a look at this short yet very informative video to do just that:
http://www.youtube.com/watch?v=sPvNr7LqP30&feature=related
Difficulty: Easy
Bear in mind that custom recoveries vary, they all work pretty much the same. The backup is referred to as a "nandroid" backup, but in the recovery menus, it may well be referred to as simply "backup and restore".
To boot into whichever custom recovery you have installed, power off the phone. From off, hold Volume Up + Home then press and hold Power until the S3 splash screen shows. Release power. Once in recovery, find the backup and restore menu and take a backup.
There is one more place you need to manually write down some settings, the APN for your data and MMS, this is the only area besides the branding when another countries stock rom might affect you if you chose to use it. So head over to;
Settings->More Settings->Mobile Networks->Access Point Names.
Click on each and write down its settings.
Backing up EFS folder
---------------------------------------------------------------------------------------------------------------------
The EFS is a filesystem folder which contains important information like for instance your IMEI (International Mobile Equipment Identity) number, even though I cant find any evidence that anyone lost their EFS folder yet, I think it is probably important enough to back it up. First open your favorite file browser like ASTRO and click on your internal build in sdcard0 and see if you have a efs_Backup folder. If you have such a folder its is probably backup up inside already. To be honest, I dont know what backed mine up, but it was there, and it will be likely there if you followed the procedures listed in the collection of this tutorial.
However, the folder is only 6mb, if you don't have such a backed up folder, using an application like KTOOL, gives you the ability to backup the whole "/efs" folder to wherever you like. The external SSD and also your PC would be a good idea to back it up to.
----------------------------------------------------------------------------------------------------------------------
Difficulty: Easy
--------------------------------------------------------------------------------------------
ROM - Hunting for a new rom
--------------------------------------------------------------------------------------------
************************************************************************************************************
My ROM is not YOUR ROM
But I have an S3, wtf is this? Note that when hunting for a ROM that you make sure it is either based on your models ROM or supports your models ROM. The reason this should be noted is because the models are so profoundly different, from Dual Core to Quad Core, from 1GB memory to 2GB memory etc. This means each ROM is optimized of based on a specific model. If you have the GT-I9300, you have the most popular model which has a lot of custom ROMS.
Read more about the differences here:
http://forum.xda-developers.com/showthread.php?t=1870827
************************************************************************************************************
This is where I got confused, I did not know if I had to match the code base of my factory stock rom to the rom I wanted. I was afraid that it might flash my modems software making my phone unusable with my service provider. It seems that the rom file is only to flash the actual OS and wont include the modem flash too.
So what ROM to pick, there seems to be very good ROMS out there, but know, the further you go away from the stock rom, the more difficult things become. You might just want to upgrade to the latest Jelly Bean and not worry about an improve stock Samsung rom. Or you might want to take it to a whole new level and perhaps install a pure Android rom (however, I noted a few people having trouble with the pure android rom, you really need to know what you are doing). But as I say, it seems things gets kinda tricky the further you move away from the Stock Rom.
Lets look at a few examples of solid roms:
At this stage we only have one stock rom available in Jelly Bean, this is most probably the safest bet when you only want to upgrade to Jelly Bean (If you do decide to just go with the safest rom, you can just root again after the rom was successfully flashed) [INTERNATIONAL GALAXY S3 ONLY] [DONT USE THIS ROM ON ANYTHING ELSE THAN INTERNATIONAL VERSION (IT WONT WORK)]:
http://forum.xda-developers.com/showthread.php?t=1646610
Now we can start looking at roms based on stock roms that was improved by a linux guru, very good example of such a rom which is very solid is Android Revolution HD, if you have other Samsung devices I would recommend sticking to this one as it comes stock with Allshare Play:
http://forum.xda-developers.com/showthread.php?t=1797334
The most popular OMEGA rom for the S3 international, pure awesomeness:
http://forum.xda-developers.com/showthread.php?t=1663656
Then you get completely customized roms like Cyanogenmod, this is next level roms and should probably only be tried once you are more confident with flashing ( . Y . )
Note that Cyanogenmod is very controversial for the international version of the S3, there are technical issues, and newer stable version is always behind, I would NOT go for Cyanogenmod at the moment..
http://www.cyanogenmod.com/
For a very nice list of roms and some explanations have a look at:
http://forum.xda-developers.com/showthread.php?t=1674286
Now that you have your rom, lets continue.
Difficulty: Easy
--------------------------------------------------------------------------------------------
Wiping & Flashing - Cleaner Flashing Method
--------------------------------------------------------------------------------------------
[I will try and confirm all my findings below]
When people refer to the term wipe, it is my understanding that it means to delete the old ROM from various locations. This ensures a more clean installation, almost like its better to install Windows afresh instead of an upgrade. However, this is not Windows, its Linux, I am sure the logic behind this is because the way Linux works, it has certain files in certain directories, that if the file is there, the service is loaded automatically. Now if you had to replace a stock rom with something completely different, some of those auto loaded files will be left behind and you will be stuck with loaded services that should not be there. But this is just my experience, I am not sure if this completely accurate.
This is where things might start becoming slightly confusing. Many people seem to argue that when upgrading from a stock version to another stock version that you don't need to wipe, I completely agree with this, as this will almost be the same upgrade process the default upgrade will follow.
However, if you upgrade to a very different ROM, start paying attention, as things might just get slightly more complicated. This I have not tried myself yet, but it seems that for this to work you wont need Odin.
Some people also recommend formatting and not just deleting, I will even advice against this, this is the EXT4 filesystem, not some NTFS filesystem. I cannot see the real benefit of formatting.
At this stage I don't know how to wipe the phone if you are going to use the alternative Odin flashing method explained below, this I have done, tried and tested, working fine:
[Below method I use to flash my own international S3]
This is what you will be doing to install a custom rom while wiping it for a fresh install (make sure you have your titanium backups handy ):
Copy your ROM inside an easy locatable phone folder by browsing to it, from your PC and copying it to your phones folder using your micro USB cable. I strongly recommend using your External SD card as some roms may wipe your internal SD card leaving you without any ROM to update.. that will be very sad. :crying:
Boot into recovery (Vol up + Home + power from off)
You will see a new Unix like screen appear, use volume + and - to navigate up and down, home button is enter, and soft touch back button back is back.
Next we will wipe the phone (if your ROM does not have special instructions on wiping this is a standard method).
Goto Wipe Data/Factory Reset -> Yes
Goto Wipe Cache Partition -> Yes
Goto Advance -> Wipe Dalvik Cache -> Yes
Next Select Install Zip from SD Card (You may also mount External SD card and load ROMS from external SD card (I can recommend this))
It will take a while...
Reboot, and hope to god all is good.
I can confirm above works perfectly, I have flashed HD Revolution ROM successfully using above method.
BUT PLEASE BE WARNED: HD Revolution recommends using Super Wipe, the instructions are unclear, it says you must copy it to the your sd card, if you do this and copy it to your internal sd card all will be wiped including your images, I think you are screwed then. Rather copy them to your EXTERNAL SD card and choose zip from EXTERNAL SD card.
Or you can see a very clear example video of how to wipe data from your phone in preparation of a new rom;
Be aware, this video shows that you should UNLOCK your bootloader, some phones wont boot after this, don't do it except if you know you have to.
http://www.youtube.com/watch?v=EJUCOtX1cUk
Difficulty: Medium
--------------------------------------------------------------------------------------------
ALTERNATIVE Flashing - With Odin
--------------------------------------------------------------------------------------------
If you have not followed the wiping method and you will just be going for the stock updated rom, you should not be needing any wiping, you can just download the stock rom as linked and follow this great guide:
STOCK ROM:
http://forum.xda-developers.com/showthread.php?t=1646610
ODIN GUIDE
http://forum.xda-developers.com/showthread.php?t=1671969
Difficulty: Medium
--------------------------------------------------------------------------------------------
Restoring your data
--------------------------------------------------------------------------------------------
After you have are done with a successful flash, we want to recover our apps, but its not just a matter of recovering everything, it will be a mess if you do that.
Many people carry out a backup before installing a custom rom and didnt really understand what kind of backup they should of carried out and have just gone with what they have seen, WRONG!!! when it comes to custom roms there is only one type of backup you can do.
Custom roms have their own system files and dont like other system files being installed over it, you will definitely have rom problems if you carry out this kind of restore from a backup over a custom rom.
When using Titanium Backup its important not to use the settings - backup all system data and backup all user apps + system data, you cant use these with a custom rom, so dont try this kind of backup, this kind of backup is to restore your phone back to its previous state, should something go wrong with the rom installation.
Click to expand...
Click to collapse
Read more detail here:
http://checkrom.com/threads/titanium-backup-explained.433/
Difficulty: Easy
--------------------------------------------------------------------------------------------
Getting rid of bloatware
--------------------------------------------------------------------------------------------
If you went for a stock based ROM, you might want to get rid of all the SAMSUNG bloatware that sits in memory and really never gets used.
This is mostly all the "S" software like "S Suggest", I believe not a lot of people is going to use this for instance. And one can't simply uninstall it as it is hiden from uninstalling.
There is a very easy way if you are rooted though (another reason to root). Simply install the little greatness called "Nobloat Free" from the Play store.
Now select those bloatware you dont want and simply uninstall. But make sure it might not be useful for yourself. To give you an idea, "AllShare Play" might sound useless, however, if you have a XBMC media pc, by simply enabling "PNP" in the configuration, you can display photos and videos instantly from your G3, does not matter where you are in XBMC.
Difficulty: Very Easy
--------------------------------------------------------------------------------------------
Unrooting and getting back your Warranty!
--------------------------------------------------------------------------------------------
At some stage you might want to sell your phone or it is giving you hardware issues that has nothing to do with software. At this stage you want to reset the phone to it 100% factory state and status. It is completely possible, unfortunately it wont work to just update the rom to the stock factory rom as there are built in counters and status writes who flags the phone as modified. However, by following these tutorials, you can quickly reset your phone.
You will need the factory rom for your country, this can be downloaded here:
http://www.sammobile.com/firmware/
Then watch both of these tutorials and decide which one you feel the most comfortable with:
http://www.youtube.com/watch?v=ZEI_c1R0_nQ&feature=related
And another approach to regaining your warranty:
http://www.youtube.com/watch?v=TEsBwtqY2xE&feature=related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oops, if you are stuck on a crossroad and you think you might have bricked (term used to define the fact that you made your phone unusable) your phone, following this tutorial will help you out:
http://www.youtube.com/watch?v=ypmqJbZqOaU&feature=related
Difficulty: Easy
--------------------------------------------------------------------------------------------
Thanks to everyone
--------------------------------------------------------------------------------------------
I just want to say thanks to the wonderfully smart people who makes rooting possible. It is amazing how much more fun some people can make the life for other. I truly appreciate every bit of it.
Also special thanks to xdadevelopers who keeps an awesome community together.
Odin Greatness!
CF-Root
SuperSu
CWM
CWMManager
ClockworkMod (WTF, this is omg awesome!)
Titanium Backup
Adfree
--------------------------------------------------------------------------------------------
Congrats on your new firmare!
--------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
FAQ
--------------------------------------------------------------------------------------------
JiiNDER said:
Hey I want to thank you so much for your guide! It actually makes rooting a lot easier. I had one question though, if I root and a new official firmware comes out, can I still update to the latest stock rom with Kies even though I will lose my root.
Click to expand...
Click to collapse
It all depends what ROM you loaded, if its not the default factory ROM or based on it, you will have to follow the instructions of the CUSTOM rom provider on how an upgrade should be achieve. Else simply use the newest default rom and simply re-root, should be a very quick to do. Also, dont use KIES if you have already rooted, rather use ODIN and follow the instructions. NOTE: KIES, if left running will make ODIN behave incorrectly.
just a slight correction/heads up.... if you root with cf root then cwm recovery is installed, hence no need to use Rom manager, it's kinda outdated now imho
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
further to that you may want to provide instructions after the rooting process on how to get into recovery and download mode
slaphead20 said:
just a slight correction/heads up.... if you root with cf root then cwm recovery is installed, hence no need to use Rom manager, it's kinda outdated now imho
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
further to that you may want to provide instructions after the rooting process on how to get into recovery and download mode
Click to expand...
Click to collapse
Thanks, I will note that above.
The stock rom at the bottom goes to the international version rom. I found this thread in the Sprint version so u might want to note that. If someone were to flash that they wouldn't boot up.
Sent from Galaxy SIII
Added many corrections.
musclehead84 said:
The stock rom at the bottom goes to the international version rom. I found this thread in the Sprint version so u might want to note that. If someone were to flash that they wouldn't boot up.
Sent from Galaxy SIII
Click to expand...
Click to collapse
Could you please explain why you think it wont boot, what exactly would be different that wont make it boot. I believe it will?
Great tutorial for the noobs. Would be really useful for them. :thumbup:
Sent from my GT-I9300 using xda app-developers app
Stormlister said:
Could you please explain why you think it wont boot, what exactly would be different that wont make it boot. I believe it will?
Click to expand...
Click to collapse
Different CPU's, different kernels, different drivers, different partitions, different radios and tech (one being GSM the other being CDMA) and the list goes on...
graffixnyc said:
Different CPU's, different kernels, different drivers, different partitions, different radios and tech (one being GSM the other being CDMA) and the list goes on...
Click to expand...
Click to collapse
Thanks for the feedback man... will mark it as International Only.
I had question regarding Odin behaving strangely, make sure KIES is stopped in your services. I have added it in the tutorial.
Stormlister said:
I had question regarding Odin behaving strangely, make sure Kiss is stopped in your services. I have added it in the tutorial.
Click to expand...
Click to collapse
Do you mean Kies ? (Samsung) good tut for super noobs btw
Sent from my GT-I9300 using xda app-developers app
i would recommend you to recommend not installing Kies at all, or uninstall it if installed.
any backup that you can do with it, can be done by 3rd party apps. it has a lot of security issues. and worst, its slow as hell.
i think a person that want to root his phone and flash a custom rom, will have no need of it anyway.
Edit: thumbs up for the effort! i could have really used such guide when i just started, instead i learned it the hard way!
OverRipeBananas said:
Do you mean Kies ? (Samsung) good tut for super noobs btw
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yes, yes Kies, thanks for spotting it
Thanks, I'll try this soon! Glad I found this, voiding warranty still sounds scary. I have other rooted devices and sometimes they can blow me away, so I think I'll go for it anyway.
Cheers.
MrEdgar said:
Thanks, I'll try this soon! Glad I found this, voiding warranty still sounds scary. I have other rooted devices and sometimes they can blow me away, so I think I'll go for it anyway.
Cheers.
Click to expand...
Click to collapse
I personally think it is well worth-it, it is almost as if the phones turns into mini super computer when rooted. It is so much fun to have a ROM installed and setup that you are completely happy with, removing bloatware, no intrusive ads. Just stay away from overclocking, I think that is taking it too far if you are a scary pants like myself.
Also, you know how the retailers are, they almost never deliver on their warranty anyway.
No offence, but given this guide is designed 'for the ultimate noob' AND it has been stickied, there are some glaringly obvious things missing, that should be cover at the beginning of your post/guide before hitting the processes of
In the first post, you do not cover information pertaining to the flash counter and triangle away, and most importantly by far, BACKING UP THE EFS. Also, possible risks from installing potentially malicious apks from 'other sources' to a rooted device.
Sent from my GT-I9300 using xda app-developers app
Good job! :good:
bootx1 said:
No offence, but given this guide is designed 'for the ultimate noob' AND it has been stickied, there are some glaringly obvious things missing, that should be cover at the beginning of your post/guide before hitting the processes of
In the first post, you do not cover information pertaining to the flash counter and triangle away, and most importantly by far, BACKING UP THE EFS. Also, possible risks from installing potentially malicious apks from 'other sources' to a rooted device.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
None taken, but in a community it works like this. We build a tutorial together. Instead of taking the time pointing out what you think is missing. Why did you not just write the part so I could add it? This tutorial is based on the international version, I am not sure if the triangle notification does not affect this version but I could not test it as I did not ran into this problem.
Regarding the EFS, I will do some research regarding this and add it to the tutorial.
I have added detail on backing up EFS folder and also triangle away.
CF-Root 6.4 - SuperSU+CWM5.5+CWMManager does not work on stock JellyBean Firmware right?
Hello everybody
This is Siddharth from India. I am a mechanical engineer. I just purchased the Galaxy Note 2 a month back prior to this I always used an iPhone. I am new to the android platform and don't know how to flash, jailbreak or how to load different roms. I am very much tempted to install the moromoto00 theme on my phone but don't have a clue how to proceed. Frankly speaking it seems a lot more complicated than jailbreaking. Can anyone help me out??
Thanks in advance
Hello
I recommend you download and install the Note II Toolkit on your PC. You can find that here: http://forum.xda-developers.com/showthread.php?t=1923956
It makes flashing and rooting very simple, and everything is explained very well.
So the first step for you now is to root your phone, install CWM and then make a Nandroid backup. The toolkit will let you do all these things very easily. :good:
Those things are necessary to do first, then after that you can start flashing ROMs and themes!
Also recommended to backup your EFS before you start flashing things. Essentially, an EFS backup backs up your IMEI code in case something goes wrong you won't be left with a device with a faulty IMEI (that would be very bad). The toolkit lets you do this as well!
Just incase anyone with an Atrix 4G and 4.5.145 firmware, I followed the instructions in the following threads to successfully install Atrix-MROM on a brand new Atrix 4G ATT with the latest update.
1- Bootloader Unlock: http://forum.xda-developers.com/showthread.php?t=1182871
2- Root: http://forum.xda-developers.com/showthread.php?t=1769497
3- CWM Flash: http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot
4- Atrix-MROM Flash: http://www.montuori.net/android-mrom/atrix-mrom/
Thank you Michael Montuori, the Atrix-MROM is awesome.
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
ravilov said:
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
Click to expand...
Click to collapse
I think this is because, normally, they would need it to flash CWM. But it doesn't happen on Atrix. .
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
ravilov said:
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
Click to expand...
Click to collapse
This is my first smart phone, and I am absolute noob in this field.
I have been using Nokia 1216 and similar monochrome display phones before it.
In that case, I gues you're actually doing quite well really... If you came from mono dumbphones straight to this and have already flashed a custom ROM, that's actually kinda impressive.
Thanks!!!
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Glad it helped you.
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
aarizaga said:
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
Click to expand...
Click to collapse
It is in that thread. You can search: automatic_unlock_v4.2.zip
Or here it is:
h t t p s:// w w w . d r o p b o x . com/s/sr6ooho4zf9wqvo/automatic_unlock_v4.2.zip
Scan it first..
The MROM is simply amazing. Best battery life so far trying the cm7 based roms!
Sent from my MB860 using xda app-developers app
I am a neewbie, and when i learned how to flash custom roms, i was wondering, it is really necesary to root if you want a custom ROM?
now i was clarified.
So if want original firmware, and root acces, i just need an unlocked bootloader? And for rooting, can i just flash a fruitcake?
Sent from my MB860 using xda app-developers app
Hi, Thank you mmontuori for the excellent Rom and hard work to do it, and to Ravilov for the help.
I want to thanks in the post of the MROM in the development forum, but I can't do it because I don't have enough posts.
Well I finish yesterday to put all in order, only my contacts information I fail to restore.
The Go Backup didn't work.
One question, I don't installed the sv kernel, is necesary? because I feel that the battery it drain very quickly.
The rest appear so far to work very well, checking the holo launcher.
are you 100% sure everything on first post works with an ATRIX 4G 4.15.1455 from AT&T wiht the original motoblur?
i am newbee but wants to learn. its probably could i kill the phone?
thx!
Atrix 4g ATT 4.5.145 working well with CM 7.2
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Vengaence said:
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Click to expand...
Click to collapse
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Vengaence said:
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Click to expand...
Click to collapse
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
CWM versions for Atrix 4g
palmbeach05 said:
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Vengaence said:
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Click to expand...
Click to collapse
Ah, correct and incorrect my friend. While my signature may point out what device i am currently on, it does not reflect my past. A peice of supporting evidence is over in AtrICS v2.0 (see home button fix)
As far as cwm goes, cwm has unofficial builds as well. Look through one of the threads, it will point you to a link about recoveries and there does exist a 5.0.2.8. EDIT It was Romracer's recovery, accesed through the unlock bootloadrr thread a few threads down from this one. The 5.0.8.x i think was more like a 5.8.1.8, but i think that was a touch version? Now CM and the other threads may say the 5.x is ok for all of our roms, but as android moves forward, so must our support from libs, apps, kernels, scripts, and of course, recoveries. That is why i promoted the 6.0.4.6 revision both here and in the new 4.3.1 thread.
Sent from my MB886 using xda app-developers app
As I begin rooting process for my J710, and realize that the J710 is still fairly new so I thought I write this post and share my notes with everyone to help your transition goes smoothly.
First thing first, some safety tips.
Know your stock firmware. In this case SM-J710 is the min requirement
Have a stock firmware file downloaded on your PC. There's nothing for US right now, but J710 is not region lock so it matter not which version you chose on Sammobile
Make sure your current and new version match up as much as possible. So J710 should be the first 4 that need to match
Created a Folder on your PC for J710, and organize everything in one place. Samething with phone microSD card
Try to make a habbit out of keeping track of your process. It will help you out alot when things goes wrong and are looking for help. Or if you need to go back and see where you make mistake. Especially useful if you are new at this. Dev can't help you if you don't know what you did yourself.
10min rules. Always give the phone minimum 10 min to boot the first time before you disconnect the battery. Sometimes it just take longer, but 10min is a good start for first booth.
TOOLS you will need.
ODin newest is 3.10, but other version will be fine
Stock USB cable that came with the phone. This will save you the hassle of downloading USB installer, and it makes data transfer from ODin to phone alot safer.
TWRP for J710. right now it's only beta phase, but I beleive its 3.02.
Superuser zip files to be flash upon successful installation of TWRP
BACK UP DATA: With the app you can use ES explorer and back up to you microSD.
With the phone, just plug in to your computer, Copy the phone folder, and create a subfolder on your PC and name it System then paste everything onto that folder. After rooting is done. Re-install the app again, then copy your system folder onto the new system folder of your root phone. Restart your phone, and all your previous login and layout will there the way you left it.
Technically you only need to copy the ANDROID & BACKUP folder for your apps. But the above methods will back up all your media along with apps info, and it alot faster.
I recommend using ES explorer because it will does all the modification for without having to go through TWRP once you have rooted enable. Just enable root, and whatever you want to modify, place it in the correct folder of the phone SYS. Reboot and its done. You won't have to go through TWRP and risk bricking. You can save your modify rom in a zip file and share up here. It like being a developer for dummies.
So before you begin. The number 1 thing you should have is the firmware. SM-J710 from Sammobile. With that being said, I have found 2 links for rooting. They are both similiar process, but the one from XDA is for SM-J710F. and the link from Androidinfo is for SM-J710MN. Depend on your choosing you need to have a backup firmware from the method that you chose.
Now that you have the stockfirmware, and your phone is not the F or MN series. Flash the stock firmware of the method that you chose, and go with the rooting process for that method. here are the links:
XDA Video tutorial http://forum.xda-developers.com/galaxy-j7/how-to/video-root-samsung-galaxy-j7-sm-j710f-t3401790
XDA thread http://forum.xda-developers.com/galaxy-j7/development/recovery-samsung-galaxy-sm-j710f-t3380736
Androidinfotech: http://www.androidinfotech.com/2016/07/root-samsung-galaxy-j7-2016-sm-j710mn.html
This rooting method is working mostly with ODin, odds of you bricking your phone is about the same as winning a lottery. With that being said, make sure everything that you plan on flashing is from J710 and you should be fine.
The J7 is more like an opensource phone from Samsung. It does not have a lot of restriction like the other models such as S series. But you are working with a beta version of TWRP so it might not work out the first time around. If that is the case, flash a different firmware model or wait for a stable version. It not the end of the world if you phone is rooted.
Backtrack to beginning: Flash the stock firmware to begin the process again. WIPING DATA before any process is always a plus.
using ODin: Flash Firmware on "BL" for new version, i forgot which slot it is for the older version
Flash: TWRP and SU on "AP" slot for new version
INTERESTING FACTS: I ran across a thread online that mention backing firmware via Odin is possible. Hopefully someone here on XDA might have an idea on the methods, if such a thing exist. I thought I share this. If only I remember where I ran into that post.
Last notes: During the rooting process, I recommend letting the phone reboot completely as you progress through each phase of the process. the reason for this, is so it will help you identify if the TWRP is not installing, or the kernels is incorrect, or the SU.
Your phone will bootloop if TWRP does not optain write priviledges.
Your kernels will always install, but if TWRP does not have privileges the phone will not boot.
Should you were able to get TWRP, and Kernel to install properly, but fail to get SU to install. You gonna have to play around with other SU version. I would do a TWRP back up should I was able to get it to install, before moving on to SU. This way you won't have to start from the beginning if it doesn't work out.
With that, I leave the rest in your hand. Goodlucks
Vi3tDroidz said:
As I begin rooting process for my J710, and realize that the J710 is still fairly new so I thought I write this post and share my notes with everyone to help your transition goes smoothly.
First thing first, some safety tips.
Know your stock firmware. In this case SM-J710 is the min requirement
Have a stock firmware file downloaded on your PC. There's nothing for US right now, but J710 is not region lock so it matter not which version you chose on Sammobile
Make sure your current and new version match up as much as possible. So J710 should be the first 4 that need to match
Created a Folder on your PC for J710, and organize everything in one place. Samething with phone microSD card
Try to make a habbit out of keeping track of your process. It will help you out alot when things goes wrong and are looking for help. Or if you need to go back and see where you make mistake. Especially useful if you are new at this. Dev can't help you if you don't know what you did yourself.
10min rules. Always give the phone minimum 10 min to boot the first time before you disconnect the battery. Sometimes it just take longer, but 10min is a good start for first booth.
TOOLS you will need.
ODin newest is 3.10, but other version will be fine
Stock USB cable that came with the phone. This will save you the hassle of downloading USB installer, and it makes data transfer from ODin to phone alot safer.
TWRP for J710. right now it's only beta phase, but I beleive its 3.02.
Superuser zip files to be flash upon successful installation of TWRP
BACK UP DATA: With the app you can use ES explorer and back up to you microSD.
With the phone, just plug in to your computer, Copy the phone folder, and create a subfolder on your PC and name it System then paste everything onto that folder. After rooting is done. Re-install the app again, then copy your system folder onto the new system folder of your root phone. Restart your phone, and all your previous login and layout will there the way you left it.
Technically you only need to copy the ANDROID & BACKUP folder for your apps. But the above methods will back up all your media along with apps info, and it alot faster.
I recommend using ES explorer because it will does all the modification for without having to go through TWRP once you have rooted enable. Just enable root, and whatever you want to modify, place it in the correct folder of the phone SYS. Reboot and its done. You won't have to go through TWRP and risk bricking. You can save your modify rom in a zip file and share up here. It like being a developer for dummies.
So before you begin. The number 1 thing you should have is the firmware. SM-J710 from Sammobile. With that being said, I have found 2 links for rooting. They are both similiar process, but the one from XDA is for SM-J710F. and the link from Androidinfo is for SM-J710MN. Depend on your choosing you need to have a backup firmware from the method that you chose.
Now that you have the stockfirmware, and your phone is not the F or MN series. Flash the stock firmware of the method that you chose, and go with the rooting process for that method. here are the links:
XDA Video tutorial http://forum.xda-developers.com/galaxy-j7/how-to/video-root-samsung-galaxy-j7-sm-j710f-t3401790
XDA thread http://forum.xda-developers.com/galaxy-j7/development/recovery-samsung-galaxy-sm-j710f-t3380736
Androidinfotech: http://www.androidinfotech.com/2016/07/root-samsung-galaxy-j7-2016-sm-j710mn.html
This rooting method is working mostly with ODin, odds of you bricking your phone is about the same as winning a lottery. With that being said, make sure everything that you plan on flashing is from J710 and you should be fine.
The J7 is more like an opensource phone from Samsung. It does not have a lot of restriction like the other models such as S series. But you are working with a beta version of TWRP so it might not work out the first time around. If that is the case, flash a different firmware model or wait for a stable version. It not the end of the world if you phone is rooted.
Backtrack to beginning: Flash the stock firmware to begin the process again. WIPING DATA before any process is always a plus.
using ODin: Flash Firmware on "BL" for new version, i forgot which slot it is for the older version
Flash: TWRP and SU on "AP" slot for new version
INTERESTING FACTS: I ran across a thread online that mention backing firmware via Odin is possible. Hopefully someone here on XDA might have an idea on the methods, if such a thing exist. I thought I share this. If only I remember where I ran into that post.
Last notes: During the rooting process, I recommend letting the phone reboot completely as you progress through each phase of the process. the reason for this, is so it will help you identify if the TWRP is not installing, or the kernels is incorrect, or the SU.
Your phone will bootloop if TWRP does not optain write priviledges.
Your kernels will always install, but if TWRP does not have privileges the phone will not boot.
Should you were able to get TWRP, and Kernel to install properly, but fail to get SU to install. You gonna have to play around with other SU version. I would do a TWRP back up should I was able to get it to install, before moving on to SU. This way you won't have to start from the beginning if it doesn't work out.
With that, I leave the rest in your hand. Goodlucks
Click to expand...
Click to collapse
I Root the Device but After root there were many issues..... I Keep on getting an notification that unauthorized action ...
and also my device keeps lagging it lags just for a second but this games every 2-3 mins
I also freezed KNOX with lucky patcher but the problem still persists any meathod to solve the problem Thanks
Thanks
Sent from my SM-J710MN using Xparent BlueTapatalk 2
Hi everyone,
I tried to find a solid guide for fully backing up my system before doing anything to it to no avail. I'm currently on stock VNS-L21/VNS-L21C432B380/EMUI 5.0/Android 7.0 and plan to do the following:
1) Unlock bootloader
2) Root
3) Install Elite kernal and Arsenik rom
4) Probably some other modifications later on
I've already got some app from the store for application backup purposes but would like to have a firmware/rom/whatever backup of my current setup in order to safely restore in case anything goes wrong. I've done considerable amount of flashing with my other Android phones previously but any help would be appreciated.
Furthermore, perhaps it's worth to create a guide for this and sticky it to the top? I saw a lot of "help, bricked device" posts in this forum. I bet the guys with know-how are sick and tired of helping. Anyway, if you point me in the right direction I might as well create the guide for others.
Have a good one,
Renārs
Without root I don't think that I can make a backup . I can make apk file but not backup of data :/