This guide will enable you to easily root your phone in 6 steps. I've taken out the mystery and complications.
1) Go to HTC Dev site and manually unlock your bootloader. Select "register" and create your account.
1a) After you are registered select "all other supported models" in the pull down box
1b) Click "begin unlock bootloader". it will ask "are you sure" yes of course you are. acknowledge legal terms. then continue.
1c) Ignore the battery pull instructions as we can't pull the battery. hold down the power key and the volume down key until the bottom buttons stop flashing and your phone shuts off (don't worry if you take a screenshot. It happens all the time). then release ONLY THE POWER BUTTON. Keep holding the volume down key until the bootloader screen shows up.
1d) Follow "step 3" and the rest of the instructions as listed on the HTC site to unlock your bootloader manually.
2) Install android ADB/SDK on your pc. This video shows how to do it nicely:
2a) ****NEW UPDATED 03/05/13*** Alternatively if you DON'T want to install ADB/SDK you can just download the NON-FLASHABLE platform-tools.zip file located in my dropbox folder here.
Just extract this folder to your desktop using WINZIP or whatever archive tool you use and proceed to step 3.
3) Open a command line in your "platform-tools" folder by holding shift+right click anywhere within the folder and selecting the menu option "open a command window here". Then click here to install TWRP using fastboot. Follow the "Download - Fastboot Method:" instructions.
3a) If your phone isn't detected by windows please install the proper USB drivers for your operating system. Go here for 32bit. Go here for 64 bit.
4) Flash SuperSu and Busybox on your device:
4a) Click here and download the latest version of SuperSu. save it to your sdcard.
4b) Go to my dropbox and download Busybox 1.20.2 and save it to your sdcard.
5) Reboot into recovery (via the bootloader selection)
6) Flash the SuperSu zip and the Busybox zip listed in 4a and 4b
That's it!
"So now what?" you may be asking.
You are now free to flash ROMs that support s-on.
Two are my favorites are
(1) Stock with Goodies. (my personal favorite and the one I use today). This is a great ROM for beginners and people who prefer a slimmed down ROM (minus the bloat) and lots of free memory!
(2) Viper4G. This is a ROM for more experienced users and offers TONS of customization.
You can also run apps from Google play that required ROOT access!
If you're feeling slightly adventurous you can flash a custom kernel (which will allow you to overclock your phone). Two of the kernels I use are:
(1) ElementalX by flar2. Click here to take a trip over there. This one is especially important to flash as it seems HTC was up to shenanigans with the latest HBoot (2.09).
If you're unlucky enough to have HBoot 2.09 they have RESTRICTED access to your /system partition. What does this mean to you? It means that if any app writes to your /system partition (ROOTED or not) the phone will "panic" and reboot. Shady behavior if you ask me. The solution? Flash this kernel! it will give you write access so that everything works properly.
(2) The Arc-Reactor kernel! This one is for people that are s-off (see below for an explanation of s-off) only! It's the kernel I currently use and is the fastest kernel out there! Highly recommended if you decide to go s-off!!!
If and when you're feeling more adventurous you can go "s-off" (security off) which removes any security limitations of your phone. It makes flashing ROMs and updating firmware a lot easier. You can find out about s-off by taking a trip over to the DirtyRacun thread here. I will NOT walk you through this process. They will totally help you on their IRC channel. Just read post # 1 in that thread.
There's also a new method of s-off which literally takes 2 minutes. It's called facepalm and is located here But is NOT for the feint of heart, bad typers, nor people that cannot follow instructions! Why? One typo here and your phone is a brick. A paperweight. Useless. Well...you can recover...but that's not the purpose of this thread. If you DO brick your phone PM me. I'll help you out.
I take NO credit for any of this. It's all out there to learn I just put it all together. In one spot. Any questions feel free to PM me.
If I helped you out hit the THANKS button...or buy me a beer! Either way lol!
Tested and works with 3.16.651.3 (even if you took the OTA and have hboot 2.09 and are s-on)
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
lancemoreland said:
Did you use SuperSU or Superuser for root access? Either way could you please update the binary to see if it succeeds or if you get an instant reboot?
Click to expand...
Click to collapse
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
rawintellect said:
Everyone that is using supersu is experiencing that issue. The program itself will grant superuser access to your device. You don't need to open it. When you try and open it it will attempt to update the binary and then reboot the phone. You can ALWAYS reflash a new version of supersu when they update it.
To be clear: I'm up and running on my phone right now with superuser access. I'm fine unless I try to open the supersu program itself. Then I experience this issue you pointed out.
Click to expand...
Click to collapse
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
lancemoreland said:
I agree. I am up and running also but the new hboot locks the system partition and any app that tries to write to it will cause a reboot. Ad-free is another example.
Click to expand...
Click to collapse
Indeed this is a well documented problem but really not what this thread is about. Perhaps you can check out THIS thread where they are discussing this issue at length and hopefully they will come up with a solution for it?
http://forum.xda-developers.com/showthread.php?t=1538053
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
rawintellect said:
It also looks as though chainfire (the OP) is working on a fix if I read the last few posts correctly. and when he gets it I will update this post with it.
Click to expand...
Click to collapse
Yes I am participating in that thread. Chainfire is looking for a work around for his specific app, other apps that write to the system partition will no longer work. The point is that with Hboot 2.09 there are limitations and we will not enjoy full root as we have before when we were s-on.
Updated with an alternative superuser program.
SuperSU would ask to update binary and then just reboot. This fixed my problem for being able to access/deny and turn off messages. However it did not uninstall superSU will this cause a conflict having them both?
Edit: Okay I am dumb, I had to uninstall superSU first. Then I reflashed superuser to be able to have root privileges for my apps. When I just reflashed superuser hoping it would get ride of and superuser and keep root it did not.
Thanks it worked!
Help with rooting please.
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
MrSteez said:
So my phone was updated OTA without being rooted to 3.15.651.16 but now it is frozen. The touch screen will work temporarily upon a simulated battery pull and then freeze again only for me to simpull again and then it freeze again. I've gone into the bootloader and factory reset and wiped the cache but it's still messed up. So I think that maybe it's the software not installing correctly or something because this only started happening immediately after I download the new update.
I'm thinking about rooting my phone and even though I'm a pretty techy person this is new to me. I'm hoping that if I root my phone I can put it back to the stock software before the update and then just re-update OTA stock to the new update. I think that may fix it. Do y'all have any input it would be greatly appreciated as I have been dealing with this useless phone for over a week now.
Thanks.
Click to expand...
Click to collapse
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Updated thread with instructions on manually uninstalling supersu first before installing superuser 3.2
Thank you very much!
rawintellect said:
Well my suggestion is to go ahead and unlock your phone, flash a recovery and root it using my instructions. Then if you want BONE stock flash the odexed version of Jellybean that Viperboy has in his thread located here: http://forum.xda-developers.com/showthread.php?t=2045929
Why am I suggesting you do this? Because the OTA was very bugged. HTC is VERY slow with fixes. Developers can fix errors in the base errors usually faster than HTC. And most importantly when you are feeling like a change you can flash a custom zip at any time. The ONLY downside to unlocking and rooting is that you void your warranty with HTC, but NOT with sprint! Sprint will still honor a replacement phone when you RELOCK your phone and use the RUU (which isn't available yet but will be) to bring it back to stock. Your bootloader will say *RELOCKED* which lets them know you unlocked it but again they will honor a replacement.
Click to expand...
Click to collapse
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
MrSteez said:
Thanks I seriously appreciate it. I'm at work right now (I actually work at Sprint by the way which is why I'm not worried about having the phone replaced my tech will do it regardless) so I'm probably gonna look over your instructions carefully and then do this tomorrow. I'll let you know what happens I'm really hoping this will do it. It has to be some kind of serious installation bug in the new update because I never had this problem until literally minutes after updating.
And then after the completely stock RUU comes out (with no root or anything special) I can go back to completely locked and stock again? That's what I think I'd prefer but who knows I'm a Android and tech fanboy maybe I'll prefer the root.
Click to expand...
Click to collapse
yes. going back to stock is as simple as this:
(1) Boot your phone into the bootloader. make sure fastboot is selected. if you have the drivers installed correctly your phone will read "fastboot usb"
(2) if you followed my instructions on rooting you have ADB/SDK installed. so issue the command to relock your phone. type: fastboot oem lock
(3) run the RUU for 3.15.651.16. Done. Your bootloader will say *relocked* but it will be 100% stock.
Uh oh
I think i messed up. I did not see busy box installed and SuperSU is not updating.
The file listed in step 6 contains busybox. It also contains supersu. You want to flash the superuser file after flashing the file in step 6. It will overlay supersu with superuser 3.2. There is no need to update superuser 3.2 once you flashed it. It is the latest release.
Sent from my EVO using xda app-developers app
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
mobilecj said:
do i need to just flash the new superuser and it will fix the binary problema nd the titanium problem?
Click to expand...
Click to collapse
I replied to your email. But check my first post on the subject of superuser and how to uninstall supersu. if you need to that is. I tested this myself and it did uninstall supersu for me by just flashing superuser 3.2. Some people have reported this doesn't work for them.
okay sorry just got both i am going to try it now.. Its all knew to me it seemed like the information was explaining a dual process and i only had acquired one problem.. will post back in a few!
Hi, I'm trying to get my note rooted and I'm following this guide, but the link to the PDA.TAR file does not work.
Is there somewhere else that i can find a link to it?
DLXII said:
Hi, I'm trying to get my note rooted and I'm following this guide, but the link to the PDA.TAR file does not work.
Is there somewhere else that i can find a link to it?
Click to expand...
Click to collapse
I hope u had the issue resolved, but if in case you didn't you could always try this two steps (they've worked for me, so it's just a suggestion since it worked for me): the first time I rooted my phone I found a one-click root option, called kingo root (here's their website www.kingoapp.com) It's pretty self explanatory on their website but in a nutshell you just download the app online and it roots your phone. Another way (which I personally found very interesting and I found just by chance) was to flash a custom recovery (CWM or Philz, dunno about TWRP) and after cleaning cache/dalvik and/or wiping device chose to reboot. (Here is a thread from mooneyb with CWM Touch http://forum.xda-developers.com/showthread.php?t=2571424) Since you don't need root to flash a recovery since it's done through Odin, when you'll reboot you'll have an option that says that you may have lost root and if you want to fix it. My phone was unrooted at the time this option showed on my phone, and when I chose "yes" and my phone rebooted, SuperSU was working fine and so was Titanium Backup.
Maybe it'll work for you too, so hope this helps!
Whenever i try to reboot through CWM or flash something, an error always pops up informing me that my root access is possibly lost. It then asks if i want to fix it. I can either say "No" or say "Yes - Fix Root (/system/xbin/su)"
I have tried both options and have discovered that i cant flash anything. I have also checked and i have cobfirmed that /system/xbin/su is in fact on my phone. I dont know what to do. Also, my phone is an AT&T Galaxy S3 i-747 rooted with towelroot, stock ROM, stock kernel(which I hope to change right after this).
EddyTeddy01 said:
Whenever i try to reboot through CWM or flash something, an error always pops up informing me that my root access is possibly lost. It then asks if i want to fix it. I can either say "No" or say "Yes - Fix Root (/system/xbin/su)"
I have tried both options and have discovered that i cant flash anything. I have also checked and i have cobfirmed that /system/xbin/su is in fact on my phone. I dont know what to do. Also, my phone is an AT&T Galaxy S3 i-747 rooted with towelroot, stock ROM, stock kernel(which I hope to change right after this).
Click to expand...
Click to collapse
You need to post your question here >> http://forum.xda-developers.com/galaxy-s3-att <<
Hi there maybe you should rather try using twrp recovery(more features) and to try and fix your root look at the bottom of this page http://forum.xda-developers.com/asc...d-add-want-t2843511/post54729790#post54729790 (rooting is mostly universal)Bin4ry will probably work best with a samsung device also try the supersu flashable file
First of all, I apologise if I have posted this in the wrong section. Secondly, please be aware right now that the device in question is the S3 4G VERSION. Very different to the vanilla S3. I have dabled in rooting/flashing and general messing around with android firmwares before so I have a mild understanding but please be patient
Now the problem: Rooting. It shouldn't be hard. Should it? Not with tools like chainfires auto rooting kit these days... Alas, CF's auto root isn't doing it for me. At first I was having dramas with KNOX (congrats on loosing a long time customer there samsung). After i got rid of that with the de-samsungizer kit flashed through CWM it stopped showing the stupid "an application has attempted to gain root access and was blocked" crap. However SuperSu continued to crash, I'm assuming because the root was not properly completed. NO error codes or anything are ever returned from Odin, or CWM, everything looks like its happy but just not rooting. Confirmed with rootchecker.
Now a couple of other things I should mention: CWM keeps getting erased or something aswell? Like I'll turn the phone off to go into recovery mode, and im sitting at the bone stock one again, with the little red exclamation mark over my poor android corpse D:
I even tried disabling auto-reboot in ODIN when flashing CF's auto root, droppping the battery and manually starting recovery mode. I get excited when I see the red pirate-droid executing instructions, all goes well, everything is happy, still no root -_-
EDIT: In download mode, knox still exists and has logged EVERY attempt i've made. so everything is definitely executing just fine...
This is also my first time rooting in the presence of KNOX
I don't know what else to do... Am I missing something? is there a glaringly obvious thread or bit of information I've missed?
Thank you in advance for any help provided.
Ok so I took a break from this for a while cos i got really busy and didn't fancy doing MORE work on my phone when i finally got a spare tic. However, I came back to it today and managed to find a magic combination.
I AM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE, PLEASE FEEL FREE TO CRY IN A PM ABOUT IT THOUGH I COULD DO WITH A LAUGH.
The following is a guide for anyone having issues making the root stick on their GT-i9305 samsung galaxy s3 4G/LTE on android 4.3. DO NOT ATTEMPT THIS ON ANY OTHER OS VERSION, VARIANT OR DEVICE.
I noticed a particularly important piece of information in the following link: How to Fix Android 4.3 Jelly Bean Rooting Problem for Galaxy S3/S4/Note 2/3 - W0lfDroid
A superSu update. So i went there grabbed that package ( SuperSU Download for update package ) and started my grand master plan. If you would like to actually read what hte user said yourself, its in a quote bubble naer the bottom, just before the comments.
now. Using an important piece of information in a thread I cannot, for the life of me, find through my browser history (apologies) I grabbed a copy of pihlz touch which you can find in the following thread: [CWM][PhilZ Touch][GT-I9305] 4.00-b21 Touch … | Samsung Galaxy S III I9300, I9305 | XDA Forums
Now. grab yo-self a copy of busybox's supersu root How to root Galaxy S3 I9305 with SuperSU 1.02 - Samsung Update located on that page. Make a folder on both your phone's internal storage and external, name them both the same thing and something you will remember. For instanceI called mine Root stuff. I only do folders on each of them in case I can't extract from external for whatever reason, its not necessary. Put both the supersu update you downloaded earlier and the one you just downloaded from above, busyboxes root, into both of these folders if you did it my way.
To avoid having to reboot your phone an extra time, make sure you did the above step BEFORE moving on
First up, I flashed philz touch with Odin (ensure you have the latest version, use your PDA checkbox and be sure that auto reboot and F. reset time are checked). Next up, turn your phone off and boot into your magnificent (no seriously, this is amazing. Its like a GUI in todays BIOS's...) new CWM recovery mode. Go into advanced and hit reset permissions or something like that... My phone is downstairs atm and I CBF in going and getting it and rebooting. Note that I am unsure if this is actually an essential part of the process, this is something I did because I worried about the permissions on the phone after my, by KNOX's count, 15 attempted flash operations -_- More like freaking 20 thousand....
Now once you have done that, go back to the main menu and tap install zips. FIRST you select the actual root, supersu1.02 busybox. Next, select the extra zip file option and que the UPDATE supersu-v2.02 after the actual root package. Once you have done this, swipe to install. THESE TWO PACKAGES MUST BE IN ORDER!!!!
Thats all I did. My phone rebooted and I was able to use Root checker to conform the root, allowed access to supersu and no crashing. Finally. THat was way too hard.
Thank you for hosting the website gentlemen/ladies where we can all come and share knowledge.
all credits go to anyone/webpage I linked people to and the brilliant programmers that made the packages. And finally, a HUGE thanks to Google and Linux (from which android is based) for freeing us from the shackles of iOS.
Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
white5pirit said:
Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Mention 'EveryThing' about your phone. You can Take a screenshot of 'About Phone' and post it here.
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
white5pirit said:
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
Click to expand...
Click to collapse
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
hitman-xda said:
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
Click to expand...
Click to collapse
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
white5pirit said:
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
Click to expand...
Click to collapse
You could just press the 'thumbs up' instead writing 'thanks' everytime.
Well, why do you want to change the permissions of the folders? You could mess-up your device if you change permissions for the root folders.
The problem looks strange. If you have rooted successfully and GRANTED permissions for ES file explorer through SuperUser, you should not get any problem changing permissions. Check in SuperUser app that you see ES file explorer.
Also try using other explorer app. I use 'Solid Explorer' and its great.
If you have temporarily rooted your device as I mentioned in above post, try using TowelRoot app for rooting your device permanently and manually download SuperSU.
If you want to use CyanogenMod (it'll be pre-rooted) you need to carry below steps;
1. Unlock your Bootloader
(Wipes everything)
2. Install recovery.
3. Take stock ROM backup.
4. Flash ROM.zip
5. Flash GApps (optional)
6. Wipe cache+dalvic+factory reset
7. Reboot
Regards,
hitman-xda
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
white5pirit said:
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
Click to expand...
Click to collapse
If your bootloader status says
'unlock bootloader allowed = NO'
Then you can't flash anything on your phone. Almost every ROM needs an unlocked bootloader. There will be some ROMs that can be flashed over locked bootloader but they will be stock based.
EDIT: You have a good Luck, you can flash recovery on Locked bootloader
http://forum.xda-developers.com/xperia-m2/development/d2303-clockworkmod-6-0-4-6-t3011821
If you flash recovery successfully, that means you can flash ROM
Check below link for ROMs Available;
http://forum.xda-developers.com/xperia-m2/development
Regards,
hitman-xda
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
white5pirit said:
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
Click to expand...
Click to collapse
It can be a drivers issue. Install PC companion and connect your phone, let PCC install essential drivers and after that follow the same steps for installing recovery.
If you post any screenshot, that would be better.
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
white5pirit said:
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
Click to expand...
Click to collapse
Yup! Everything looks good. Just try to enter into recovery before downloading CM.
1.Switch off your phone and wait for 10 sec
2. switch on
3. When you see LED, try pressing either of vol buttons.
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
es0tericcha0s said:
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
Click to expand...
Click to collapse
Yeah you are right! Purely CM doesn't work on locked bootloader. But there must be any ROM available that is based on CM or even other ROMs that has some CM features.
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
es0tericcha0s said:
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
Click to expand...
Click to collapse
Z4 experience looks great ;
http://forum.xda-developers.com/xperia-m2/development/rom-z4-experience-locked-unlocked-bl-t3079811
Your xposed idea is great. Plus there must be GravityBox