Database Users

[Q] MT4G not taking CWM recovery

I'm working on a friend's MT4G after having rooted mine several months ago. The phone I'm working on is perm rooted with s=off. I can go into hboot and it shows s=off. The problem is the phone will not take Clockwork Mod's recovery.
CWM downloads and installs, then gets superuser permission and claims to be flashing recovery, but trying to reboot into recovery doesn't work. The phone boots to the "T-Mobile MyTouch 4G" screen, blinks off, comes back to that screen, then proceeds to boot to stock Android.
Uninstalling and reinstalling CWM just gets the same result - no recovery.
Shutting down completely then hoilding Vol up while pressing power makes the phone vibrate rapidly 3 times, then the LED blinks orange.
Going to hboot, then selecting recovery from there boots to stock Android same as trying to get to recovery through CWM.
How do I get this sucker to take CWM recovery?

It happened to me also, I just kept pressing it over and over and eventually it downloaded the file, If you have your's rooted why not go into your SD card and take the recovery IMG and put it on the other phone?

If you have the engineering screen you can ADB flash it via fastboot.
or you can use the ADB commands from within the ROM to do it.
either way download the recovery image i have posted in this thread. or from koush's web site store just the recovery image on the root of the SD card.
Code:
adb shell
su
flash_image recovery /sdcard/recovery.img
via hBOOT, give you have the .85 hBoot.
1) Download the attached file from the link i showed above and store just the recovery image to your folder from which you preform all of your ADB commands
2) plug the phone into the computer
3) boot the phone into HBoot
4) from the ADB commands change the drive to the folder where you stored the recovery image.
5) type these commands
Code:
Code:
fastboot flash recovery recovery.img
the screen should say something to the degree of
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
6) then select "bootloader"
7) navigate to "reboot recovery"

Turns out that particular phone did NOT like CWM recovery 3.0.2.4. Once I got legacy recoveries to show up, I put 3.0.0.5 on it and was able to get into CWM recovery. From there I flashed 3.0.0.6, then put RoyalGinger on it.
Works great now, it's just odd that 3.0.2.4 didn't work on it.

[Recovery]CWM 6.0.4.5[UPDATED WITH INSTRUCTIONS][25/12/2013]

Well here is cwm 6.0.4.5 for our beloved a500. You will need this to flash KitKat ROMs like the new kitkat rom that was recently relased for our tablet. It is recommended that you flash this in secboot as I am not very sure what works and what does not. It pays to have a working recovery in your recovery partition.
To flash this rom in your secboot, you must have skrilax bootloader installed from http://forum.xda-developers.com/showthread.php?t=1619913
Download link of recovery: http://www.mediafire.com/view/?myy59371lsrs6u4
Instructions:
1. Use this awesome tool from http://forum.xda-developers.com/showthread.php?t=2588979 to install adb and fastboot on your windows pc easily. (Remember to run the downloaded exe as administrator)
2. Install Acer A500 usb drivers from http://us.acer.com/ac/en/US/content/drivers (Just search for A500 in the search by product model search box.)
3. Make sure you have Skrilax_CZ's bootloader installed on your A500.
4. Turn off your A500 and turn it on again, this time holding the volume up button.
5. When the bootloader screen appears, scroll with the volume buttons and select Fastboot with the power button.
6. Now, copy the recovery.img which you downloaded from the download link above to the root of your C:/ drive.
7. Press start and open cmd.
8. In cmd, type cd C:/
9. Now, connect your A500 to the PC via usb and wait for a while before typing
Code:
fastboot flash secboot recovery.img
in cmd.
10. After the process is done, type
Code:
fastboot reboot
into cmd.
11. When the tablet boots, hold volume up and when the bootloader screen shows, scroll to Boot Secondary Kernel Image with the volume keys and select it with the power button. CWM should load and have fun!!!
Thanks to @pjsports for his 4.3 device source and vendor blobs

