Database Users

Semi-Bricked myTouch 4G

Alright I have a semi-bricked mytouch 4G. (a friend's phone) I followed the gfree guide and did the hboot flash and now I'm in a boot loop. I have the original boot screen loaded and I can get to the recovery menu. S is off so the phone is rooted. How do I get CWM on the phone so I can install a new ROM and kernel so I can unbrick this thing. With my verizon fascinate I have options to go from where I am stuck (Odin and .md5 files). Where do I go from here? Can somone give me a step by step without pointing me to a different forum? I have searched for more than a couple of hours and this is where I have found myself.

Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.

darinmc said:
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
Click to expand...
Click to collapse
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.

fsuagentsmith said:
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
Click to expand...
Click to collapse
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.

neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
I get sending recovery failed... any help from there?

fsuagentsmith said:
I get sending recovery failed... any help from there?
Click to expand...
Click to collapse
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?

neidlinger said:
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
Click to expand...
Click to collapse
yes, I see that

fsuagentsmith said:
yes, I see that
Click to expand...
Click to collapse
ok I changed it to that screen on the phone while trying to push the recovery image. It worked!!!

Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.

neidlinger said:
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Where is the reboot recovery option? As I said in original post I'm familiar with Samsung Galaxy and CWM not so much this phone.

fsuagentsmith said:
Where is the reboot recovery option?
Click to expand...
Click to collapse
are you in Recovery or in Hboot? what color is the screen? black or white?

neidlinger said:
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
Click to expand...
Click to collapse
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?

neidlinger said:
are you in Recovery or in Hboot? what color is the screen? black or white?
Click to expand...
Click to collapse
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?

fsuagentsmith said:
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
Click to expand...
Click to collapse
Awesome!!! I see what you told me to do! When I select recovery this is CWM 3! Awesome. I will see where I can go from here. I still may have questions.

fsuagentsmith said:
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
Click to expand...
Click to collapse
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.

neidlinger said:
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
Click to expand...
Click to collapse
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.

fsuagentsmith said:
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
Click to expand...
Click to collapse
glad to see you got it going.
just make sure to do nandroid backups prior to flashing any new Kernels and make sure they are compatible with AOSP 2.3 ROMs.

neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down

steb0ne said:
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
Click to expand...
Click to collapse
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App

Nicgraner said:
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Well, I was rooted and had been running the leaked 2.3 stock rom. Decided I wanted to try CM7...and flashed it and it appeared to flash okay b/c I was able to boot up, but I couldn't get gapps to install, so I ended up trying to restore from my backup, and that failed, and I couldn't get back to CM recovery. So, I'm stuck in a constant boot loop.

Permarooted s-off still get no CWM recovery mode!?

I am rooted with s-off running on a ATT simcard but still can't boot in CWM recovery. In rom manager it says: current recovery Clockworkmode 3.0.2.4
Whenever I attempt to boot into recovery the MT4G comes up it reboots and it comes up agains and boots regularly. Any thoughts?
I followed all the instructions in this thread and am at the 85.xxx bootloader
http://forum.xda-developers.com/showthread.php?t=858996

I am bone stock other since I've not be able to get into recovery mode. Would a factory reset help?

Do it manually. Go to the bootloader and load recovery from there, or use adb and type adb reboot recovery.

adb does the same thing it attempts to get into recovery then goes blank and reboots regular and same thing with hboot.

Do you have fastboot on?

Nope. Fastboot is off. I can't even factory reset the phone. It just reboots like with everything else

be1ieve1111 said:
Nope. Fastboot is off. I can't even factory reset the phone. It just reboots like with everything else
Click to expand...
Click to collapse
most likely it feels as if the recovery image didn't take.
Code:
adb reboot bootloader
from there select "recovery" and see what boot loader you are using. If you have the engineering screen manually flash it.
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
1. Download CWR3. - link supplied above
2. Save to your Android SDK tools (c:\android-sdk-windows\tools) or platform-tools (c:\android-sdk-windows\platform-tools) folder and rename to recovery.img
3. Turn off your phone.
4. Hold the volume down button + power until you boot to a white screen.
5. Use the volume rocker to select FASTBOOT then press the power button to select it.
6. Connect your phone.
7. Open up a windows command prompt and navigate to your sdk tools or platform tools folder. tools (c:\android-sdk-windows\tools) or platform-tools (c:\android-sdk-windows\platform-tools)
8. Type
Code:
FASTBOOT DEVICES
to make sure your computer "sees" your phone and is ready to flash the recovery. You should get a serial number and then the word fastboot as the output.
9. Type
Code:
fastboot flash recovery recovery.img
and press enter. Give it a minute to do it's thing. You should get a message that says writing recovery and success.
10. Unplug your phone and use the volume rocker to select BOOTLOADER and then again to select RECOVERY and you should be booted into the orange menu of Clockwork Recovery 3
Click to expand...
Click to collapse
taken and modified from http://forum.xda-developers.com/showthread.php?t=919834

It says fastboot isn't a recognized command when I type FASTBOOT DEVICES
also for the bootloader part. It loads real quick and it says something about no image or wrong image in the lines of code that loads on the screen then disappears

Are you using Linux? If so, cd to platform-tools and use ./fastboot instead of fastboot. Otherwise try updating adb and see if it works. Also, the random text is the phone searching for PD15IMG or another restore image. Disregard that, unless you want to flash the stock unrooted image.

[Q] Cannot boot into a custom recovery

So, this is my first attempt at rooting a device and so far it's gone pretty well despite several hiccups along the way. My current problem is the inability to boot into a custom recovery. I'm running the stock 4.4.2 ROM, have root access per towelroot, have SU installed and updated from SuperSU, and have unlocked the boot loader via the motopocalypse exploit in it's .apk format. Booting into fastboot, I am able to verify I have unlocked the boot loader (Status Code 3.) Now, I have several custom recovery files downloaded and have attempted, including ClockWork Mod offical touch and non, and unofficial versions of TeamWin Recovery Project. All four of these yield the same results, namely, I cannot access them.
The steps I preform are:
(1. Turn the device off
(2. Boot into AP fastboot by holding down the volume + and - buttons, turning on the device, and selecting AP Fastboot as prompted
(3. Run the command "fastboot flash recovery <filename>.img"
(4. Have the following returned:
> sending 'recovery' (8228 KB)...
> OKAY [ 0.640s]
> writing 'recovery'...
> OKAY [ 2.180s]
> finished. total time: 2.820s
(5. Run the command "fastboot boot <filename.img>"
(6. Have the following returned:
> downloading 'boot.img'...
> OKAY [ 0.640s]
> booting...
> Command restricted
> FAILED (remote failure)
> finished. total time: 0.730s
(7. Run the command: "fastboot continue" to regain access to my phone
Also, when I boot into the boot selector and select the recovery option, it will show the "Warning, your warranty is void" prompt, flicker, then show the prompt again, which I presumed to be the phone flashing back the stock recovery, which I hadn't had previous success accessing fully either, and then continue to boot normally. Because of that, I used RootBrowser on my device and proceeded to move the "recovery-from-boot.p" file from it's /system home to /storage/emulated/0/Download in the case that I needed it again in the future.
Moving said ".p" file yielded no different result in the aforementioned fastboot commands. However, when I boot into recovery on the device itself via the boot selector, it will hang (let it run for five minutes at one point) at the "Warranty Void" screen, then restart into AP Fastboot after holding the power button, at which point I am unable to turn on the device and need to run the "fastboot continue" command to be able to access my device again. I will also need to run said command every time I want to restart my phone.
Copying said ".p" file back caused the device to again hang at the "Warning: Bootloader Unlocked" screen before I held down the power button which cause it to run AP Fastboot, at which point I could run the "fastboot continue" command and access my phone again.
Suffice to say I'm in a bit of a pickle and am a little lost as to how to get myself out of it. Any help would be greatly appreciated!
- J

The recoveries you should be using are here( TWRP for kitkat second from the bottom works the best) you can either fastboot flash or use rashr/ flashify available on the play store...
We cannot teach people anything; we can only help them discover it within themselves.

4502
I used the TWRP2710-RAZR_M-KITKAT.img and used the Fastboot command to flash it. My phone still isn't liking fastboot commands except for a few, but rebooting into recovery from the boot selector menu now works like a charm. Thank you!
- J

So, now I have the TeamWin Recovery Project functioning, however now I'm unable to flash any ROM. I've wiped the whole device using the advanced wipe feature, attempted to flash an official version of Cyanogen mod (namely 10.2-something,) and an official version of PacMan Rom. Both give me a failed error message whenever I try to flash them. I've just downloaded a fresh nightly from http://forum.xda-developers.com/showthread.php?t=2735565 from 25.08.2014 and I'm going to see if that does the trick. If that doesn't work, much as I'm anticipating, do you have any suggestions? (Also, would I be better off starting a new thread as this is pretty much a secondary issue?)
- J

Never mind! I was actually able to have a friend show me how to properly wipe a device before flashing a custom ROM and now it's functioning properly. Thank you again for your help!
In case someone else has this issue, how I wiped was first a Factory Data Reset, then an advanced wipe for the Cache and the Dalvic, then flashed the ROM and GAPPS, then wiped the Cache/Dalvic again, then actually rebooted the system and it started right into Cyanogen mod.

Yep, I tend to wipe each one(FDR & system+dalvic+cache) 3 times tho I don't think that's really necessary I just wanna be sure it got it all... Happy you got it all working
We cannot teach people anything; we can only help them discover it within themselves.

[Q] Flashing a recovery to I9505 (jgedlte)

I've been trying during the last few hours to flash CWM/TWRP to my S4. Before starting, my phone was simply rooted (with CF-auto-root and Odin).
So I ran
Code:
fastboot oem unlock
and now I'm trying to flash with
Code:
fastboot flash recovery <recovery.img>
, but I keep getting the following error:
Code:
sending 'recovery' (9588 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: FAILSecure - Secure check failed)
finished. total time: 1.224s
(This one is from a run with recovery-clockwork-6.0.4.7-jfltexx.img, I also tried openrecovery-twrp-2.6.3.0-jgedlte.img and got the same error).
I ran
Code:
fastboot erase recovery
to see if it would help, but it did not do any better in the next tries to flash.
Now, I DID manage to boot into CWM with
Code:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
, but I rather flash it (Especially now that I erased the stock recovery.)
I also tried Odin and Heimdall, but Odin simply crashes when I hit "Start" and Heimdall fails to to communicate with my phone.
EDIT: Great. When booting with "fastboot boot", TWRP's touch doesn't work. CWM's touch doesn't work either, so I use the non-touch version, but when trying to install CM with ADB sideload, adb on my PC doesn't recognize CWM. What am I supposed to do now...?

Jon-G said:
I've been trying during the last few hours to flash CWM/TWRP to my S4. Before starting, my phone was simply rooted (with CF-auto-root and Odin).
So I ran
Code:
fastboot oem unlock
and now I'm trying to flash with
Code:
fastboot flash recovery <recovery.img>
, but I keep getting the following error:
Code:
sending 'recovery' (9588 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: FAILSecure - Secure check failed)
finished. total time: 1.224s
(This one is from a run with recovery-clockwork-6.0.4.7-jfltexx.img, I also tried openrecovery-twrp-2.6.3.0-jgedlte.img and got the same error).
I ran
Code:
fastboot erase recovery
to see if it would help, but it did not do any better in the next tries to flash.
Now, I DID manage to boot into CWM with
Code:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
, but I rather flash it (Especially now that I erased the stock recovery.)
I also tried Odin and Heimdall, but Odin simply crashes when I hit "Start" and Heimdall fails to to communicate with my phone.
EDIT: Great. When booting with "fastboot boot", TWRP's touch doesn't work. CWM's touch doesn't work either, so I use the non-touch version, but when trying to install CM with ADB sideload, adb on my PC doesn't recognize CWM. What am I supposed to do now...?
Click to expand...
Click to collapse
This process will trigger knox to 0x1
1. Download the recovery you want:
Download philz touch revovery from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/?page=4 (download the one with .tar.md5 extension)
Download TWRP here:
http://techerrata.com/browse/twrp2/jfltexx (download the one with .tar extension)
2. Download odin3 (v3.10.0) here:
https://mega.co.nz/#!OANlQZBS!GIq9q4Yy72syVYh36Q2whYIg85PST0QJhtIBrRh5MCk
3. Connect your phone in download mode to your PC (Don't reboot into download mode, shut down your phone and then boot into download mode) (you may have to install the driver, here: https://mega.co.nz/#!HQd12QYY!wuM2FvxmScI8rQIdosPaS6CLcvI4-yJNHHOiR3Rv0I0)
4. Open Odin click AP button, choose the file you downloaded and then click start.
5. Your phone will reboot, shut down your phone and try to boot into recovery (hold volume up and home and then press and hold power button release the power button when the blue text appears but keep pressing volume up and home, release those when the screen goes black).
6. You should now be in your chosen recovery.

jeffrey268 said:
This process will trigger knox to 0x1
1. Download the recovery you want:
Download philz touch revovery from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte/?page=4 (download the one with .tar.md5 extension)
Download TWRP here:
http://techerrata.com/browse/twrp2/jfltexx (download the one with .tar extension)
2. Download odin3 (v3.10.0) here:
https://mega.co.nz/#!OANlQZBS!GIq9q4Yy72syVYh36Q2whYIg85PST0QJhtIBrRh5MCk
3. Connect your phone in download mode to your PC (Don't reboot into download mode, shut down your phone and then boot into download mode) (you may have to install the driver, here: https://mega.co.nz/#!HQd12QYY!wuM2FvxmScI8rQIdosPaS6CLcvI4-yJNHHOiR3Rv0I0)
4. Open Odin click AP button, choose the file you downloaded and then click start.
5. Your phone will reboot, shut down your phone and try to boot into recovery (hold volume up and home and then press and hold power button release the power button when the blue text appears but keep pressing volume up and home, release those when the screen goes black).
6. You should now be in your chosen recovery.
Click to expand...
Click to collapse
You are giving him instructions for the I9505. I think he has a I9505G, so he should not follow your instructions. You are giving him a recovery for the I9505. The I9505G is a different model.
If Heimdall fails to communicate with your phone, then you don't have the correct drivers installed. TWRP doesnt have a non touch version. So my guess is that you flashed the recovery for a different device.

If the phone is already rooted just use ROM Manager or TWRP Manager apps from Google Play.
Both will just wipe out and overwrite any existing recovery image and replace it with the one you want. Problem solved right from the phone. No ADB shell needed.

Thanks guys. I managed to flash both philz (That link you gave me, although it is for I9505 and I do have a I9505G) and TWRP.
Both work, but besides them the phone is completely bricked.

Jon-G said:
Thanks guys. I managed to flash both philz (That link you gave me, although it is for I9505 and I do have a I9505G) and TWRP.
Both work, but besides them the phone is completely bricked.
Click to expand...
Click to collapse
If you can boot to recovery the phone is not a complete brick.
Once you are in recovery you can flash anything you want. You should be able to flash any new ROM and it will boot right up.

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.