Database Info

[Q] [Problem] Cannot flash recovery

Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.

It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error. Screenshot of cmd would be very helpful too please
Sent from my Nexus 5 using Tapatalk

rootSU said:
It is indeed the stock recovery. OTA returned it. It also removed root so rom manager won't work, but you shouldn't use rom manager anyway.
You'll need to download a recovery and flash it using fastboot .
Please describe the exact steps you took to get the fastboot error.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What I did is to check if the boot loader is unlocked.
And yes. It is unlocked.
So I carried onto checking if fastboot detects my devices by doing "fastboot devices". And my nexus5 gets detected.
Then I moved on to trying to flash recovery using " fastboot flash recovery recovery.img ".
But the error appears at this point. And I'm stuck.
Is this sufficient?
Do note that I did change the file name to recovery and not recovery.img as most files do not include the file type in the file name.

Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.

You would be better served setting windows not to hide known file types to be honest.
A screenshot of your fastboot flash attempt and error would be most useful please
Sent from my Nexus 5 using Tapatalk
---------- Post added at 05:40 PM ---------- Previous post was at 05:28 PM ----------
chblg said:
Try flashing the recovery using dd (You need root)
Boot the phone normally and push the recovery.img using adb and flash it:
Code:
adb push *Path to recovery.img* /data/media/0/
adb shell
# dd if=/data/media/0/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I hope this helps.
Click to expand...
Click to collapse
He hasn't got root. Fastboot is his only option
Sent from my Nexus 5 using Tapatalk

Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img

Nukyi said:
Hi All.
Hopefully someone is able to help me. I'll try to give as much information as I can.
I have followed the following guide to root my nexus 5.
I have rooted it successfully last month.
However, I have accidentally installed a OTA update from google this week (Android 4.4.3).
Just a while earlier, I have decided to flash a custom rom.
So, as usual, I reboot my phone into recovery.
However, the recovery shows the android with a red triangle, stating "no command".
I have read the forums and read that this is actually not an error but it is the default recovery for android. (Edit: Ok. Maybe its not the default recovery. Anyone able to give me advice on this?)
I guess that my recovery was returned to the stock recovery after the OTA update.
So I tried to flash CWM recovery using ROM manager, but it states "An error occured while flashing your recovery".
I decided to restart my phone and to try it again, now it stucks at 100% on ROM Manager.
I have also tried to flash recovery.img using fastboot. However, it didn't work too.
It returns with an error: "cannot open recovery.img"
May I know if anyone can help me with this problem?
More info on the current status of my phone:
Bootloader unlocked. (Checked by trying to unlock it again. System states that process has failed as it is already unlocked)
ADB Device: Detect-able.
Fastboot Device: Detect-able.
Click to expand...
Click to collapse
rootSU said:
Well FWIW for anyone else reading, my assumption was going to be that the OP didn't put the full path to the recovery OR didn't put the recovery in the location the cmd prompt was running from.
Would have been nice to have seen this through to conclusion, but I cannot monitor forever so I'm unsubscribing due to lack of replies.
eg:
Code:
c:\Users\Administrator>fastboot flash recovery recovery.img
If there is no path to recovery image as above, then the asumption to cmd is that the recover image is in c:\users\administrator (Which it probably isnt)
If it is on the administrators desktop you would:
Code:
c:\Users\Administrator>fastboot flash recovery c:\users\Administrator\Desktop\recovery.img
Click to expand...
Click to collapse
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.

Nukyi said:
Hi. Sorry for late reply. Was at work. I'll try out the full path. What I was told is to just put the recovery IMG into the same folder as fastboot and it should do the trick. Will post screenshots after trying out.
Click to expand...
Click to collapse
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.

Nukyi said:
Hi All,
Here's the screenshot of my cmd.
Please kindly assist and advise on what should I do.
Thank you.
Click to expand...
Click to collapse
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?

rootSU said:
Ok thanks.
Did you turn off "Hide known file types"? can you screenshot in Windows explorer, the location of the recovery image with hide turned off and in "details" view please?
Click to expand...
Click to collapse
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.

