I have built a CWM recovery image for the AT&T Fusion 2. If anybody would like to test it out, here is the link.
http://jenkins.cyanogenmod.com/job/recovery/18266/
Doesn't work:
Basically everything. You can only boot into CWM, and scroll using the Volume keys, but you can't select anything.
WiFi glitches on first reboot. To get WiFi working again, forget the connected WiFi network, and disable WiFi, then reboot.
NOTE: I have personally flashed this recovery image, and works, but FLASH AT YOUR OWN RISK. Enjoy! :cyclops:
Built second test build!
RoboticBuddy said:
I have built a CWM recovery image for the AT&T Fusion 2. If anybody would like to test it out, here is the link.
http://jenkins.cyanogenmod.com/job/recovery/18266/
NOTE: I have not personally flashed this recovery image as of now, so FLASH AT YOUR OWN RISK. Enjoy! :cyclops:
Click to expand...
Click to collapse
Flashed the img I am able to scroll up and down in CWM but not select anything. I went ahead and make a second build using recovery.img and the fstabs file. Still no more functionality, so I am searching for the graphics.c file and the postrecoveryboot.sh file.. I cannot find them.. YET
here is my version of the second build for the fusion 2 https://www.dropbox.com/s/r281aa12zko1brr/recovery.img try it with the installador tools from the fusion 1! (i will write a guide later..)
Anyone have any advice on how to find the files? I am guessing they are needed to get CWM working. This is my first build though, and any help will be GREATLY appreciated.
Just built my second build and third total for the fusion 2. The second worked fine, but not any better than the first. The third wouldn't boot into recovery. The third incorporated what I thought was the postrecoveryboot.sh
Shagerty said:
Flashed the img I am able to scroll up and down in CWM but not select anything. I went ahead and make a second build using recovery.img and the fstabs file. Still no more functionality, so I am searching for the graphics.c file and the postrecoveryboot.sh file.. I cannot find them.. YET
here is my version of the second build for the fusion 2 https://www.dropbox.com/s/r281aa12zko1brr/recovery.img try it with the installador tools from the fusion 1! (i will write a guide later..)
Anyone have any advice on how to find the files? I am guessing they are needed to get CWM working. This is my first build though, and any help will be GREATLY appreciated.
Just built my second build and third total for the fusion 2. The second worked fine, but not any better than the first. The third wouldn't boot into recovery. The third incorporated what I thought was the postrecoveryboot.sh
Click to expand...
Click to collapse
I have been searching for those files as well, but being new to this, I don't know what they are used for
And your own build of CWM, isn't it the same thing as mine?
And you can just flash it over to the phone using fastboot; "fastboot flash recovery recovery.img". . . .
RoboticBuddy said:
I have been searching for those files as well, but being new to this, I don't know what they are used for
And your own build of CWM, isn't it the same thing as mine?
And you can just flash it over to the phone using fastboot; "fastboot flash recovery recovery.img". . . .
Click to expand...
Click to collapse
In the second build I used the recovery.img and fstabs files. No more functionality. Third build I used the recovery.img and the fstabs and what I thought was the postrecoveryboot.sh. it wouldnt load on the third build.
I found a tool that pushes the recovery.img files with the click of a button.
Thanks guys!
Hey guys it's great that you two are working on a CWM recovery for this 'not very well known' device. I would love to help, if you need me to do anything just ask! My brother is getting into some more development with his device (Galaxy Player 4.2) and he might be able to help, I'm not a developer but I could start learning . Anyways, will you guys be able to build a CM10/JB for this device?
I am certainly shooting for it! But am in the same boat! I'm just getting into developing. Learning java code right now but I am just scratching the surface.. I would greatly appreciate your assistance as much or as little as you know the help is awesome! Like you said it is a little known device. We need all the help we can get!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
CenterTurkHD said:
Hey guys it's great that you two are working on a CWM recovery for this 'not very well known' device. I would love to help, if you need me to do anything just ask! My brother is getting into some more development with his device (Galaxy Player 4.2) and he might be able to help, I'm not a developer but I could start learning . Anyways, will you guys be able to build a CM10/JB for this device?
Click to expand...
Click to collapse
I'm too busy with school to start learning Android development, so I just can't really work on this device that often.
First of all, we need a working CWM before we can move on to ROM development.
Thanks for your future help!
Sounds great
Wow, sounds great guys! And I will keep completely up to date with this. I am also busy with school, but I do have time at home to do things with this [project]. I'll post and keep you guys updated if I can find or improve on anything!
Related
It shouldn't be that hard correct? I mean I downloaded rom manager and it flashed a DroidX recovery image to my phone successfully. But when I tried going to it it wouldn't bring me to the recovery image just the phone with the green triangle. So if someone just tweaked the DroidX recovery image I believe the Defy could have a simple and quick recovery image.
I'm no developer, but I doubt it would not be just a tweak.
From what I understand DroidX has a different security level than the Defy. In the Defy we will have to use bootstrap to get a recovery working for now, much like Milestone 2. I'm trying to get a recovery working on the Defy, but I haven't had much time this week, but yes, once recovery it's done making a nandroid backup image should be pretty easy .
If anyone else it's working in a recovery please let me know. At the time I'm looking at porting the open recovery to Defy.
pedrodh said:
From what I understand DroidX has a different security level than the Defy. In the Defy we will have to use bootstrap to get a recovery working for now, much like Milestone 2. I'm trying to get a recovery working on the Defy, but I haven't had much time this week, but yes, once recovery it's done making a nandroid backup image should be pretty easy .
If anyone else it's working in a recovery please let me know. At the time I'm looking at porting the open recovery to Defy.
Click to expand...
Click to collapse
Take a look here my friend: http://twitter.com/HandlerExploit
This guy is working on CustomRecovery and deblured ROM AFAIK..
Maybe he can help you or you can help him.. Whatever.. Help US
Thanks!
pedrodh said:
If anyone else it's working in a recovery please let me know. At the time I'm looking at porting the open recovery to Defy.
Click to expand...
Click to collapse
I have a Milestone with OpenRecovery. Remember that to get OR working in the first place, a Milestone user has to flash a recovery-only SBF that downgrades to a "vulnerable" version of stock recovery which allows non-Moto-signed .zip files to flash.
Is the Defy stock recovery vulnerable as well? If not, then OpenRecovery might be a dead end. Basically I think we've seen a number of different levels of security in terms of recover for Moto devices:
1) No security at all
The original Droid, as well as the Cliq/Dext and maybe others fall into this category. You can flash a non-Moto update.zip to gain root, and you can install a custom recovery with flash_image that will work.
2) Non-replaceable but vulnerable
The Milestone falls into this category. I think the locked bootloader will fail to work with a custom recovery. However the vulnerable stock recovery (version 2e) can be flashed by SBF onto any device with any version OS. The vulnerable recovery lets you branch out to custom recovery on SD via update.zip (e.g. OpenRecovery)
3) Non-replaceable, not vulnerable
The Droid 2, Droid X and possibly others fall into this category. You can't flash a non-Moto update.zip, and you can't replace it due to the locked bootloader. No signed SBF exists that will add a vulnerability to the recovery. Thus the bootstrap hack is the "next best option".
So the viable options for the Defy will depend on which security level it has.
I can't yet confirm this, but the Milestone 2 might have OpenRecovery, using bootstrap method. That means, whatever security Defy has, it will still be possible. But I'vent had time lately to start working on this. Once I do, I'll take a closer look on how things play out. Maybe HandlerExploit will find is way first than I do, if so, better for me
open recovery with bootstrap isnt a problem. since the defy doesnt have a camera key changes to the key mapping we need to adapt it to touch since the original stock recovery is touch as well... it should be out very soon. If anything it will be posted first on modmymobile (skirlax is the one who does all the open recovery)
Right, but I'm still wondering: is the Defy sufficiently locked down that the custom recovery *must* be a bootstrap? Or can we do better?
Sent from my Nexus One using XDA App
Isn't this the recovery image we need?
i can confirm the bootstrap is working great! using it right now.get fullly rooted,insecured boot.
Very good news !
tenfar said:
i can confirm the bootstrap is working great! using it right now.get fullly rooted,insecured boot.
Click to expand...
Click to collapse
Hey,
that sounds really interessting. Would you mind telling us more about the efforts you already made?
Are you talking about a bootstrap recovery method like we have one for the Droid X / Droid 2 ?
That would be GREAT!
Will the recovery image work on the Motorola Bravo when it comes out? The specs are practically identical except for the camera. Reason I ask is because there is practically no dev section for the Bravo. I've been able to root it and remove all the bloatware but would really like to be able to backup the phone.
Why is it people are still saying that we need a revcovery when one has been posted several weeks ago on another forum?
It's over at mod my mobile (I'm still not aloved to post links...)
pomah said:
Why is it people are still saying that we need a revcovery when one has been posted several weeks ago on another forum?
It's over at mod my mobile (I'm still not aloved to post links...)
Click to expand...
Click to collapse
I'm following just about every forum with a defy section, including modmymobile, and I am not seeing any custom recovery image. There are nuff theads telling you how to get into "recovery mode" but this is not what we need to be able to flash roms
Higgsy said:
I'm following just about every forum with a defy section, including modmymobile, and I am not seeing any custom recovery image. There are nuff theads telling you how to get into "recovery mode" but this is not what we need to be able to flash roms
Click to expand...
Click to collapse
I tried to make a recovery, but failed.
I managed to extract the original recovery and unpack with "unpack-bootimg.pl" from http://android-dls.com. But even if I do not change anything (kernel/img) and just repack it, I got a "Err:A5,69,35,00,2F" on recovery boot.
What I seen is that on defy we have no NAND flash (mtd) device, all is on 2Gb mmcblk(1) device.
In my opinion the recovery is signed....
Ok, I guess than that it's not the recovery posted in http://modmymobile.com/forums/639-m...motorola-defy-system-boot-recovery-dumps.html
Actually, the post there says it all: "I hope u can use them to create custom roms "
And what about the Rom Manager app?
Sent from my MB525 using XDA App
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?
NOTE: If anyone has any further questions about recoveries on the S3, please note that I have moved on to another device. Sorry!
So you've got your device rooted, and you want to install a custom recovery? Great! Don't just follow any guide you stumble across though, as some of the early recovery packages for the "AT&T" model were actually just copies of the custom Sprint recovery, and then you'll have all sorts of fun trying to install ROMs. ("Status 7" errors anyone? )
I'd like to talk about 4 ways to get the custom recovery of your choice onto your device.
Using mskip's Toolkit CWM [link]
Follow the instructions posted in his thread, and if you have any problems, direct them there as well!
Using ROM Manager CWM [link]
For some reason, ROM Manager doesn't always offer the correct list of devices to flash a recovery for and you won't see the SGS3 (AT&T) in the list. If that happens, force-close the app from Settings > Applications and try again. If this method just won't work for you, move on to option 4.
Using GooManager TWRP [link]
If you've been looking at ROMs, you may have noticed Goo.IM is a popular hosting website for Android developers. It's so popular, in fact, that they have produced an Android app that searches their website for updates for your ROM, and can even install TWRP with only a few simple clicks! Just open up GooManager, tap Menu, and tap "Install OpenRecoveryScript". You will be guided step-by-step from there by the app.
Note: Some people (myself included) have reported issues with this method, where the app claims to have installed the recovery, but when you reboot into recovery mode, nothing has changed. This issue may have been resolved in newer versions; I was able to successfully install TWRP using this method on Sept 26 2012.
Manually via ADB or Terminal Emulator CWM or TWRP [Terminal Emulator link]
If the other options just won't work for you, or if you would rather do an install by hand to ensure you're getting the latest version, read on...
Manually Installing a Recovery
While this may seem difficult, it's really not. Grab a recovery image (these files end in ".img") such as ClockWork Mod (CWM) or Team Win Recovery Project (TWRP) for your device. Most ROM developers say to use CWM, but they both work equally well.
In our case, we need an image for the Samsung Galaxy S3 AT&T. Telus, Rogers, Bell, and SaskTel phones are (almost*) the exact same phone as AT&T, if you have one of these devices, you will be installing the AT&T recovery.
Now, transfer the ".img" file you downloaded onto your device. I'd suggest somewhere with a nice short path, like "/sdcard/<file>.img" (you'll thank me later, especially if you're using terminal emulator on the device)
Now, let's back up your existing recovery. If things go wrong, you can use this backup to get back to where you started.
Code:
$ su
# dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery-backup.img
That should have created a "recovery-backup.img" on your phone's internal storage.
Here's the part you've been waiting for: Flashing the new image, which installs it as your recovery system. You do this from either an ADB shell or inside Terminal Emulator.
Code:
$ su
# dd if=/sdcard/[B]<file>[/B].img of=/dev/block/mmcblk0p18
You're done. Reboot into your new recovery by holding VolUp and Home while you power on your device.
If you need to return to the stock recovery, that IMG can be downloaded here: stock-recovery.img - 10.00 MB
*NOTE: While we're on the topic, let's take a second to talk about what makes the Canadian I747M different from the AT&T I747.
The short version is... The modem. AT&T is using completely different and incompatible modem firmware in their phones when compared with the Canadian models. Rogers, Bell, Telus, and any other Canadian I747M are the same device (Samsung worked some strange voodoo and got all the Canadian carriers to agree on the same hardware!) which means that if Rogers releases a new modem firmware update, a SaskTel user could install it without issue. AT&T modem updates will not work on Canadian models, nor will Canadian updates work on AT&T phones! I've tried it. Trust me. You don't want to deal with the hassle of fixing it.
Please remember to click/stick/lick/kick the "Thanks" button if you found this guide helpful!
How bout a 4th method for TWRP?
This should come in handy for some of the newer users
Well, the other TWRP method assumes that you already have a custom recovery installed to flash the ZIP from... If you've gotten that far already, I don't think you should need me to tell you how to flash a ZIP.
theres also GooManager from the market. its how I installed TWRP just download the app open it hit menu you'll see some options come up hit "install Open Recovery Script" it will ask if your sure hit ok and your done the whole process will take 30secs
Moved to General so new members can post questions
and stuck
FNM
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
Where'd you get it from? I'll add it to the OP.
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
tonymtl said:
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
There sure is! One of the benefits of manual installation is that you can find exactly what you want to use, and not rely on ROM Manager or other tools to make the decision for you!
Sent from my SAMSUNG-SGH-I747M
dstruct2k said:
Where'd you get it from? I'll add it to the OP.
Click to expand...
Click to collapse
+1. I am also looking for stock recovery...
Sent from my SAMSUNG-SGH-I747 using xda premium
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
nekkidtruth said:
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
Click to expand...
Click to collapse
That's a known issue with any recovery on the SGS3, it seems that the hardware clock cannot be accessed by the recovery no matter which recovery you use.
Did you happen to make a backup of your stock recovery? If so, I'd like to get a copy of it to add to the OP.
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
zmore said:
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
Click to expand...
Click to collapse
I could never get that to actually work in the past, so I guess I forgot about it. I just tested it now, and it worked fine, so I've updated the OP. Thanks!
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
See my Index for flash back to stock. There is a great vid tutorial.
PS dstruct2k I have added this thread to the INDEX. Nice work
Thanks, just flashed latest CWM Touch. External SD Card support rocks
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Then you're skipping a step, or typing something incorrectly. Once DD is done its work, you should get a response saying "Copied 10MB OK" or something similar. If it says that, then the stock recovery no longer exists.
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Please visit this post and follow from step 11-15. Shows kind of messed up on the XDA app so view it on your desktop. Very detailed guide for those who are confused. Thank you.
http://forum.xda-developers.com/showthread.php?t=1912335
Sent from my T&K Blessed SGH-I747
I followed those same steps but from a different thread and it still wasn't upgrading my clockwork recovery and kept getting status 7 when trying to flash cm10. Now I installed touch version hoping I would be able to get cm10 installed but still getting status 7. Any help appreciated
Sent from my SGH-I747M using xda app-developers app
Hi there,
Over the past few days I've been "messing" around with rooting my One X, starting with Cyanogen and then I was stupid and soft bricked it trying to put on a wrong ROM. I managed to sort all that out with a recovery and went back to Cyanogen.
I've just put Paranoid Android 3.10 on through the method that a youtube user "cursed4eva" followed which was the "standard" process as I was going from CM of which was just a "fastboot flash boot boot.img" in fastboot, then using recovery install the ROM and GApps from zip.
It's all working fine, apart from the WiFi won't turn on when you click the button in settings it flashes blue then back to grey.
Googling around it appears you have to repackage the ROM with a new Kernel (Seen XM 295 was meant to be good) So I have that downloaded but now I can't find any tutorials on how to go about actually repackaging the ROM for PA3.10 or XM295 with a One X.
Any help with getting this sorted or any other methods of getting my WiFi working would be great.
Thanks,
Tom.
You dont repack a rom......only repack the kernel. After that flash it. Google on nibble repack
Thanks for the reply,
my bad on the terms as mentioned I'm fairly new to the rooting of phones, Ok that site has finished,
Just to confirm, you use the new image file it's made, move that back into the PA zip file then do the normal process to install the ROM to the phone?
Ah i think you forgot to flash the boot.img from the rom.zip
The boot.img won't be flashed with the rom install. It needs to flashed via fastboot
Thanks for the reply,
First time around I flashed the boot image across I just wanted to ask if you move the "new boot.img" the website has made with the repackaged kernel into the paranoidandroid zip file or if you keep the standard one in there.
I'm aware I need to fastboot flash the new image across just not sure if it's also needed in the zip on the phone or not.
Ah no not needed
Thanks for all the help
Hi again.
It's all finished and the WiFi still doesn't want to turn on fully. To go with it Bluetooth also now doesn't want to turn on xD
Out of interest do you have any recomendations of kernels to use that can fix this issue?
Never used aosp roms. Check the thread OP. If the delivered boot.img won't work properly it should say something about in there.
It says repack with any aosp kernel. So repack the boot.img and flash the new boot.img, then flash the modules.zip via recovery of the kernel you repacked it with.
Did you try this one too ?
http://forum.xda-developers.com/showthread.php?t=2174855
Whilst trying to install the zip for that one it gets up to
"installing update..." then errors with:
"assert failed: getprop("ro bootloader") == "1.28.000" and repeats for the numbers from changing for 1.28, 1.31, 1.36 and 1.39.
I assume that is something to do with the bootloader rather than the rom?
on the bootloader screen all I can see is the HBOOT-1.72.000 etc. so not quite sure about that :/ that is with the 3.65 version on the link, attempting 3.99 now if all else fails will just go back to Cyanogen for now
Within the thread for the rom I was trying to start it didn't mention it, a few posts did which was met with repackage the kernel and that the XM 295 one worked for them.
Ah then you have to edit a file in the meta inf folder of the rom.zip.....hold on i for it somewhere
http://forum.xda-developers.com/showthread.php?t=2478409
Easiest is to remove for instance 1.39 and replace it with your bootloader version
Edit - Feel stupid, sorry didn't full read it xD HBOOT version is my bootloader.
Thanks once again.
Sorry for the double post but would just like to say a big thanks for all the help.
Phone is now running Paranoid Android 3.65 with working WiFi and signal So once again a big thanks
TrueSlawter said:
Sorry for the double post but would just like to say a big thanks for all the help.
Phone is now running Paranoid Android 3.65 with working WiFi and signal So once again a big thanks
Click to expand...
Click to collapse
Nice ! Good news then. Well enjoy
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.