nelsontky said:
Well here is cwm 6.0.4.5 for our beloved a500. You will need this to flash KitKat ROMs in the future. It is recommended that you flash this in seboot as I am not very sure what works and what does not. It pays to have a working recovery in your recovery partition.
Download link: http://www.mediafire.com/view/?myy59371lsrs6u4
Installation:
fastboot flash secboot recovery.img (recommended)
Or
fastboot flash recovery recovery.img
Thanks to @pjsports for his 4.3 device source and vendor blobs
Click to expand...
Click to collapse
ok this is what i get when i try to flash this or any recovery
C:\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)... OKAY [ 1.278s]
writing 'recovery'... FAILED (remote: (00030003))
finished. total time: 1.675s
C:\sdk-tools>
any ideas?
ok I got a recovery on there but now it is not seeing any files within my folders- this is so strange

I tried flashing this recovery but i get this error
also i tried flashing the img recovery with this app but i don't work either
https://play.google.com/store/apps/details?id=com.cgollner.flashify

nsciucco said:
ok this is what i get when i try to flash this or any recovery
C:\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)... OKAY [ 1.278s]
writing 'recovery'... FAILED (remote: (00030003))
finished. total time: 1.675s
C:\sdk-tools>
any ideas?
ok I got a recovery on there but now it is not seeing any files within my folders- this is so strange
Click to expand...
Click to collapse
Erm what ROM are u using. And yea do you have like zip files in your folders cos I think the recovery only see zip files

tire_007 said:
I tried flashing this recovery but i get this error
also i tried flashing the img recovery with this app but i don't work either
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
Dun use the app (idk those apps never worked for me, well except for the Acer recovery installer) and when using fastboot, make sure the recovery.IMG is in the same directory as fastboot

I was on cm10.2. My tablet froze so I held the power button down to hard reset. Then it never booted up. I tried to go into recovery to install a new rom and I'm not even able to get into downloads. If I click sd or sd-ext there is no folders anything. It's like my device is wiped. I'm stuck. Only thing I can do is get into bootloader or apx mode. I've downloaded roms that I can supposedly flash in apx mode with that blackthunder tool. But I can't figure it out. I'm not an idiot either. I've rooted well over 200 phones . I do it for extra cash...and never had a issue like this
Sent from my SM-N900P using xda app-developers app

nsciucco said:
I was on cm10.2. My tablet froze so I held the power button down to hard reset. Then it never booted up. I tried to go into recovery to install a new rom and I'm not even able to get into downloads. If I click sd or sd-ext there is no folders anything. It's like my device is wiped. I'm stuck. Only thing I can do is get into bootloader or apx mode. I've downloaded roms that I can supposedly flash in apx mode with that blackthunder tool. But I can't figure it out. I'm not an idiot either. I've rooted well over 200 phones . I do it for extra cash...and never had a issue like this
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Hmmm download a working recovery and flash into your recovery partition. Then flash this into secboot

Flash what?
Sent from my SM-N900P using xda app-developers app

nsciucco said:
Flash what?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Well you can download twrp from http://teamw.in/project/twrp2/88 and flash it to your secboot partition with "fastboot flash secboot [name of recovery].img" Then go to your boot menu (hold volume up when booting) and choose the akb partition (second partition) This should get you booted into twrp where your files should be there. If there are still no files, you have to use an external sdcard good luck

any chance you can build this: http://forum.xda-developers.com/showthread.php?t=2201860
against our device + CWM version 6.0.4.8?
I'd do it, but I have no idea where to start. I love PhilZ touch recovery, it's very customizable and also very useful.

kronflux said:
any chance you can build this: http://forum.xda-developers.com/showthread.php?t=2201860
against our device + CWM version 6.0.4.8?
I'd do it, but I have no idea where to start. I love PhilZ touch recovery, it's very customizable and also very useful.
Click to expand...
Click to collapse
Well i can try but no promises

thanks! apparently it's easy.
Once you can build stock CWM, just replace your bootable/recovery folder with this one and lunch for your device
Click to expand...
Click to collapse
I just don't have the sources, or the knowhow to compile this myself.

nelsontky said:
Well i can try but no promises
Click to expand...
Click to collapse
had a chance to try yet? not to bug or nag, just curious for an update

Now updated with instructions
Now this is updated with instructions!

thanks man.
good work

