[Howto] Install a Recovery

Search This thread

Sykotyk

Member
Jun 15, 2013
14
3
Toronto
I'd hate to bug you all but am at work and searching forums while boss is out of office. Tried flashing rom but failed (assuming because the rom is d2att and im d2can and i have to delete the check it preforms in the beginning) getting fail /status 7 it says assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att" e:Error in /sdcard/aokp_d2att_nightly_2013-06-15.zip . Trying to restore nandroid and is failed while restoring /data. I made two backups and they are both doing the same thing. Can i restore in advance and install everything except data? FML
 

dstruct2k

Senior Member
Jan 31, 2008
1,253
938
Winnipeg
Google Pixel 4
I'd hate to bug you all but am at work and searching forums while boss is out of office. Tried flashing rom but failed (assuming because the rom is d2att and im d2can and i have to delete the check it preforms in the beginning) getting fail /status 7 it says assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att" e:Error in /sdcard/aokp_d2att_nightly_2013-06-15.zip . Trying to restore nandroid and is failed while restoring /data. I made two backups and they are both doing the same thing. Can i restore in advance and install everything except data? FML
Status 7 never means you should edit the ROM; You should figure out why the recovery is refusing the ROM in the first place.

I'd suggest rebooting into recovery, formatting /data, rebooting into recovery again, and trying to restore a backup. If you're running TWRP, there's a d2can version that will cause assert/status 7 errors because it doesn't match the expected d2att properties. Make sure you're on the newest d2att recovery and try flashing again.
 

laposted

New member
Jun 20, 2013
3
0
Need some help please

Hello everybody,

I am a beginner in the cell phones' field and I need some help please. I lately rooted my device (which is a Samsung Galaxy S3 Mini GT-I8190N 4.1.2) and I am currently trying to install a recovery. I downloaded Goomanager but I when I run it and hit Menu to select Install OpenRecovery, I get "no recoveries were found for your device".

Could you please tell what to do in this situation?

Thank you
 

dstruct2k

Senior Member
Jan 31, 2008
1,253
938
Winnipeg
Google Pixel 4
Hello everybody,

I am a beginner in the cell phones' field and I need some help please. I lately rooted my device (which is a Samsung Galaxy S3 Mini GT-I8190N 4.1.2) and I am currently trying to install a recovery. I downloaded Goomanager but I when I run it and hit Menu to select Install OpenRecovery, I get "no recoveries were found for your device".

Could you please tell what to do in this situation?

Thank you
I'd suggest checking out the subforum for your device, located here: [link]

TWRP for your device is here: [link]

I'm not able to help much more than that because we have completely different devices.
 

laposted

New member
Jun 20, 2013
3
0
Thank you

Thank you, I will have a look and I hope I will find the explanations I am looking for.
 

jordan.harris01

Senior Member
Jan 4, 2011
387
38
Is there a way to flash the default recovery without adb? Don't want to wait until I'm home this evening. Got a update this morning on telus.

Sent from my SGH-I747M using xda app-developers app
 

itzac

Member
May 25, 2011
16
1
Edmonton
Thanks for the stock recovery image

I just wanted to say thanks to everyone here who posted the stock recovery image. I've been looking for it for days so I could restore it and get the OTA update to 4.1.2 installed. Any suggestions on resetting the flash counter? I've got Triangle Away installed, but I'm a little gun shy since my device isn't listed as supported in the thread.
 

dstruct2k

Senior Member
Jan 31, 2008
1,253
938
Winnipeg
Google Pixel 4
I just wanted to say thanks to everyone here who posted the stock recovery image. I've been looking for it for days so I could restore it and get the OTA update to 4.1.2 installed. Any suggestions on resetting the flash counter? I've got Triangle Away installed, but I'm a little gun shy since my device isn't listed as supported in the thread.
Triangle Away works perfectly fine on this device, and it's pretty much the only way to get an OTA to apply after you've tripped the flash counter.
 

rstepanick

New member
Feb 18, 2012
1
0
Hopefully someone can help me out, been at this for a couple of days trying to get a custom recovery on this device (i747m), but every time I load a recovery I just get the downloading screen. Rooted using CF-Autoroot, tried using Mobile Odin, Goo Manager, Rom Manager, and manually as shown in this thread. been searching for hours, maybe I just keep looking over the answer?

Running stock 4.3.

Any thoughts would be great!
 
Nov 26, 2013
27
0
I own a Samsung galaxy s3 i747m from Koodo, which method should I use? In OPs post it says the i747m is not supported? Also, one of my friends with a galaxy s2 told me installing cwm on his phone removed the "Koodo" that appears on the lock screen and when you pull down the status bar, is that true?

Sent from my SGH-I747M using XDA Premium 4 mobile app
 

dstruct2k

Senior Member
Jan 31, 2008
1,253
938
Winnipeg
Google Pixel 4
I own a Samsung galaxy s3 i747m from Koodo, which method should I use? In OPs post it says the i747m is not supported? Also, one of my friends with a galaxy s2 told me installing cwm on his phone removed the "Koodo" that appears on the lock screen and when you pull down the status bar, is that true?

Sent from my SGH-I747M using XDA Premium 4 mobile app
The M is not properly recognized by the app I mentioned. You can still use any of the other methods to install a recovery, although I strongly suggest TWRP over CWM (much easier to use and many more functions)

Changing your recovery will not make any changes to your Android OS, not even removing the carrier logo/branding. Once you've got a custom recovery though, you can flash any ROM you want, and no other ROMs will have that branding. (I don't know how the partition layout on the S2 worked, maybe the recovery and Android shared a kernel and that's why his changed?)
 
  • Like
Reactions: SterneSchreien
Nov 26, 2013
27
0
The M is not properly recognized by the app I mentioned. You can still use any of the other methods to install a recovery, although I strongly suggest TWRP over CWM (much easier to use and many more functions)

Changing your recovery will not make any changes to your Android OS, not even removing the carrier logo/branding. Once you've got a custom recovery though, you can flash any ROM you want, and no other ROMs will have that branding. (I don't know how the partition layout on the S2 worked, maybe the recovery and Android shared a kernel and that's why his changed?)[/sizie]


Can I flash the recovery using Odin? It seems simplier than using adb or mobile terminal. I used your Terminal Emulator method and it worked flawlessly and very simply, thanks a lot!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 86
    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? :p)



    I'd like to talk about 4 ways to get the custom recovery of your choice onto your device.

    1. Using mskip's Toolkit CWM [link]
      Follow the instructions posted in his thread, and if you have any problems, direct them there as well!

    2. 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.

    3. 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.

    4. 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!
    3
    Moved to General so new members can post questions
    and stuck
    FNM
    2
    Anyone know where to get stock sammy recovery img? Searched but didn't see it.

    Edit: Got it.
    1
    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. ;)
    1
    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