Okay, so I tried to install Cyanogenmod to my Xperia S and well, I failed. I had flashed clockworkmod v1 since a long time ago and thought how it would go easily to just flash the Cyanogenmod, although, at first I got a message that looked like it was trying to tell me it was the wrong phone (the nozami version of cyanogenmod 9, which I'm quite sure was for Sony LT26) so I tried installing CWM 2, which was remarkably easy with RecoverX. Still got the same message though. So I later tried OpenSEMC-OTA-RC2. Got the same message this time, just that CWM this time said the ROM was for another phone. Both times though, it didn't say any real phone model or anything like that.
So after searching around on the page I found in the installation file that I should fastboot flash the boot.img into the phone and then do a regular flash. For this i used
Code:
fastboot flash boot boot.img
and restarted the phone as I needed to run to school. (Still came 5mins late though )
Continuing in school, my last step was to flash the zip file. This time I got no errors, but neither could I start my phone.
I've bricked the phone and well, I can get into fastboot, but nothing else, really. Not even the charging screen.
So my conclusion would be to run
Code:
fastboot flash recovery recovery-nozami.img
And redo the processes, but it says it needs root to do that, even tho, as I said, its already rooted. What can I do?
Also, the phone is unlocked since quite some time ago
How do I delete this reply?
Petomatick said:
I forgot to tell, the European phone in question is Xperia S, with unlocked bootloader and has been rooted since the day I got it, approximately a year ago.
Click to expand...
Click to collapse
Umm...next time on be a bit polite and someone will come to help you nicely. The developers who work on your phones do so for free and they have no obligation to provide the guides or their development works to you. Its upto you to read the guides or not to. If you would have searched properly then you would find only one guide for installing cwm on your device because xperia s doesnt have a separate recovery partition. you will find only one guide cwm 6.0.3.2 for xperia s by doomlord. Follow the instructions there and then flash the cm package using cwm recovery as per the instructions provided along with cm
Dark Wraith said:
Umm...next time on be a bit polite and someone will come to help you nicely. The developers who work on your phones do so for free and they have no obligation to provide the guides or their development works to you. Its upto you to read the guides or not to. If you would have searched properly then you would find only one guide for installing cwm on your device because xperia s doesnt have a separate recovery partition. you will find only one guide cwm 6.0.3.2 for xperia s by doomlord. Follow the instructions there and then flash the cm package using cwm recovery as per the instructions provided along with cm
Click to expand...
Click to collapse
You're right. I should've calmed down before I wrote the topic. Sorry community.
Also, the phone is from the European region.
Petomatick said:
Okay, so I tried to install Cyanogenmod to my Xperia S and well, I failed. I had flashed clockworkmod v1 since a long time ago and thought how it would go easily to just flash the Cyanogenmod, although, at first I got a message that looked like it was trying to tell me it was the wrong phone (the nozami version of cyanogenmod 9, which I'm quite sure was for Sony LT26) so I tried installing CWM 2, which was remarkably easy with RecoverX. Still got the same message though. So I later tried OpenSEMC-OTA-RC2. Got the same message this time, just that CWM this time said the ROM was for another phone. Both times though, it didn't say any real phone model or anything like that.
So after searching around on the page I found in the installation file that I should fastboot flash the boot.img into the phone and then do a regular flash. For this i used
Code:
fastboot flash boot boot.img
and restarted the phone as I needed to run to school. (Still came 5mins late though )
Continuing in school, my last step was to flash the zip file. This time I got no errors, but neither could I start my phone.
I've bricked the phone and well, I can get into fastboot, but nothing else, really. Not even the charging screen.
So my conclusion would be to run
Code:
fastboot flash recovery recovery-nozami.img
And redo the processes, but it says it needs root to do that, even tho, as I said, its already rooted. What can I do?
Also, the phone is unlocked since quite some time ago
Click to expand...
Click to collapse
Hi,
We do not use fastboot to install cwm or any recovery on the Xperia S as it doesn't have a recovery partition. Instead, the recovery is present in the ramdisk of the kernel. So flashing the boot.img installs cwm too. To get your phone working, please follow these steps -
1. Flash the rom's boot.img throught fastboot.
2. Enter Cwm.
3. Wipe data/factory reset,cache partition, advanced---> wipe dalvik cache
4. Flash the rom zip and reboot.
If your phone still refuses to boot then flash a stock firmware using Flashtool by Androxyde and start the procedure from step one again.
Good luck
abcdjdj
Sent from my LT26i using xda app-developers app
Thank you for your reply, but I cant flash anything. Its telling me the phone isn't rooted, but I know it is.
Related
Teamwin Recovery Project for A100 version 2.2.2.1 -godmachine81 release-
SOURCES: Available via Github
Download and Install via the official supported method by TWRP
Install Goo Manager app from Play Store, Open Goo Manager, In the Menu in top right corner go to "Install OpenRecovery Script" Follow Instructions On screen
Download Automated Installer (Windows / Linux):
Linux Installer - 2.2.2.1
Windows Installer - 2.2.2.1
Download IMG:
TWRP v2.2.2.1 main mirror
Download Flashable Zip: (Upgrade Only)
TWRP 2.2.2.1 Flashable Upgrade
Updated TWRP release features:
Uses a custom recovery kernel based off of my v1.5 standard kernel with most unneeded features taken out, i.e. governors, schedulers, networking, misc devices, and most things not needed for recovery operations
Kernel and TWRP includes patches aimed at brick prevention
Resolution is set at native 1024x600
Very fast actions and touch response
Backward compatibility with previous releases of TWRP
Compatibility with all Ice Cream Sandwhich and Jelly Bean ROMs for the A100(HoneyComb should be compatible too, however currently untested)
All previous features from TWRP that you may be familiar with are included
Mount Point Information:
External Storage - mountpoint= /external_sdcard
Internal Storage - mountpoint = /sdcard
Instructions:
Automated Installation (Windows/Linux):
Most importantly you need to have all drivers required for adb and fastboot working on your OS, this shouldn't be a concern for linux users, however it may be for Windows users as it is picky about adb drivers.
Download the above Automated Install .zip file for your operating system
Extract the contents of the Zip to a location on your PC's hard drive
Change to the extracted directory's contents.
Run the installer; On windows you may just double click the install-windows.bat file, on linux you need to run the install-linux.sh script
example linux installation commands:
Code:
cd a100_twrp_installer_linux
Code:
bash ./install-linux.sh
Read the on screen information of the progress. If you get any errors you will need to resolve the issue or try one of the following alternative install methods.
If you need more detailed installation instructions please read the INSTALL file included inside the .zip
Manual installation:
Download the .img file for the recovery
Connect your A100 device to USB on your PC
While your A100 is booted in either Android or Recovery just enter the following into your PCs command prompt/shell:
Code:
adb reboot bootloader
Now flash the image - at the command prompt/shell enter:
Code:
fastboot flash recovery openrecovery-twrp-2.2.2.1-a100.img
Reboot the device - again from the command prompt/shell:
Code:
fastboot reboot
Enter Recovery mode - While tablet shuts off, hold the Vol - (down) button until you see the screen saying "loading recovery kernel"
Checkout the new TWRP build and enjoy!
Flashable Upgrade Instructions: (flash just like you would any other .zip, but here are instructions anyway)
Download the Flashable ZIP above
Save to a location on your tablets internal or external memory
Boot to recovery
Choose the file a100_twrp_upgrade_2.2.2.1.zip in the install menu
Swipe to install
Wait and DO NOT Disconnect your A100!
When finished, go back to Main menu - choose Reboot - and Reboot Recovery
Enjoy the Official 2.2.2.1 TWRP Release!
If you would like to help out with the continuance of my kernel development and other goodies for your Acer Iconia Tab please consider a small donation to help out with bills, baby formula, wipes, diapers, etc. All donations are very appreciated by my family and I! Thanks
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
pio_masaki said:
.....I was gonna mention some things about your brick stuff, but I think I'll save it for off forum.
On topic: its about time we twrp users got some loving, thanks for taking the time to put this together for us!
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
And don't forget that i forgot the download link!! lol **fixed haha
Broken links, so you can correct it.
Fransis88 said:
Broken links, so you can correct it.
Click to expand...
Click to collapse
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
linuxsociety said:
Thanks francis88, i just tested them on my end again (btw the hosting server is remote from me) it worked for me, so maybe you should check if you have an adblocker or some kind of ipfilter going on? possibly the host was having issues too, but the links works for me at the moment. tested both github sources and the download link to the img. Thanks again
*Edit: Please keep in mind I am using androidfilehost's beta site and they are doing quiet a bit of changes to the site lately trying migrate users from the original site over to the new, and once they get everything settled in and the 'beta' goes away everything should straighten back up. I really like the services at 'androidfilehost' and the owner is really great at working with devs, so please be patient as they continue to upgrade their servers to bring us superb file hosting services. If a link appears to be broken, please wait a few minutes and try again, if the link is down for a long period of time please contact me in PM so that the thread stays for discussion about the TWRP Recovery. Sorry and thanks everyone
Click to expand...
Click to collapse
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Fransis88 said:
Perfect, i have been able to download it. i had a very bad experience with CWRP, now I only use TWRP apart from the fact that their options seem to me much more practical.
Click to expand...
Click to collapse
So let me know how you like it. Also if you happen to be a linux user, I have wrote an automated installer script for linux, Xbow59 is currently writing a windows batch script for installation, I currently have the Linux installation working though if you'd like to test/try it out just let me know. Windows users can look forward to an automated solution within a day or so
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
Click to expand...
Click to collapse
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
linuxsociety said:
By unlocking the bootloader successfully, what exactly did you do? If you flashed the btl100 file to the device that's not successfully unlocking, in fact don't touch that 100 file again. Hopefully you followed the guide and used the A200 bootloader unlock method. If you followed that guide though you wouldn't be getting the dead android looking guy. Be careful with this stuff, can easily brick!
Click to expand...
Click to collapse
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
nim.whit said:
help :/........ i am on stock rooted ics. i just unlocked the bootloader sucsessfully and went to flash this. flashed the recovery. and when i try to boot into recovery i get the dead android guy with an ! in a triangle above him......... should i flash recovery again or try to boot into recovery again? i just dont want to mess anything up.
edit: im just scared its trying to update a stock package. i had an update a couple days ago and tryed to update but it failed since i deleted a bunch of bloat, no problem. but i dont know where it downloaded and if its still there trying to install.
Click to expand...
Click to collapse
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
nim.whit said:
i used that method (only one i know) and i got the distotrted green acer logos and it says its unlocked. after i followed the steps to install twrp and it went smoothly. until i tryed booting into recovery. should i try to boot into recovery again? ive rebooted a few times so im still safe if i have to power off. OR should i try to reinstall twrp and follow the guide again. because i am CERTAIN i am unlocked. before i had to send in for repairs i had it unlocked but of course they relocked it.
(btw im not getting angry or smart assy with you haha,if it seems that way i dont mean it to come out that way)
Click to expand...
Click to collapse
yep what pio said:
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
I had forgot all about this, even though it is in my unreleased linux auto installer. If by chance you are using linux, I have an installer that will do this all for you the right way, I just haven't posted it yet because I don't have the windows installer fixed
you can either download the linux installer git repo and just extract it to a directory named twrp_install or similar; just run sudo bash ./install-linux.sh after you are in the install directory. https://github.com/godmachine81/Acer-A100-TWRP-Installer/zipball/linux <<current linux installer for a100 twrp
Or you can clone the repo
Code:
git clone https://github.com/godmachine81/Acer-A100-TWRP-Installer.git
then checkout the linux branch:
Code:
git checkout linux
then install:
Code:
sudo bash ./install-linux.sh
The git method requires you have git installed, you will probably just want to install from the zipball method if you don't already have git
pio_masaki said:
Delete or rename /system/etc/install-recovery.sh then install twrp again.
its overwriting your custom recovery every boot.
Tapatalked from my A100 - Jellytime X B6
Click to expand...
Click to collapse
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
nim.whit said:
aahhhhhh. thought it was something of that nature. now will i have to delete/rename and reflash twrp every time i need to flash something? or will it stick once i sucsesfully flash it?
will report if it works in a few seconds
edit: noobness showed there. haha thats a script to reinstall recovery at boot so once i delete it it wont reflash stock recovery right?
edit edit: nope, im not on linux (yet) my computer is a mess of three harddrives and messed up registrys and unofficial windows 7 haha. once i buy a copy of windows 7 its a full wipe and partitioning for a windows/linux dualboot
EDIT EDIT EDIT: SUCCESS now i flash linux's kernel
Thanks for the help you guys. once i get some money from the boss man i will gladly donate a little something something for the cause
Click to expand...
Click to collapse
Once that's removed or renamed it will stop, one time deal.
Tapatalked from my A100 - Jellytime X B6
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
linuxsociety said:
Also I noticed you mentioning that you are using a stock rom, you might want to talk to pio_masaki about this; but to my understanding the stock roms from Acer are not suppose to be flashed from custom recovery. I have read different things on this, however I haven't ever attempted to do such, from what I can tell doing this can or will brick your tablet by overwriting your bootloader and failing to install android, giving you no way to get to recovery nor android.. Might be something you want to discuss with him sometime.
Click to expand...
Click to collapse
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
pio_masaki said:
In your kernel thread he mentioned staying on stock for stability, so I don't think he'll be flashing off stock anyways. Not yet anyways....
Restoring stock works as it leaves the boot loader alone.
Tapatalked from my A100 - Kuroikaze B3
Click to expand...
Click to collapse
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
linuxsociety said:
Thanks, just trying to look out for these newcomers - however I'm still a bit confused at which causes the brick. The way I first interpreted it, it was flashing any Acer packaged update.zip from a custom recovery that would cause it. Then someone said that only the HC zips would. So to play it safe, I believe I'd double double check as many times as possible before I flashed any .zip from Acer from either twrp or cwm if it was me. Wish there was some clarity though on which Acer zips are SAFE and which ones are BRICKs -n- a Zip lol
Click to expand...
Click to collapse
The ics Acer zips are known brickers but it happens for a reason I'm not very clear on. HC will also brick it.
Basically there's a chance it will run the zip, attempt to flash everything, however for some reason it will fail to flash system or boot correctly, but does replace the bootloader. What I'm not clear on is why it fails on system or boot but succeeds on bootloader, or why recovery doesn't error flashing it.
Once this situation occurs you get locked out of both recovery and system by the bootloader, no adb or fastboot access to correct it.
Using the information I've gathered on this I've been working on a method to restore to stock if needed, but its going slow as I have to triple check everything before I even test it. Its a long and annoying process but should result in a 100% factory stock system.
Tapatalked from my Galaxy S II.
Installed and working perfectly!
Fransis88 said:
Installed and working perfectly!
Click to expand...
Click to collapse
Great Francis88, mind I ask which method of installation you chose?
Hello
I own Ouya for the month but most of time I use it as media-box for TV (watching movies, etc)
I have already rooted it and installed play market but i hate the stock UI and obsolate android
I saw a video in youtube with CM11 and ouya (android 4.4) and started to google the solution
I already know that it is based on Eternity Project kernel.
I found the way to install bootloader http://www.eternityproject.eu/topic/1114365-eternityproject-tpl-bootloader-for-ouya/ and it is clear
The next step is to install kernel http://www.eternityproject.eu/topic/1114362-eternityproject-kernel-3437-for-ouya-cpu-2ghz-gpu-650mhz/ but it is unclear for me about fastboot command
The next step as I understand is to install CM11 from the CWM
Is it possible to install KitKat without EP kernel?
So If someone have detailed steps or howto on installing CM11 on ouya please give it to this thread
Thanks in advance
I think this is what you're looking for. I'm not sure the EP boot loader is compatible but I'm sure its mentioned in the thread somewhere. Or in the bootmenu thread anyway.
http://forum.xda-developers.com/showthread.php?p=51332165
Sent from my Nexus 5 using XDA Premium 4 mobile app
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
quepaso said:
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
Click to expand...
Click to collapse
Can you put that in a bit more laymans desperate for a guide,you say wipe all stuff,do i backup my ouya in recovery first do i erase every thing and how please?
Sorry to be a pain [email protected] it up once and had to unbrick already spent 48hrs repairing my ouya and put a guide up on how on here,because nobody puts it laymans online for this.I downloaded all files ready to download folder mate.
PHYSC-1 said:
Can you put that in a bit more laymans desperate for a guide,you say wipe all stuff,do i backup my ouya in recovery first do i erase every thing and how please?
Sorry to be a pain [email protected] it up once and had to unbrick already spent 48hrs repairing my ouya and put a guide up on how on here,because nobody puts it laymans online for this.I downloaded all files ready to download folder mate.
Click to expand...
Click to collapse
Its hard to lay it out, you need to go to the threads where the info is already layed out.
Do you already have a custom recovery installed like clockwork? Great, then go to the failsafe thread to get a newer version of the recovery, and the failsafe installer. If you do not, you need to go to the custom recovery threads as there are multiple, and get any type of custom recovery installed. Then from there, install the newer custom recovery from the failsafe thread, then the failsafe itself from within the new custom recovery, then from there you can install cm11 using the cm11 thread following the instructions.
quepaso said:
Its hard to lay it out, you need to go to the threads where the info is already layed out.
Do you already have a custom recovery installed like clockwork? Great, then go to the failsafe thread to get a newer version of the recovery, and the failsafe installer. If you do not, you need to go to the custom recovery threads as there are multiple, and get any type of custom recovery installed. Then from there, install the newer custom recovery from the failsafe thread, then the failsafe itself from within the new custom recovery, then from there you can install cm11 using the cm11 thread following the instructions.
Click to expand...
Click to collapse
Just realized cwm is removed,can't install using oneclickrecovery tool either fails says cannot find img etcetc,yet its all there no problems adb is fine and works.Fastboot driver i can't get running although listed yellow exclamation,any ideas?
Fixed it managed to get fastboot going downloaded the required missing dll files and win_usb.inf set up and used ouyatoolbox 1.0.0.0 to rewrite recovery,found i can no longer add the newer 6.0.4.8 recovery zip in update from zip in 6.0.3.2 recovery though? Used to be able to do that. Any way tmore to the point is can someone tell me the step by step process to add cm11 firmware so i don't have to read a load of [email protected] that doesn't end up giving less than nothing in terms of having a clue how,someone in the thread writes about erasing stuff and what oreder but that doesn't tell you how to install or what erase process is or anything detailed and the net has exactly the same misguided tutorials on how to do it.Tellinng a newbie to erase stuff means they will erase all the wrong stuff in all fairness it's good to have a slightly better idea by reading that but it doesn't go in depth or step by step.
All i have found is sites pointing back to the xda pages that do not explain it,it's like your expected to know everything before you have been taught and fill in the gaps off the top of your head.
quepaso said:
This is the order you need to go:
Upgrade to newest clockwork mod from milaq in your recovery.
Then install the failsafe bootloader.
Then install cm11 from the new recovery, along with gapps he posted in the same thread Make sure to wipe all the stock stuff.
Thats it.
Click to expand...
Click to collapse
Exactly what he said, I just did these same steps on a 3rd new ouya yesterday and it went off without a hitch. The cm11 thread is long but honestly all the information you need is in the first few posts. If you were able to connect the ouya to USB and run oneclickroot then you're ready to get started.
I have looked all over and see some threads overlapping other threads, however I am not finding anything for the D5316 Model. I am running Android 4.4.2 Build Number 19.1.A.0.486 The kernel version is from Thu Jul 17 10:07:21 2014. I would like to root and get recovery on it to try a faster rom and get rid of the Sony bloatware. If you have been successful or I missed a link on how to do that please point me in the correct direction...... Thank you in advance.
Kinz1980 said:
I have looked all over and see some threads overlapping other threads, however I am not finding anything for the D5316 Model. I am running Android 4.4.2 Build Number 19.1.A.0.486 The kernel version is from Thu Jul 17 10:07:21 2014. I would like to root and get recovery on it to try a faster rom and get rid of the Sony bloatware. If you have been successful or I missed a link on how to do that please point me in the correct direction...... Thank you in advance.
Click to expand...
Click to collapse
you can try all root methods available i.e giefroot, rootkitxperia, easy root tool, etc. find them in the cross development section
Chena_22 said:
you can try all root methods available i.e giefroot, rootkitxperia, easy root tool, etc. find them in the cross development section
Click to expand...
Click to collapse
EDIT: Apparently, it's working now. All I had to do was reflash the ftf file in flashtool and it was able to keep the custom recovery and boot the phone past it....go figure.
Thanks for posting this, I am having some trouble myself and it's really frustrating. I am able to flash both CWM and TWRP. I am even able to boot into these recoveries but I cannot get the damn thing to boot past it. Pretty sure it's the kernel but I cannot find a place that will tell me step by step as to getting custom recovery on the model of this phone. I am still on 4.4.2. Can you please point me in the right direction?
bor3d2damax said:
EDIT: Apparently, it's working now. All I had to do was reflash the ftf file in flashtool and it was able to keep the custom recovery and boot the phone past it....go figure.
Thanks for posting this, I am having some trouble myself and it's really frustrating. I am able to flash both CWM and TWRP. I am even able to boot into these recoveries but I cannot get the damn thing to boot past it. Pretty sure it's the kernel but I cannot find a place that will tell me step by step as to getting custom recovery on the model of this phone. I am still on 4.4.2. Can you please point me in the right direction?
Click to expand...
Click to collapse
So you were able to root your d5316?
Kinz1980 said:
So you were able to root your d5316?
Click to expand...
Click to collapse
Yes I was! I can get you the instructions if you want.
bor3d2damax said:
Yes I was! I can get you the instructions if you want.
Click to expand...
Click to collapse
Yes, please do! Also did you get recovery figured out? I am wanting to use xposed.
Kinz1980 said:
Yes, please do! Also did you get recovery figured out? I am wanting to use xposed.
Click to expand...
Click to collapse
Yes,
Basically what you have to do is download Dual Recovery and put it on your SD card or internal storage on the phone. Download Supersu 2.40 and do the same thing. Then go to the CWM recovery thread and download that. Follow the instructions there. Once you finish following the instructions just boot into CWM recovery, then flash Dual Recovery. Reboot the phone and wait until you see the green light. Press the down key once you see the green light. It should take you into TWRP. After that flash Super Su and then you reboot and let it boot all the way, done. Make sure you are bootloader unlocked and have working ADB AND FASTBOOT on your PC
bor3d2damax said:
Yes,
Basically what you have to do is download Dual Recovery and put it on your SD card or internal storage on the phone. Download Supersu 2.40 and do the same thing. Then go to the CWM recovery thread and download that. Follow the instructions there. Once you finish following the instructions just boot into CWM recovery, then flash Dual Recovery. Reboot the phone and wait until you see the green light. Press the down key once you see the green light. It should take you into TWRP. After that flash Super Su and then you reboot and let it boot all the way, done. Make sure you are bootloader unlocked and have working ADB AND FASTBOOT on your PC
Click to expand...
Click to collapse
Let's back up for a second.....
Give me a breakdown one more time from the very beginning.
1.unlock the bootloader
2. Download "dual recovery"and place on sd card
3. Download superuser and place on sd card
4. Install cwm recovery
5. Flash the dual recovery.....why? Is there something wrong with cwm?
6.Flash superuser
At what point is the phone rooted? Does flashing SU do that? I have used tools in the past on other phones. This is my first Sony phone.
If you care to, or the time to...could you please paste the links to each step (assuming I have them all correct or I am not missing something)
I really appreciate you helping this much I was ready to give up on this phone, cause I couldn't get any help! :what::banghead:
just the topic I was looking for!
mind if I follow this? I just bought this phone yesterday. Looking for a way to get Lollipop on it.
I was hoping to get a reply by now. Which model# do you have
I just flashed FXP ASOP 2/23 after I was able to get 2/08 running on the device and now the device won't boot past the android logo. I can get it flashboot mode and rewrite the 3 imgs (boot, system, and user data) however it still won't boot.
Any Ideas?
hoonu said:
I just flashed FXP ASOP 2/23 after I was able to get 2/08 running on the device and now the device won't boot past the android logo. I can get it flashboot mode and rewrite the 3 imgs (boot, system, and user data) however it still won't boot.
Any Ideas?
Click to expand...
Click to collapse
I am just trying to get root and recovery
I was able to get root by doing the following.
Flash the cwm boot.img. You will not be able to boot android but you will be able to boot to recovery.
Flash the dual recovery from cwm. Go ahead and flash supersu zip as well.
Reboot. Wait till you see the green light (not pink) flash and press the volume down button to boot to twrp or volume up to boot phils recovery.
I used twrp. Once in TWRP, I flashed the rooted stock firmware (mainly to restore a fully working boot.img), and reflashed dual recovery from twrp. Also flash the newest supersu zip.
Maybe a easier way, but worked for me.
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Did you follow the instructions to flash TWRP using Odin?
olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear
bump
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?
N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.
N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post
aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.
Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.
swarby2 said:
Hi, so recently my HTC One X has been acting up so I decided to install a ROM to make it much faster, so I had to unlock the bootloader. When i've done that I flashed CWM on my device. Then I tried to install a rom that was on the device and it didn't install which leads me to my first problem, the page said I needed to reset everything and use the fastboot command to flash the zip file that worked but when I went to CWM (to install gapps) the device never booted in the ROM just kept going back to CWM. So I googled this and there was multiple things I tired out like adb command etc also it would be easier if this problem was fixed if this button worked (mount USB storage) I press that and it does not work. So then I don't know what to do. I'm stuck here please help me the rom was cm-11-20160815-NIGHTLY-endeavoru.zip.
Click to expand...
Click to collapse
CWM was abandoned a long time ago in the community so it won't cope with the instructions modern roms use. Its a bit sad that CWM came to a such sudden end I kind of miss the different recoveries based on it. Not to mention philz touch recovery..
Anyway go here: (its a twrp recovery) http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Read the instructions and flash the provided .img file and your phone should be up and running within the hour.
Edit: I'm not sure if that rom uses the new or old layout. The documenation is more than a bit poor because the device info is outdated on the cyanogenmod wiki. Last edited in year 2012..
https://wiki.cyanogenmod.org/w/Endeavoru_Info
If the rom will not flash with the new layout recovery provided above.
Read instrutions how to revert to old layout first. And flash this older recovery from here:
https://dl.twrp.me/endeavoru/
SÜPERUSER said:
CWM was abandoned a long time ago in the community so it won't cope with the instructions modern roms use. Its a bit sad that CWM came to a such sudden end I kind of miss the different recoveries based on it. Not to mention philz touch recovery..
Anyway go here: (its a twrp recovery) http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Read the instructions and flash the provided .img file and your phone should be up and running within the hour.
Edit: I'm not sure if that rom uses the new or old layout. The documenation is more than a bit poor because the device info is outdated on the cyanogenmod wiki. Last edited in year 2012..
https://wiki.cyanogenmod.org/w/Endeavoru_Info
If the rom will not flash with the new layout recovery provided above.
Read instrutions how to revert to old layout first. And flash this older recovery from here:
https://dl.twrp.me/endeavoru/
Click to expand...
Click to collapse
Really? Didn't realise that... Im trying to charge my phone because I can't flash it because the battery is too low. So thanks for telling me. I will post when Ive flashed it to my phone. When you flash it dosen't get rid of all the roms that's already on the phone? Because I cant access the phone within usb but does this recovery solve that? Like mount usb storage like in CWM?
swarby2 said:
Really? Didn't realise that... Im trying to charge my phone because I can't flash it because the battery is too low. So thanks for telling me. I will post when Ive flashed it to my phone. When you flash it dosen't get rid of all the roms that's already on the phone? Because I cant access the phone within usb but does this recovery solve that? Like mount usb storage like in CWM?
Click to expand...
Click to collapse
Flashing the recovery will not wipe anything except the recovery partition obviously. When you boot to twrp you will be able to access the internal storage by going to Mount and press the Mount usb storage twice. And the one x should be detected on your pc.
But when you're done with the backup you will wipe all partitions with the Format data option as described in the thread I linked yesterday. So backup all important data to your computer.
Thank you so much! I'm up and running!