nelsontky said:
Now this is updated with instructions!
Click to expand...
Click to collapse
can you provide building instructions? I tried using the sources you used, but I get errors using his repos. He's got some repos from "loosethisskin" which don't allow building. I can't remember the exact errors, but I'm wondering what you did to avoid this(if you encountered this at all)
By simply not replacing those repos(ie: removing them from the manifest before syncing) I get a resulting recovery.img that fails to fastboot flash.
I've even tried using acer recovery flasher, and a couple other tools, but it doesn't boot.
I'd like to try building 6.0.5.0 as well as PhilZ Recovery, but again, I can't get it to build.

@nelsontky
Thanks for your job.
I want to make a backup before to install the new Bootloader ( Skrilax_CZ's), but to that I cannot do it with stock recovery (the stock recovery didn't have the option to backup/restore).
Is there some problem/incompatibility that avoid to load your recovery (6.0.4.5) before to load Skrilax_CZ's bootloader?
Or in another way the function of your recovery are based on Skrilax_CZ's bootloader?
Could you update your recovery with new file from CWM Github (recovery version is now 6.0.5.0)?
Could you post the configuration file (Board parameters) that you use to compile the recovery.
I downloaded the source of CWM and I want to test it myself.
If you update your CWM repository via GitHub pull command just recompile the recovery.
Proposal to download the file: could be better to distribute the recovery as zip (like A500_CWM_recovery_vx.x.x.x.x.zip - it's self explantory) with inside the recovery.img file. It's always better to avoid to download native recovery image to avoid partial download or corrupted file.
Thanks.

bovirus said:
@nelsontky
Thanks for your job.
I want to make a backup before to install the new Bootloader ( Skrilax_CZ's), but to that I cannot do it with stock recovery (the stock recovery didn't have the option to backup/restore).
Is there some problem/incompatibility that avoid to load your recovery (6.0.4.5) before to load Skrilax_CZ's bootloader?
Or in another way the function of your recovery are based on Skrilax_CZ's bootloader?
Could you update your recovery with new file from CWM Github (recovery version is now 6.0.5.0)?
Could you post the configuration file (Board parameters) that you use to compile the recovery.
I downloaded the source of CWM and I want to test it myself.
If you update your CWM repository via GitHub pull command just recompile the recovery.
Proposal to download the file: could be better to distribute the recovery as zip (like A500_CWM_recovery_vx.x.x.x.x.zip - it's self explantory) with inside the recovery.img file. It's always better to avoid to download native recovery image to avoid partial download or corrupted file.
Thanks.
Click to expand...
Click to collapse
The Skrilax_CZ bootloader is absolutely necessary, because it allows flashing and booting from the secboot. The recovery is too large to fit in the recovery partition. That having been said, I may be able to shrink it to fit, if I could get it to compile and boot.
I've had to do the same thing to the recovery for the HTC ChaCha,
He's not using a straight up CWM repo, he would be using the repos for CM10.2, which automatically compiles CWM along with it(or if you give it the arguments, it can compile just recovery)
The bootloader can only be flashed using nvflash, and for a backup, you'll need an older copy of CWM and flash that via fastboot. I personally recommend the tegraowners recovery(I don't like the tegraowners team, but their recovery really is best out of the older ones) you can find it here

Apparently windows 8 hates my tablet. so I tried it on a windows 7 machine, the result was a working recovery. although oddly, it build 6.0.4.6, not 6.0.5.0. weird. maybe I'll poke at it later and try to update just the cwm repo. whatever the case, this gives me a working setup to try PhilZ Touch Recovery

I believe that the main scope should be to have a recovery that use no more space than the partition size.
It's due to avoid not use unofficial bootloader and to avoid overwiting importan partition like NVRAM (IMEI).

Flashing Recovery no worky - unlocked BL xt1080

Hi,
I have a Droid Maxx XT1080.
I purchased a Moto 360 and my Maxx was running 4.2.2 so it wasn't compatibility. I've never updated cause I had root & wifi tether. I found out sunshine would be able to unlock my bootloader so I did it. I then used RSLite and flashed 4.4.4. So now I have 4.4.4, no root, no wifi tether, unlocked bootloader. I've been trying to flash recovery with TWRP or CWM with no luck. It says it flashed via command prompt and fastboot but when I go to select recovery in fastboot it just reboots the phone. With the phone off and pressing power and volume up, it won't enter recovery as well, just boots straight up.
I don't know if I should just use RSLite to flash the whole phone back to a different state and try again. I just don't want to write over the unlocked bootloader accidentally.
I tried using this recovery method with no luck: http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/
I've also tried TWRP 2.8
Thanks,
Ambrose

You press volume down and power hold the rocker 1st

Durteedee said:
You press volume down and power hold the rocker 1st
Click to expand...
Click to collapse
Understood, that brings me to fastboot which I then scroll down to recovery and hit the power button to select. I get a blank screen and have to press and hold my power button again for the phone to eventually reboot into Android.

OK what is said via fastboot flashing are you flashing as root/admin?

Durteedee said:
OK what is said via fastboot flashing are you flashing as root/admin?
Click to expand...
Click to collapse
Phone:
Flashboot Reason: Key pressed
USB Connected
getvar max-download-size
downloading 8708096 bytes
done
flashing recovery
done
Command Prompt (as Administrator on Windows 8.1):
C:\Users\teh brosta\Desktop\Windows>fastboot flash recovery cwm6.0.3.6.img
sending 'recovery' (8504 KB)...
OKAY [ 0.770s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.689s
I selected recovery from fastboot and it just booted the phone...

When it boots up turn on adb and reboot recovery from there

Durteedee said:
When it boots up turn on adb and reboot recovery from there
Click to expand...
Click to collapse
That actually brought me into CWM, but it wouldn't let me do anything. I just saw the logo in the middle and version number at the bottom. I just flash TWRP and used adb to get into recovery that seems to be working! What is preventing me from getting to recovery from fastboot?
Thank you!

My guess has something to do with it not being made for your device, try flashing moto x recovery first then the custom one

when in fastboot you use vol up to select not the power button. i think this is where you are going wrong.

This should work
tehbrosta said:
Hi,
I have a Droid Maxx XT1080.
I purchased a Moto 360 and my Maxx was running 4.2.2 so it wasn't compatibility. I've never updated cause I had root & wifi tether. I found out sunshine would be able to unlock my bootloader so I did it. I then used RSLite and flashed 4.4.4. So now I have 4.4.4, no root, no wifi tether, unlocked bootloader. I've been trying to flash recovery with TWRP or CWM with no luck. It says it flashed via command prompt and fastboot but when I go to select recovery in fastboot it just reboots the phone. With the phone off and pressing power and volume up, it won't enter recovery as well, just boots straight up.
I don't know if I should just use RSLite to flash the whole phone back to a different state and try again. I just don't want to write over the unlocked bootloader accidentally.
I tried using this recovery method with no luck: http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/
I've also tried TWRP 2.8
Thanks,
Ambrose
Click to expand...
Click to collapse
I just went through the same thing on a Maxx last night. This is what worked for me
Download TWRP 2.8 from here http://techerrata.com/browse/twrp2/ghost
flash that through the dos windows with your phone booted to fastboot mode.
as soon as the phone resets hold the power and vol down. you must do this fast. Then pick recovery and twrp should boot up. then exit twrp and it should ask you to root, move the slide bar and you all set.

smooth781 said:
I just went through the same thing on a Maxx last night. This is what worked for me
Download TWRP 2.8 from here http://techerrata.com/browse/twrp2/ghost
flash that through the dos windows with your phone booted to fastboot mode.
as soon as the phone resets hold the power and vol down. you must do this fast. Then pick recovery and twrp should boot up. then exit twrp and it should ask you to root, move the slide bar and you all set.
Click to expand...
Click to collapse
Running into same issue. have Twrp 2.8-ghost but what do you mean flash dos windows?
when I run the command it says
(bootloader) variable not supported!
error: cannot open 'Twrp..img' file
"

Carrzy said:
Running into same issue. have Twrp 2.8-ghost but what do you mean flash dos windows?
when I run the command it says
(bootloader) variable not supported!
error: cannot open 'Twrp..img' file
"
Click to expand...
Click to collapse
is your bootloader unlocked? if it is this is the command you should be typing.
Code:
fastboot flash recovery recovery.img
just replace the recovery.img portion with the file name of your twrp file.

Read this!
http://forum.xda-developers.com/showpost.php?p=55779972&postcount=116

aviwdoowks said:
Read this!
http://forum.xda-developers.com/showpost.php?p=55779972&postcount=116
Click to expand...
Click to collapse
Still didn't work..

Instead of using RSD or RSD Lite use moto-fastboot. I stopped using RSD a long time ago. I was having an issue flashing the TWRP recovery on my phone but i noticed when I first flashed my phone with 4.4.4 it failed the motoboot.img flash. So when i re-flashed my phone with 4.4.4 and then re-flashed TWRP it finally worked out for me.
Being motorola uses moto-fasboot regular fastboot won't work.

Stuck on boot animation screen? [SOLVED]

I tried to root my NSTV and got as far as flashing the .zip file in TWRP but after I rebooted, it's now stuck in the boot animation screen with the dancing colored circles?
Any ideas please?
SOLUTION
First download Recovery OS Image from here: https://developer.nvidia.com/gameworksdownload
SHIELD RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
 These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD, connect your SHIELD
 via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Disconnect power cable
- Insert USB OTG cable and make sure to connect other end to a host PC
- Connect power cable to SHIELD
- Quickly start pressing power button for ~3 seconds
- Do not hold the button and connect power supply afterwards
- HDMI TV should be always connected to SHIELD
Alternative method:
- Perform software shutdown on SHIELD by holding Power button for 10 seconds
- Connect USB OTG cable to SHIELD
- Start pressing power button for 3 seconds
- HDMI TV should be always connected to SHIELD
Fastboot menu navigation:
- Single tap on touch button for navigations between different menu.
- Hold down touch button for 4 second and release for selecting any menu
To flash this recovery image to your SHIELD, run the following commands from
 the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
 DTB file name to use for flashing for your product(see below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
Unlocking the Bootloader
Your SHIELD may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- It will take you to '!!! READ THE FOLLOWING !!!' page.
- Two selectable options are available. 'Confirm' and 'Back to menu'.
- Select 'Confirm' to unlock the bootloader.
Unlock may take upto 2 hours for pro device.
Get <DTB file name>
- For base sku use dtb file "tegra210-foster-e-p2530-0930-e02-00.dtb"
- For pro sku use dtb file "tegra210-foster-e-hdd-p2530-0932-e02-00.dtb"

old thread i know, but still very helpful!
after updating to 3.2 yesterday and then trying to root it again (lost after the update), i was stuck at the boot animation screen for-ev-ver!!
used this guide to fix and was successful, however there was one change that i had to make: after extracting the 3.1 recovery image....there was no "userdata.img" file. so in place of that file, i flashed the "vendor.img", which was in the extracted folder along with the other files i needed to flash.
in the end what worked for me was the following:
downloaded the 3.1 recovery OS image from the link provided in OP. extracted/unzipped the image file to a folder, then from that folder i flashed the following files in this order:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash staging blob
fastboot flash dtb tegra210-foster-e-p2530-0930-e02-00.dtb
worked like a charm for me, booted up fine, ran updates and when it was done it asked if i wanted to update to version 3.2 ....i said yes and when that finished, i tried to root it once again. all went smoothly this time. not sure what went wrong the first time, but i am now on version 3.2, rooted, and did not even lose any data along the way!!
hardest part for me was getting into the bootloader (using HW method posted above). took me quite a few tries before i nailed it, lol
thanks for posting @Neo3D

Just tried to do it, but failed:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 67108864 bytes
sending 'recovery' (22712 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.014s

I;m stuck,it won't except the tegra darcy or tegra foster. Help please i am sitting her stuck!

Problem rooting Nexus 4 on Mac OS X

I am wanting to root my old Nexus 4 because you can apparently use a USB OTG cable with it once it's rooted? I can't seem to get the damn thing rooted though!
I've been following this tutorial, as the second video is specifically for Mac users.
I've managed to unlock my boot loader, and then try to flash CWM, but whenever i reset my phone, it doesn't boot into CWM, just the normal boot screen. I've followed the video step by step and tried it multiple times, with no success.
I've also tried using these one-click methods (the One-Click ClockworkMod Recovery Toolkit version), and I can boot into CWM recovery, but then whenever I restart my phone, I loose the CWM recovery,
Can anybody help me try to root my Nexus 4 on Mac OS X. I don't mind not rooting if there is another way USB OTG can be used with the Nexus 4?

Ysh232 said:
I am wanting to root my old Nexus 4 because you can apparently use a USB OTG cable with it once it's rooted? I can't seem to get the damn thing rooted though!
I've been following this tutorial, as the second video is specifically for Mac users.
I've managed to unlock my boot loader, and then try to flash CWM, but whenever i reset my phone, it doesn't boot into CWM, just the normal boot screen. I've followed the video step by step and tried it multiple times, with no success.
I've also tried using these one-click methods (the One-Click ClockworkMod Recovery Toolkit version), and I can boot into CWM recovery, but then whenever I restart my phone, I loose the CWM recovery,
Can anybody help me try to root my Nexus 4 on Mac OS X. I don't mind not rooting if there is another way USB OTG can be used with the Nexus 4?
Click to expand...
Click to collapse
Use TWRP 3.0.0, it's up to date and supported still. The flashing process is the same as CWM: ./fastboot flash recovery twrp-3.0.0-0-mako.img Also, to boot into recovery, power off your phone and hold Volume Down+Power and it will boot into the bootloader, then use the volume buttons to select recovery and power button to boot it into recovery. I use OS X so if you need any help just quote me and I'll try to help out
Edit
If you have ADB downloaded as well in the same directory of Fastboot, you can enable USB Debugging under developer options in Settings on your N4. Type /.adb reboot recovery in Terminal whenever you want to boot into recovery, without having to do the above process that I mentioned.

After flashing recovery, boot directly into recovery after flashing using the volume and power button. Do not reboot the phone before booting into the new recovery. Also, there is no need to power off the phone before booting the new recovery for the first time.

fireball0093 said:
Use TWRP it's up to date and supported still. The flashing process is the same as CWM: ./fastboot flash recovery twrp-3.0.0-0-mako.img Also, to boot into recovery, power off your phone and hold Volume Down+Power and it will boot into the bootloader, then use the volume buttons to select recovery and power button to boot it into recovery. I use OS X so if you need any help just quote me and I'll try to help out
Edit
If you have ADB downloaded as well in the same directory of Fastboot, you can enable USB Debugging under developer options in Settings on your N4. Type /.adb reboot recovery in Terminal whenever you want to boot into recovery, without having to do the above process that I mentioned.
Click to expand...
Click to collapse
Thanks for the advice. I downloaded TWRP and booted into recovery. I then entered the following into the terminal:
Code:
A-MacBook-Pro:RootNexus4 A$ ./fastboot-mac flash recovery twrp-3.0.0-0-mako.img
sending 'recovery' (9122 KB)...
OKAY [ 0.292s]
writing 'recovery'...
OKAY [ 0.475s]
finished. total time: 0.767s
I then changed the setting on my N4 from 'Start', to 'Recovery Mode' and pressed the power button. It seems to have booted into TWRP correctly. I then chose to restart phone as normal and got the infinite boot sequence of coloured balls swooping in-between each other...
I'm confused whats going on here...

Ysh232 said:
Thanks for the advice. I downloaded TWRP and booted into recovery. I then entered the following into the terminal:
Code:
A-MacBook-Pro:RootNexus4 A$ ./fastboot-mac flash recovery twrp-3.0.0-0-mako.img
sending 'recovery' (9122 KB)...
OKAY [ 0.292s]
writing 'recovery'...
OKAY [ 0.475s]
finished. total time: 0.767s
I then changed the setting on my N4 from 'Start', to 'Recovery Mode' and pressed the power button. It seems to have booted into TWRP correctly. I then chose to restart phone as normal and got the infinite boot sequence of coloured balls swooping in-between each other...
I'm confused whats going on here...
Click to expand...
Click to collapse
I've now tried to Reboot (through TWRP, and clicked Bootloader, but TWRP says there is no OS installed. Thats probably why I get the infinite boot loop? How can I re-install the OS? I've downloaded the factory image from Google, but can't flash it...

You can manually flash each partition to the phone using fastboot commands. This will restore the phone back to stock.
Once the phone is able to boot the stock rom, reinstall twrp, boot into twrp, and flash supersu.