Nukyi said:
Yes. I did. Here are the images.
I'm using windows8. So it may look a little different.
Click to expand...
Click to collapse
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks

rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
Alright. I'll do it and get back to you shortly.
Thank you.
Really hope this fixes the problem.

rootSU said:
If I gave you a few steps to try and rule out some variables to narrow down the fault are you happy to do them?
My first thing to suggest would be to take a copy of the "platform-tools" folder and drop it on the root of c: (meaning ensure c:\platform-tools exists)
Then right click Computer > Properties > Advanced System Settings (A System Properties pop up will be shown, in the advanced tab)
In the pop-up, press "Environment Variables" and in the bottom window, called "System variables" scroll down to the entry called "Path" and press edit.
Scroll to the very end of the line of text. Add the following to the end of the line with no spaces (and no quotes obviously)
";c:\platform-tools" and click OK to all windows and pop-ups. Just to break that down, it is a semi colon ; followed by the path to the platform-tools folder.
Give yourself a restart.
What this does, is gives you the ability to call the fastboot command from anywhere. So instead of typing Desktop\adt-bundle......\platform-tools\fastboot flash blah blah, you can literally just type "fastboot flash" because like other commands, it is now a system variable.
Then put the recovery.img in the directory that cmd opens up to which appears to be be "c:\users\blah"
Then open cmd and do the basic command with no paths.... fastboot flash recovery recovery.img
Let me know,
Thanks
Click to expand...
Click to collapse
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?

Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)

jj14 said:
Did you check if the MD5 of the recovery file is correct? (to rule out a bad download)
Click to expand...
Click to collapse
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.

Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
Now try and run cmd as an administrator if you are not doing

Nukyi said:
I have tried it. Still doesn't work. (Screenshot as attachment)
Could there be a problem with the phone instead of with the path/common errors?
Click to expand...
Click to collapse
no. the recovery.img is not in c:\users\username\
put that file there, then retry your command
OR
fastboot flash recovery c:\entire\path\to\recovery.img

Nukyi said:
Re-downloaded it many times. Checked all of the md5.
Downloaded not only CWM recovery. But also other custom recovery.
Click to expand...
Click to collapse
are you sure you downloaded the image and not the zip??

samersh72 said:
are you sure you downloaded the image and not the zip??
Click to expand...
Click to collapse
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.

