i unlocked bootloader with teh asus unlock tool. I then rooted using the debugfsroot method found in the stickies. everything went well Or so i thought. After all rebooting was done i went into app folder and the superuser app was in there so i thought that i was rooted. Went to install twrp through goo manager and it said it couldn't get root permissions adn that i wasn't rooted. So i downloaded titanium backup to backup my apps and when i opened it it too said i wasn't rooted or that busybox wasn't downloaded. I downloaded busy box from the market and tried to install it and same thing....any one know what's up?
try rooting again with the same method and post what the cmd says after you are done with it~
lil-devil said:
try rooting again with the same method and post what the cmd says after you are done with it~
Click to expand...
Click to collapse
ok doing that now
here's what is says...
Installing Superuser.apk...
891 KB/s <843503 bytes in 0.924s>
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Rebooting...
Once your Prime reboots, it will be rooted!
Press any key to continue...
vballrkc said:
here's what is says...
Installing Superuser.apk...
891 KB/s <843503 bytes in 0.924s>
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Rebooting...
Once your Prime reboots, it will be rooted!
Press any key to continue...
Click to expand...
Click to collapse
UPDATE: After the second root now everything i described above is requesting superuser permissions so it appears all is well. If i have problems i will repost. Thank you for your response though i guess it just didn't stick the first time.
i'm glad that it works now
Hello,
i have a litle problem with the method above everything went ok .. i have root acces i think :'(
but the problem is that almost all applications started to crash, force close ro stoped running at all.
everything that was working before the root is broken somehow
any way to fix this ,???
i would suggest you to try unrooting with the root keeper app
if that doesn't work try reseting your tab via the pin hole under the SD card
if that still doesn't solve the problem default the tf201~
Ahem, OP, you do realize your bootloader is unlocked? That your warranty is void? That you no longer can receive otas? It's failing to push superuser.apk because it's already there. seems to me that you may need just to update su binary in superuser app. To start over, you need to uninstall Superuser app (if you can). If chainsdd su binary has been installed correctly with the right permissions, then you should be able to get root through adb, and then remount /system as rw, and remove Superuser.apk from /system/app.
Whats done its done. Stop wasting time. Check out the sticky for nvflash in the dev thread (read the whole thread, seriously) and get some nvflash goodness, better safe than sorry.
After that, continue to learn the ways of fastboot (if you use a toolkit, it's considerably harder to troubleshoot when things go wrong, to see where it failed, that's why you opened this thread, you don't know what went wrong), flash latest cwm or twrp through fastboot, flash a custom rom (after factory reset in cwm/twrp, naturally) with cwm/twrp, which will have root. and a whole lot more good things. if you don't want to go custom rom just yet and stick with modified (pre-rooted!) stock roms (made for unlocked bootloaders). all of this can be found in the dev thread, as you probably know.
If you're unlocked, the whole thing gets easier.
If you really want to stick with an (tweaked) asus stock rom, even unlocked, for some unknown-to-human-race reason, you may just download a superuser/supersu cwm/twrp (flashable) zip, copy it to the internal sdcard, boot a custom recovery (which also has root) through fastboot, flash that zip you copied before, and reboot system. you'll be rooted. an exploit is only needed when device is not unlocked.
# rant
# Damn, being unlocked/with a real safety net software wise feels GOOD!
sent from my tf201
bk201doesntexist said:
Ahem, OP, you do realize your bootloader is unlocked? That your warranty is void? That you no longer can receive otas? It's failing to push superuser.apk because it's already there. seems to me that you may need just to update su binary in superuser app. To start over, you need to uninstall Superuser app (if you can). If chainsdd su binary has been installed correctly with the right permissions, then you should be able to get root through adb, and then remount /system as rw, and remove Superuser.apk from /system/app.
Whats done its done. Stop wasting time. Check out the sticky for nvflash in the dev thread (read the whole thread, seriously) and get some nvflash goodness, better safe than sorry.
After that, continue to learn the ways of fastboot (if you use a toolkit, it's considerably harder to troubleshoot when things go wrong, to see where it failed, that's why you opened this thread, you don't know what went wrong), flash latest cwm or twrp through fastboot, flash a custom rom (after factory reset in cwm/twrp, naturally) with cwm/twrp, which will have root. and a whole lot more good things. if you don't want to go custom rom just yet and stick with modified (pre-rooted!) stock roms (made for unlocked bootloaders). all of this can be found in the dev thread, as you probably know.
If you're unlocked, the whole thing gets easier.
If you really want to stick with an (tweaked) asus stock rom, even unlocked, for some unknown-to-human-race reason, you may just download a superuser/supersu cwm/twrp (flashable) zip, copy it to the internal sdcard, boot a custom recovery (which also has root) through fastboot, flash that zip you copied before, and reboot system. you'll be rooted. an exploit is only needed when device is not unlocked.
# rant
# Damn, being unlocked/with a real safety net software wise feels GOOD!
sent from my tf201
Click to expand...
Click to collapse
So many things to respond to here, how about i just choose that if you would actually read the progression of this thread instead of just reading the first post and then skipping the next 9 posts and proceeding to rant to make yourself feel better then others, you would realize the problem has been fixed and all is good and that really none of what you wrote was A. relevant to my problem and B. helpful at all. Thanks. have a nice day.
vballrkc said:
So many things to respond to here, how about i just choose that if you would actually read the progression of this thread instead of just reading the first post and then skipping the next 9 posts and proceeding to rant to make yourself feel better then others, you would realize the problem has been fixed and all is good and that really none of what you wrote was A. relevant to my problem and B. helpful at all. Thanks. have a nice day.
Click to expand...
Click to collapse
I actually had good intentions, but now I don't freaking care what you think: Don't use sarcasm on me boy. BTW, no sarcasm here: You'll never learn anything if you keep using toolkits.
Related
Hello!
I did something really stupid. I rooted my Vibrant, and all was super easy and fine, but my home button was being unresponsive so without thinking enough did a reset on my phone. I wanted to make sure I covered my bases so I downloaded Titanium Backup and "backed up" all of the important things....call log, contacts, browser history, etc. etc. then did the master reset, but I don't think it worked. So now that I have done the reset it gives me force close messages on all of the main functions of the phone....dialer, web, you name it. Plus my home button still isn't working :/
So, the way I see it I have two options; risk sending the phone back to t-mobile under the guise of the home button issue....and maybe pay dearly for it (Superuser is still in the apps)
OR....
Hope and pray in the power of the XDA Gods, at least in order to get this to the workable category.
Thanks for any advice!
Are you able to get to the "Terminal Emulator" without it FCing?
You could boot into Clockwork Recovery and flash eugene's STOCK rom to see if that fixes anything.
hmmm, there's only the superuser and then the preinstalled apps. i did the one click root, so maybe that was missing the terminal app?
twag said:
hmmm, there's only the superuser and then the preinstalled apps. i did the one click root, so maybe that was missing the terminal app?
Click to expand...
Click to collapse
No its not missing, the "one click" just does rooting for you. You have go to into the market and download the application "Terminal emulator," if you're able to get that then you can unroot yourself and exchange your phone without T-Mobile ever finding out that you rooted. Or you could try flashing a stock ROM with Clockwork Recovery
got it! unfortunately though, every time i click market i get the force close :/ Meanwhile, I downloaded the clockwork recovery, but I'm definitely new to this, so where would I wanna go from there?
Thanks a lot by the way
twag said:
got it! unfortunately though, every time i click market i get the force close :/ Meanwhile, I downloaded the clockwork recovery, but I'm definitely new to this, so where would I wanna go from there?
Thanks a lot by the way
Click to expand...
Click to collapse
Get Terminal Emulator as well; where do you want to go from now? You want to try to troubleshoot this problem or just unroot the phone and exchange it
Edit: Figure ill just make it easier.
If you want to troubleshoot: http://forum.xda-developers.com/showpost.php?p=7329357&postcount=2 is what you're looking for. Follow those instructions and your problems will most likely go away.
To unroot
Code:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Also remove apps that require root access.
Either one will do the trick. I would go with troubleshooting, the directions are simple. If it doesn't work then.. unroot and make sure that all the bloatware is there + no root applications so they wont be able to tell.
Here dude. It seems you can not download terminal emulator from the market, so here it is with the root file for good measure. Only thing is I hope you have a way to download it and get it to your phone. Gl, and let me know if you need any more help.
Just making sure we're on the same page.....so you meant to install clockwork on my computer right?
My market FC's every time i try to go in there.
Any way that I can at least get this guy to fly in under the warranty inspection radar and be functional is the way I'm wanting to go. should i attempt to load the files from the clockwork program into my phone? Sorry I'm so fuzzy on this.
One click root and unroot here http://forum.xda-developers.com/showthread.php?t=746129
twag said:
Just making sure we're on the same page.....so you meant to install clockwork on my computer right?
My market FC's every time i try to go in there.
Any way that I can at least get this guy to fly in under the warranty inspection radar and be functional is the way I'm wanting to go. should i attempt to load the files from the clockwork program into my phone? Sorry I'm so fuzzy on this.
Click to expand...
Click to collapse
If you can follow directions good, this post should solve your problem. http://forum.xda-developers.com/showthread.php?t=747634&page=2
Hey bro, here is a simple fix.
Download ROM Manager which I attached below and install it. Within ROM Manager you will have a option to install Clockwork, so go ahead and install in through ROM Manager. ( Clockwork gets installed on your device ). Then follow this link http://forum.xda-developers.com/showthread.php?t=740077 to download a stock Vibrant Rom. Follow the instructions on how to install the ROM, and you should be good.
Forgot permission for "unknown" in superuser app
Ok, so I accidently tapped forget for the "unknown" in super permissions and now when I try to type su in adb shell it says access denied. Any help?
I ve tried about 4 imulaters none will open.then I thought I had found the aswers to one of my issues, getting terminal imulator to work. But after ive installation and reboot just for good measure. I get the message that I cant install apps connected to the market. Im thinking maybe I should try unrooting and resetting the imei. Is there another way?
if youre getting a lot of fc errors, then odin back to JFD. make sure to use the .pit and .tar files. you'll be on official stock. then you can root/ update to official. anyway, its never a bad idea to go back to complete stock after major errors.
I tried this emulater su removal thing but it said that none of those fials exist. I am clearly rooted with su. Could it have something to do with my 17 digit imei cant seem toswitch back?
No and you seem to be pretty clueless to what they are suggesting you do. The easiest way to fix most problems with FC. Are using Odin to flash the OS back to stock. Several guides in the bible. Look under android development for the vibrant bible.
Maybe I should elaborate my issues so I dont seem so clueless, I dont have sync! I have tried kies, and odin but does didly squat w/o sync.
I dont have market access or OTA support. I just got back terminal after about 15 tries.
So im basically try to see which I get first; unrooted or stock reset. All of which seem to have some OTA necesity unless I can find a complete APK or termina access deal. Yea im a noob to
If your going to do anything to your phone such as rooting you need to download odin. There is a tutorial in the dev section under the vibrant bibal. Odin will restore your phone back to stock like it was out of the box. There are plenty of ppl willing to help on these forums so if you run into problems just ask. Every time I thought I screwed up my phone odin has saved my life.
Sent from my SGH-T959 using XDA App
I've spend much of the day trying to root and then flash my new Optimus V. For some reason I keep running into snafus, even after rooting two Eris phones and a Nook color without too much difficulty. Would REALLY appreciate the group's assistance.
After much trial and error, I finally got root using SuperOneClick.
After that, I first tried to use adb to install the asop ROM per http://forum.xda-developers.com/showthread.php?t=962862 , but would always get stuck on the blue bootloader screen. By trying to fix that, I got stuck in a clockworkmod recovery loop. I finally got out of that by doing a flash_image of the stock ROM via adb. But then, the google market, and hence my google apps (including clockworkmod) was gone.
So now I'm stuck without access to clockwork mod, and a broken stock rom/interface (with no market access.) There may be a way to launch CWM even with the vashished google apps, but I'm not sure what it is...
Here is what I do have readily available in my "toolkit":
-root still working (via superoneclick);
-Root Explorer (having manually installed the Amazon marketplace apk);
-abd access to my 4g SD card;
-a backup 4g SD card, should one prove helpful.
My goal is pretty simple: to get a good custom rom (probably ASOP) with a fully functional suite of apps, and to MAKE SURE that the other corruption I've unwittingly done to my phone's data is complete eradicated.
I apologize for the jumbled nature of this post. I'm sure I'm leaving some diagnostic stuff out that would be useful--please fire away and I'll be more than patient about trying to clarify.
THANK YOU in advance for any help you can offer!
polphi said:
I've spend much of the day trying to root and then flash my new Optimus V. For some reason I keep running into snafus, even after rooting two Eris phones and a Nook color without too much difficulty. Would REALLY appreciate the group's assistance.
After much trial and error, I finally got root using SuperOneClick.
After that, I first tried to use adb to install the asop ROM per http://forum.xda-developers.com/showthread.php?t=962862 , but would always get stuck on the blue bootloader screen. By trying to fix that, I got stuck in a clockworkmod recovery loop. I finally got out of that by doing a flash_image of the stock ROM via adb. But then, the google market, and hence my google apps (including clockworkmod) was gone.
So now I'm stuck without access to clockwork mod, and a broken stock rom/interface (with no market access.) There may be a way to launch CWM even with the vashished google apps, but I'm not sure what it is...
Here is what I do have readily available in my "toolkit":
-root still working (via superoneclick);
-Root Explorer (having manually installed the Amazon marketplace apk);
-abd access to my 4g SD card;
-a backup 4g SD card, should one prove helpful.
My goal is pretty simple: to get a good custom rom (probably ASOP) with a fully functional suite of apps, and to MAKE SURE that the other corruption I've unwittingly done to my phone's data is complete eradicated.
I apologize for the jumbled nature of this post. I'm sure I'm leaving some diagnostic stuff out that would be useful--please fire away and I'll be more than patient about trying to clarify.
THANK YOU in advance for any help you can offer!
Click to expand...
Click to collapse
Boy, First of all don't panic. Without bricking you can't learn.
Second for Root you can use Gingerbreak. This should work. http://forum.xda-developers.com/showthread.php?t=1044765
for Flashing on all use custom recovery tool. And its like one two three from your phone only using terminal apps. Here is the guidehttp://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
After entering in Custom recovery mode you can do what ever you want to do. Flash rom as per your desire.
have you flashed clockworkmod recovery before?? if yes access it using the three button combo....you can flash any rom you want from recovery....
hit the thanks button if i have helped you.
sajjan said:
have you flashed clockworkmod recovery before?? if yes access it using the three button combo...
Click to expand...
Click to collapse
Alas, after restoring the stock, the three button combo brings up not clockworkmod, but "Android system recovery <3e>", which *only* allows:
reboot
apply sdcard update.zip
wipe data/factory reset
wipe cache partition
Since I don't have an update.zip file that works, I can't seem to get beyond this. When I tried renaming a custom rom recovery file update.zip, I got a signature mismatch, which makes sense.
First, thanks to both sweetbinodray and sajjan for the replies.
sweetbinodray said:
Boy, First of all don't panic. Without bricking you can't learn.
Click to expand...
Click to collapse
Hehe, that's similar to what I keep trying to tell myself.
Second for Root you can use Gingerbreak. This should work.
Click to expand...
Click to collapse
I have root, even have root explorer working via Amazon mktplace. (I shouldn't need or want to re-root, should I?)
for Flashing on all use custom recovery tool. And its like one two three from your phone only using terminal apps. Here is the guidehttp://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
After entering in Custom recovery mode you can do what ever you want to do. Flash rom as per your desire.
Click to expand...
Click to collapse
When I follow that guide, I'm linked to an updated thread which asks me to enter shell (no problem) then use the following command as first in a series:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
that results in "mount: operation not permitted".
Basically, having (regrettably) tried to to start from scratch by reflashing stock, I keep running into these permission snags.
Seems like if I could get to the CWM recovery screen, or figure out a way to trick the stock recovery screen into accepting a different update.zip, I'd be OK.
Then again, perhaps that's making things too complicated?
TIA once again!
Also, this looks like it might work, but I can't seem to get the validation email necessary to validate a board membership, which appears necessary to download the Quick Boot file.
polphi said:
First, thanks to both sweetbinodray and sajjan for the replies.
Hehe, that's similar to what I keep trying to tell myself.
I have root, even have root explorer working via Amazon mktplace. (I shouldn't need or want to re-root, should I?)
When I follow that guide, I'm linked to an updated thread which asks me to enter shell (no problem) then use the following command as first in a series:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
that results in "mount: operation not permitted".
Basically, having (regrettably) tried to to start from scratch by reflashing stock, I keep running into these permission snags.
Seems like if I could get to the CWM recovery screen, or figure out a way to trick the stock recovery screen into accepting a different update.zip, I'd be OK.
Then again, perhaps that's making things too complicated?
TIA once again!
Click to expand...
Click to collapse
Ok what i can suggest you is do manual set up for custom recovery using terminal apps. Here is the guide http://forum.xda-developers.com/showthread.php?p=15185778#post15185778 and start form install terminal emulator. And write following commands.. its like one to three....
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!
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
upndwn4par said:
Never flash an SBF unless you have no other choice. Major hard brick risk.
In this section I have a stickied thread with the answers you need.
If your bootloader is still unlocked and you still have a custom recovery installed, flashing a fruit cake should work fine.
Click to expand...
Click to collapse
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
I just sold mine but will look in PC history. My matrix was stock 4.5.145 and I rooted it. I remember failing a few methods till I found one that worked. If I figure out what I did I will post it for you. If not fruitcake is best way
KetoSoi said:
At this point, I dont have much choice. Unless some one figures out what motorola/att did with 145 to completely screw root (its beyond my abilities), I need to press forward. If I brick it, I brick it. I'll use your sticky as my guide then, seems reliable.
Bootloader is unlocked, though I've never installed a 'custom recovery'. Looks like the various fruitcakes links are unavailable for download?
What is the advantage of the fruitcake version over the version I posted?
Thanks for the guidance
K
Click to expand...
Click to collapse
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
upndwn4par said:
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
Understood, thanks for the explanation.
UnlockRoot couldnt gain root access
I will attempt your suggestions Thanks very much for the guidance, its invaluable
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
KetoSoi said:
Unless some one figures out what motorola/att did with 145 to completely screw root ...
Click to expand...
Click to collapse
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
upndwn4par said:
Let me know how things go with the above before you even consider this.
Click to expand...
Click to collapse
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
ravilov said:
From what I hear, the only thing that Moto "screwed up" (I wouldn't really call it that) is that on .145 they filled up /system. That is actually trivial to resolve - delete a few apps from /system/app that you don't need/want (you can install them later if you want to, some can live happily on /data) and - this is crucial - wipe /preinstall, since that is what fills up /system. If you don't wipe /preinstall, just deleting apps from /system will only last until next boot. Or, well, you don't need to wipe /preinstall, you can just flash the rooting preinstall image.
Click to expand...
Click to collapse
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
KetoSoi said:
I tried several variations of what youre refering to, however it was to no avail.
I went as far as to delete several useless items (apps) out of the dir, the free space indicated never changed. The amount I removed was more that enough copy su in... yet, it always reports not enough space.
I tried an experiment. I renamed the 'fake' su (always zero bytes) in the bin dir to 'su.old'. Within 30 seconds, *something* renamed it back to 'su', happened right in front of my eyes in Root Explorer.
When you say 'wipe preinstall', specifically you mean?
Click to expand...
Click to collapse
Wow, that's just bizarre. Not sure what to think here.
I meant something like
Code:
moto-fastboot erase preinstall
KetoSoi said:
I was able to flash CWM Recovery no problem. I was able to flash your superuser zip as well, however it did not root the system. All indicators showed it as being successful, but ultimately it was a no-go.
At that point I flashed your fruitcake 141 images, good to go there. I then applied the preinstall method, and viola, rooted again.
I am good to go, thanks to your knowledge and skills Thank you!
Now, all I have to do is email a scan of my middle finger to motorola/att.... lol
Click to expand...
Click to collapse
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
upndwn4par said:
Awesome!
I really don't understand why the superuser zip did not give you root access.
Moreover, I don't understand why some users seem to be able to root 145.
I guess I shouldn't be surprised since this device has always been a PITA.
Click to expand...
Click to collapse
Very odd some cannot root. I was on permalocked bootloader and still rooted after soak
Its sad, because the 145 update seemed like it made the phone a little snappier, and the screen was a pinch smoother.
What do you guys think about applying the CWM Zip for update 4.5.145 in my situation? Would that be safer?
Uh oh.... you guys ran away! LOL
I was able to flash the 145 update via CWM from NYG-SBXLII's handy zip file
No real problems, 145 running fine WITH root intact. Awesome
Had to blow away the recovery-from-boot.p file afterwards, and re-flash CWM Recovery, but it was all good.
Updated SU and bin's, good to go.
affiatic said:
http://forum.xda-developers.com/showthread.php?t=1769497.
I am pretty sure this is the method I used to root 4.5.145 before I sold it
Click to expand...
Click to collapse
This worked for me too with 4.5.145, followed it exactly and had no problems. Thanks!
KetoSoi said:
Well, I've pretty much had it with this latest update (ATT, 4.5.145). I'd like to go back to .141 as its easily rootable. My Atrix is boot unlocked, and I have no interest in the custom ROMs. I dont have squat on the phone I need to keep, so I can blow the whole thing away as needed. I have the latest USB drivers and RSDlite ready to go.
I located the following ROM, and downloaded it... "1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf", appears to be the correct one.
I've been reading and reading and reading on the forums here (i.e. I've searched a lot), but theres a lot of cross-info, its hard to tell whats applicable in some situations.
So the question....
Which HowTo/Method/Guide would be most appropriate for my situation? Or is there something that would prevent this back-rev?
Thanks for any help or suggestions.
K
Click to expand...
Click to collapse
How did you unlock the bootloader for firmware 4.5.145? I've been looking everywhere on how to do it safely!
upndwn4par said:
The difference between what you posted (an SBF) and what I suggest (a fruit cake) is that an SBF is full stock firmware (bootloader, boot, system, radio, etc). It is the bootloader that causes the problems. Flashing an SBF is a crap shoot. You might do it 10 times without a problem, and the 11th time you hard brick your device. By hard brick I mean hard brick = your device is now a paperweight.
A fruitcake is essentially the same as a custom ROM. You are only flashing the boot and system images. This is always the best option for returning to stock.
However, you are in a different situation - uncharted waters so to speak. No one knows what to expect from 145. And since you don't have a custom recovery installed (CWM, TWRP, etc.) you can't just flash a fruit cake like you would flash a ROM. You should be able to use the fastboot method to flash the fruit cake, but again...uncharted waters.
I suggest trying the following in this order based on your current situation (options 1 and 2 assume you do in fact have an unlocked bootloader):
1) Fastboot flash a custom recovery, then try to flash the zip I posted on my rooting guide thread. If this works you will have rooted 145.
2) Fastboot flash a custom recovery, then flash the 141 fruit cake I made.
3) Fastboot flash the boot and system fruitcake images.
All the files and info you need can be found on my "Answers" thread and my rooting guide.
Do not flash an SBF until all else has failed. Let me know how things go with the above before you even consider this.
Edit:
Before you try any of the above, did you try UnlockRoot? It may work.
Click to expand...
Click to collapse
hello, ive been using 4.5.145 and was unable to root it, the problem with mine is that when I try to use the preinstall method it chokes when i type the "cp /preinstall/su /system/bin/... there was a message cp write error: no space left on device.. I have tried everything (almost) to root it but was unlucky.. then i saw this thread http://forum.xda-developers.com/showthread.php?t=2153422 ... i wanna try your suggestion but cant find the zip file in suggestion 1 and the 141 fruitcake you made on suggestion 2 and cant find file on option 3.. please do help me.. I have unlocked bootloader and have rom racers cwm.. thank you and more power..
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