Nukyi said:
Pretty sure it is the image. Downloaded from the website itself. They only comes in .img and not in zip.
Click to expand...
Click to collapse
Ah. It just worked suddenly. No idea why. But I guess @rootSU 's suggestion works well.
And maybe also @Zepius 's suggestion.
Here's what I did to help others who have the same problem.
I did what rootSU asked me to do (changing the "path" part).
Then took Zepius suggestion and duplicated the recovery img in a few folders (the original folder i'm using, on desktop, on C drive root folder)

[Q] Help with ADB Side Load

Help I messed up and formated the phone in TWRP 2.8.3.1 and now its stuck on the LG logo. I can still boot into TWRP but all my files were deleted off the phone. I have the SDK downloaded for sideload but when I goto the command prompt it reconizes the phone but DOES NOT have "sideload" next to the device name. When I try to side load I get an error and nothing. I also did not turn on ADB side load on my device before it happen. Please help if possible.....

Symbian_Black said:
Help I messed up and formated the phone in TWRP 2.8.3.1 and now its stuck on the LG logo. I can still boot into TWRP but all my files were deleted off the phone. I have the SDK downloaded for sideload but when I goto the command prompt it reconizes the phone but DOES NOT have "sideload" next to the device name. When I try to side load I get an error and nothing. I also did not turn on ADB side load on my device before it happen. Please help if possible.....
Click to expand...
Click to collapse
Let me help you
0. do not enable adb sideload inside twrp
1. look up your directory where adb is
2. open command window there (right click on folder or inside folder -> open command window here)
3. put your files inside the very same directory (for example rom.zip)
4. adb push rom.zip /sdcard/rom.zip
5. flash

bender_007 said:
Let me help you
0. do not enable adb sideload inside twrp
1. look up your directory where adb is
2. open command window there (right click on folder or inside folder -> open command window here)
3. put your files inside the very same directory (for example rom.zip)
4. adb push rom.zip /sdcard/rom.zip
5. flash
Click to expand...
Click to collapse
I forgot to tell you that I did not have debugging enabled on my phone at the time.........

Doesn't matter at all.
Should work.
Or - buy an USB otg Cable and you can use USB flash disks
Poslano sa mog LG-D802 koristeći Tapatalk

THANK YOU
bender_007 said:
Let me help you
0. do not enable adb sideload inside twrp
1. look up your directory where adb is
2. open command window there (right click on folder or inside folder -> open command window here)
3. put your files inside the very same directory (for example rom.zip)
4. adb push rom.zip /sdcard/rom.zip
5. flash
Click to expand...
Click to collapse
I got it to work! I actually did the ADB sideload in TWRP but used your command prompts. THANK YOU

Same thing but...
It is awesome you got your's to work! I have the exact same problem but my usb port isn't working I believe. Over multiple pc's and usb cables I keep getting UNKNOWN USB DEVICE. I went into a repair shop today and got a different port but then the screen wouldn't turn on so they put my old port back in. The LED light did flash so I'm wondering if I'd be better off getting the new USB port then worrying about the screen later. Any advice would be greatly appreciated. Thank you!

It help me a lot
The trick was not enabling adb sideload in twrp. Thank you for the info. I almost bought a new phone.

Of course. Read posts m8
Poslano sa mog LG-D802 koristeći Tapatalk

Please Help - Stuck in boot loop

Hi All, I hope someone can help.
I got this phone in December, and unlocked it, flashed TWRP and rooted.
My phone automaticly updated and was on version 7.1.2. But Super SU wasnt working anymore.
I tried to boot into TWRP but it was saying somthing like "No command given" when I tried.
I used Skipsoft toolkit to flash the recovery again (What I originally used) and when the phone rebooted, it gets to the Google logo and instantly reboots.
I can get to bootloader, but if I select recovery, it reboots.
Is there anything I can do here?
I did a backup in TWRP before I flashed, its stored on the phone.
Thanks in advance

I would use the tool to go back to stock. Just pick the last Google is the app I believe its V. Either update to the lastest software or I just flashed a rom with the newest vender

Hi, Thanks for your reply.
How can I do this though, I cant get the phone to boot, or into recovery

Is there a way I can use adb to push a TMRP so I can restore my backup?
My PC makes the noise as if something is attached by USB, but when I do adb devices, nothing shows.

Hi all,
I managed to sort it out and restore to original as advised above with fastboot. Never used it before, but I followed this guide and it worked great.
http://www.droidviews.com/install-stock-firmware-on-google-pixel-or-restore-it-to-stock/
Thanks again

You can get TWRP and root on the May update.
https://forum.xda-developers.com/showthread.php?t=3600606

Anthony2oo5 said:
Hi all,
I managed to sort it out and restore to original as advised above with fastboot. Never used it before, but I followed this guide and it worked great.
http://www.droidviews.com/install-stock-firmware-on-google-pixel-or-restore-it-to-stock/
Thanks again
Click to expand...
Click to collapse
This didn't work for me. I got as far as:
7. Now type the following command in the command window and hit the Enter key.
flash-all.bat
When doing that, I got the following returned in the CMD prompt:
'flash-all.bat' is not recognized as an internal or external command, operable program or batch file.

In the CMD prompt, make sure you're in the folder where you extracted the contents of the zip file.

graymoment said:
This didn't work for me. I got as far as:
7. Now type the following command in the command window and hit the Enter key.
flash-all.bat
When doing that, I got the following returned in the CMD prompt:
'flash-all.bat' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
X04D said:
In the CMD prompt, make sure you're in the folder where you extracted the contents of the zip file.
Click to expand...
Click to collapse
As X04D states you need to be in the correct directory. Hold shift and richt click in the folder where the files are located and press "Open command prompt here" then try again.

Anthony2oo5 said:
As X04D states you need to be in the correct directory. Hold shift and richt click in the folder where the files are located and press "Open command prompt here" then try again.
Click to expand...
Click to collapse
I probably should have clarified, but by quoting step 7 as the point it failed, I meant to imply that I had performed steps 1-6. Step 6 is the "open command prompt here" step.

graymoment said:
I probably should have clarified, but by quoting step 7 as the point it failed, I meant to imply that I had performed steps 1-6. Step 6 is the "open command prompt here" step.
Click to expand...
Click to collapse
That error means flash-all.bat is not in the same directory as the command prompt you opened. You unzipped it elsewhere, didn't unzip it or you opened the command prompt in the wrong place.

Flash this file after flash other files
VerifiedBootSigner

How to fix a soft bricked device from a flash that failed due to missing files

This guide is meant to less techie people, and written in detail. Please don't mind me if I overexplain. If you have any questions, feel free to comment them.
Also, I am not responsible for anything you do to your phone; you assume your responsibility for anything you do because of this guide.
Scenario:
So, lets say that you tried to flash an zip file on your android using sideload, but the zip required another file to be in the same directory as it, in order to work.
After flashing the zip and getting an error, your phone may not get pass the logo of the brand and be soft bricked.
Also, you formatted your external sd as internal, and cant access your usual location with files in the recovery.
In this case, don't worry, as I'm here to help you unbrick your phone without reinstalling the rom.
Things you will need:
your phone
a computer connected to your phone with an usb cable
the proper drivers for your phone
a custom recovery like cwm or twrp installed on your phone
probably root, although I'm not sure
and finally the adb (android development bridge) utility
Where to get a custom recovery?
- https://www.xda-developers.com/how-to-install-clockworkmod/
or search on xda under at your device's forum
Where to download adb from?
- https://forum.xda-developers.com/showthread.php?t=2588979 (this one comes with the drivers)
- https://dl.google.com/android/repository/platform-tools-latest-windows.zip (just the adb files)
So lets get started:
First, get your phone into Recovery mode (on samsung hold power button volume up and home button), and connect it to your pc with a usb cable.
Open ADB by shift + right clicking the folder platform-tools in witch it is located. Click on "Open Command Prompt window here" or "Open Powershell window here" (depends on your windows settings).
You need to find a location on your phone that is accessible through the flash zip menu from your recovery. (from sdcard / from sdcard1 or whatever your external sd is called)
In my case, i could get to see folder 0 and obb from "flash zip from sdcard".
To find a suitable folder:
In the window, type
Code:
adb.exe shell
if you opened cmd, or
Code:
./adb.exe shell
if you opened powershell.
This will open a terminal that will run commands on your phone.
(Now you can type commands in the cmd window that will be run on your phone.)
Type in
Code:
cd /sdcard/0
to go to the main sd card location that is accessible in recovery when you go to flash a zip from there. (if you can get to another folder where you could a flash a zip from, change the location to that place)
You can use here the command
Code:
ls
to view objects in the folder you are in.
After you are done, type
Code:
exit
to exit.
To solve the soft-brick, you need to reflash the zip, but with the files it needed in the same directory.
Type in the ADB window
Code:
./adb.exe push "location of the file you are sending" "location of the folder you are sending to (eg. /sdcard/0)"
if you are in powershell, or without the ./ if you are in cmd.
Use this until you have sent all the files needed for a successful flash.
Then just use the "flash zip" utility from your recovery with the location you have sent the files to, on your phone, to complete the flash, and solve the half-brick.
Restart your phone and you should be good to go.
Thanks to the following threads, that helped me put this together, and solve this problem on my phone:
https://forum.xda-developers.com/showthread.php?t=1927198
https://forum.xda-developers.com/showthread.php?t=2588979​

Bricked full stock

I never modified my phone whatsoever, I apply the OTA updates
Last day it bricked between my hands while I texted someone
I can boot it in "CSC FastBoot Mode" and here I can select what I want to do
Is there a way to reflash it without loosing data? Or anything, but retreiving my data

Please, someone can reply if it's possible?

Does it offer the option to access/start recovery? If yes once in recovery mode you should be able to choose apply update from adb or maybe even apply update from sd card.
Depending on the firmware you were on (Android 11 or Android 10) download the appropriate firmware version from https://www.asus.com/Mobile/Phones/All-series/ZenFone-6/HelpDesk_BIOS?model2Name=ZenFone-6 and rename it to update.zip and put in on your sd card if you have one and if that options is available. If that option is available choose that option and navigate to the appropriate folder and choose the update.zip.
If you only have the apply update from adb option or the other one doesn't work download the platform tools https://developer.android.com/studio/releases/platform-tools first, extract them, connect your phone to your pc, then in the extracted folder hold shift key while right clicking an empty space in the extracted windows explorer folder and choose the option "open command prompt here" or similar. On your phone choose the update from adb option, in the command prompt on pc put in adb devices first. If it hasn't already windows should install drivers now and the command prompt should say a long sequence of numbers and "sideload" besides it. If windows doesn't recognise the device or it doesn't show any device in the command prompt line go to windows updates, "show optional windows updates", open driver updates and it should offer an ASUS android bootloader or ASUS adb driver or something similar.
Once that works simply input the command shown on the phone adb sideload update.zip or similar into the command prompt and it should reinstall the full OTA again without wiping anything.

*double post*

regenwurm16 said:
Does it offer the option to access/start recovery? If yes once in recovery mode you should be able to choose apply update from adb or maybe even apply update from sd card.
Depending on the firmware you were on (Android 11 or Android 10) download the appropriate firmware version from https://www.asus.com/Mobile/Phones/All-series/ZenFone-6/HelpDesk_BIOS?model2Name=ZenFone-6 and rename it to update.zip and put in on your sd card if you have one and if that options is available. If that option is available choose that option and navigate to the appropriate folder and choose the update.zip.
If you only have the apply update from adb option or the other one doesn't work download the platform tools https://developer.android.com/studio/releases/platform-tools first, extract them, connect your phone to your pc, then in the extracted folder hold shift key while right clicking an empty space in the extracted windows explorer folder and choose the option "open command prompt here" or similar. On your phone choose the update from adb option, in the command prompt on pc put in adb devices first. If it hasn't already windows should install drivers now and the command prompt should say a long sequence of numbers and "sideload" besides it. If windows doesn't recognise the device or it doesn't show any device in the command prompt line go to windows updates, "show optional windows updates", open driver updates and it should offer an ASUS android bootloader or ASUS adb driver or something similar.
Once that works simply input the command shown on the phone adb sideload update.zip or similar into the command prompt and it should reinstall the full OTA again without wiping anything.
Click to expand...
Click to collapse
How can I know if I need WW version or another one?
I don't remember if I was on 10 or 11 but I applied all OTA until december 2020, something like that
And how can I know if I can take the last firmware version or not?
Booting into recovery mode gives a black screen for 10 seconds then a reboot
Even the charging mode display bolt before charging animation then black screen then reboot itself after a time
Only CSC mode works normally, displaying something and not rebooting

In general ASUS does only offer one firmware package for all regions as far as I know and the statement on the firmware page generally only means which regions it has been certified for. Further information can be found at https://zentalk.asus.com/en/categories/zenfone-6-(zs630kl)
It depends on where you bought the device.
If recovery mode isn't accessible you will most likely have to use on of the unbrick threads under https://forum.xda-developers.com/f/asus-zenfone-6-2019-guides-news-discussion.8906/ most probably https://forum.xda-developers.com/t/...k-your-zenfone-6-android-p-q-zs630kl.4189715/ will help you here.